Common​

• DisplayName - The display name of the activity.

Input​

• Arguments - A list of IN arguments that you can pass to the process you want to run from Orchestrator. If an argument has an unknown type, it is converted to JSON.
• Arguments variable - As an alternative to the Arguments dictionary, you can provide a single variable that holds the dictionary of arguments to pass to the invoked process. When this variable is set at runtime, it takes precedence over Arguments.
• Process Name - The name of the process in Orchestrator you want to run, stored in a String variable. This field supports only strings and String variables. Process Name should contain the name of the Package, as that is being used by the Robot.

Misc​

• Entry Point - Specifies which workflow from the invoked process should be the one to be ran first. This field supports only strings and String variables.
• Folder Path - The path of the Orchestrator folder where the specified process is located, if different from the folder where the process is running. This field only supports string values, with / as the separator to indicate subfolders. For example "Finance/Accounts Payable".
  Note:

  The Folder Path parameter does not work for processes executed by robots in classic folders. Only robots in modern folders have the ability to pass data outside of their folder. Unserializable data types cannot be passed between workflows (e.g. UIBrowser, UIElement, etc).

• Private - If selected, the values of variables and arguments are no longer logged at Verbose level.
• Target Session - Specifies the session in which the child process is started.
  • Current - The child process opens in the same session as the parent one.
  • Process Default - The child process uses the Process Settings.
  • Main - The child process starts in the main session regardless of where the parent process runs.
  • Picture in Picture - The child process starts in the Picture in Picture session regardless of where the parent process runs.
• Use Package - Specifies if the process should be identified by its package name (selected) or by its process name (not selected).

• "The arguments could not be read from the invoked target, so they were left unchanged." - Shown when you select Refresh arguments and the process name is empty, the entry point does not resolve, the call to Orchestrator fails, or its metadata cannot be parsed. While you edit the activity, this case reports nothing.
• "The invoked target declares arguments that cannot be imported (for example, a missing name or type, or a duplicate name), so the arguments were left unchanged. Fix the target's arguments and refresh again." - Shown when you select Refresh arguments. The import is refused as a whole rather than writing only the arguments that could be built.
• "The arguments could not be updated in the workflow, so they were left unchanged. See the logs for details." - Shown when you select Refresh arguments if the invoked process was read but the dictionary could not be written back. Nothing is lost.
• "The invoked target declares no arguments. For safety the following are not removed automatically:" followed by the argument names. - Shown both when you refresh and while you edit, when the invoked process declares neither input nor output arguments. The listed arguments are kept deliberately, and you can remove them manually if the invoked process no longer uses them.
• "The invoked target declares no input arguments. For safety the following are not removed automatically:" followed by the argument names. - The same case for a process that declares output arguments but no input ones, so the message does not say the process declares nothing when it declares several.
• "The following argument(s) are missing or misconfigured:" followed by the argument names. - Shown while you edit, when the invoked process declares arguments the activity does not have, or has with a different type or direction. Selecting Refresh arguments resolves it.
• "The following arguments are extra:" followed by the argument names. - Shown while you edit, when everything the invoked process declares is already configured and the activity carries further arguments on top of it.
• "The following argument(s) are missing or misconfigured:" followed by the argument names, then "N argument(s) are extra." - Shown while you edit, when the previous two cases apply at once, which is what pointing the activity at a different process produces. The missing arguments are named, the extra ones only counted.