Designer Screen Layout
A process is an automation scenario used with Brity RPA. There are three types of upper-level objects that can possess processes: ① New Regular project ② New Headless project ③ New Process flow The three object types above may be classified depending on how they are executed by Bot. For more information about each object type, see Project, Process flow, and Headless project.
For regular and headless projects, the same Designer screen layout is provided. However, the Designer screen layout is different for process flows. The following explains the different screen layouts and provides information about how to use them.
Project screen overview
The following explains the Designer screen layout for regular and headless projects. A project consists of the following components:
Menu and toolbar
Project
Library
Canvas
Shared Resource, Variables, and Output
Properties
No. | Description |
---|---|
1 | Menu and toolbar |
2 | Project |
3 | Library |
4 | Canvas |
5 | Shared Resource, Variables, and Output |
6 | Properties |
Menu and Home
Menu
You can check the menu by clicking the icon on the designer title bar.
A set of menus that provide Designer features for creating, opening, and saving projects or processes, and configuring the settings.
No. | Description |
---|---|
1 | Create a new project or process flow. |
2 | Open a saved project or process flow. |
3 | You can launch the designer to open the project or process flow. |
4 | Open most recently used file. |
5 | Save the file you are currently working on. |
6 | View the execution results and times of recently executed processes. |
7 | Import projects or process flows from the server or package. |
8 | Distribute projects or process flows to the server or export a copy of the project or process flow as a package. |
9 | Design a project with the recording feature. Provides the same feature as the record button on the toolbar. |
10 | Run or stop a designed project. |
11 | You can select tabs to display on the screen, such as projects, library views, etc. |
12 | Check and scan CPU and memory usage. |
13 | Change the Designer, Server, and License settings. |
14 | View the user manual, samples, open source license, logs, or Designer information. |
15 | View the designer's open source license, log, version and update package information. |
16 | Close Designer. |
Settings
To configure Designer settings in the menu, you can click Settings, including the View, Assign Object, Record, and Language options.
No. | Description |
---|---|
1 | Basic Tab: Set up default settings such as designer language. |
2 | View Tab: Set up viewing settings, such as popups that occur during designer use. |
3 | Assign Object Tab: Set up settings for designating automated objects. |
4 | Record Tab: Set up settings related to automatic scenario recording. |
5 | Engine Tab: Set up settings for the engine used in running automation. |
6 | Server Tab : Set up settings associated with a server associated with a designer. |
7 | License Tab: Set up the settings related to the license. |
Basic
No. | Description |
---|---|
1 | [Language] Select a language for Designer. |
2 | [Auto Save Interval (min)] Set the intervals for automatic saving when editing a process or task. |
3 | [Login Browser] Set the browser type for SSO login. |
4 | [Base Folder] Set the default path to store projects. You can click Check to ensure that you have the permission to access the folder. |
View
No. | Description |
---|---|
1 | [Show Play Popup] Display a pop-up asking whether to minimize the Designer while a process or task is executed. |
2 | [Minimize in Play] Set whether to minimize Designer while a process or task is executed. |
3 | [Trace Execution] Track the current step of the process and indicate it on the Designer screen. |
4 | [Show Execution Report] Automatically display the execution report when the process is complete. |
5 | [Show Extension Notification] Set whether to provide a notification when an extension program is added. |
6 | [Show Property Guide] Display descriptions for each property item in a library. |
7 | [Use Chrome result image] Display the Chrome library target image in the report. When this option is enabled, the browser window will blink while the image is saved. This option is always enabled for Headless Chrome projects regardless of this setting. |
8 | [Close all opened tabs] Close all open tabs after executing a process or task. |
9 | [Show Debug Log] Display the debug log in the output viewer. |
10 | [Use Activity Recommendation] When creating the scenarios, use activity recommendations. |
Assign Object
No. | Description |
---|---|
1 | [Show CheckOption Popup] Display the pop-up window for check options to locate objects. |
2 | [Use Auto CheckOption] When performing an automation, Designer automatically enables the check option to search for objects. |
3 | [Show Indexing Popup] Display the indexing option pop-up window. |
4 | [Use Auto Indexing] Automatically specify the index (order) of objects sharing the same property. |
5 | [Show Assign-Tip Popup] Display the tips for assigning objects in a pop-up window. |
6 | [Use Invoke as Default] Set to use “Invoke” as the default value. |
7 | [Show sub-object bounds] Display the boundary of sub-objects when an object is selected. |
8 | [Hide Capture image] Set whether to hide the captured image that is the target of an activity. While this option is enabled, the captured image will not be displayed when the target object is selected in an activity card. |
Record
No. | Description |
---|---|
1 | [Show Record-Tip Popup] Display tips for recording in a pop-up window. |
2 | [Disable steps before automatic conversion (delete when unchecked)] Set whether to keep the recording before an automatic conversion in a diagram in a disabled status or to delete the recording. |
3 | [Display stepname as detailed event info] Set whether to display the name of recorded steps as detailed event information. This option will be applied only to the projects that have been recorded with Recorder. |
Engine
No. | Description |
---|---|
1 | [Clean Up ALL] Close all applications executed by a process to reliably execute automation. |
2 | [Clean Up NEW] Close all applications executed by Bot to reliably execute automations. |
3 | [Clean Up Ignore List] Set the items that will be excluded from clean-up operations. Separate each item with a semicolon (;). (Ex.: |
4 | [Step Image Max Count] Set the maximum number of execution screen images that will be stored. For example, if there are 10 steps and the maximum number to be stored is 3, the last three screens, 8th, 9th, and 10th, will be stored when the steps are executed. |
5 | [History Backup Count] Set the number of execution history entries that will be backed up. |
6 | [Step Result Max Count] Set the maximum number of steps that will be stored in report. The report will not be created if “0” is entered as the setting value. |
7 | [Allow Draw Bounds] Retrieving the objects and images during job execution determines whether to display the search bounds. |
8 | [Use Old Version Library] Set to use old versions of libraries, such as the Web library. |
9 | [Use DirectX Screen Capture] Enables capture using DirectX technology when capturing a screen. |
10 | [Message Box Auto Close(Sec)] Close the message box automatically when the specified time (Second) is elapsed. The message box will not close automatically if "0" is entered as the setting value. |
11 | [Chrome Default Latency(ms)] Set the required default waiting time according to the performance of the execution environment if the execution result of the chrome library is unstable. |
12 | [Clean up chrome Library data] Set whether to remove automatically generated data during Chromeopen. The generated data is automatically cleaned up with or without option activation when using Chromeclose. |
13 | [Use the lite model of the GUI Detector] Check if the default is a lite model, as it takes longer to navigate if not used. It runs on a model where more objects can be found. If you use a new model while changing the settings, you need to install a new model, as the two models are not compatible; while changing the settings, the behavior of the existing scenario is not insured. |
14 | [Debug Mode] Store the variable values from the previous execution if an error occurs while performing a process |
15 | [Validate Variable Type] Check if the variable types declared during the execution are assigned with different types of values. |
16 | [Use Variable Monitoring] When used with the debug mode, you can monitor the values of variables at the time of the currently executing step in real-time. The variable value is displayed just before the current step is executed. |
17 | [Use Remote BOT] Set the scenario to run the remote BOTs. Set the IP of the bot to use. Enabled: When a process is executed, a pop-up to enter information from a remote location is displayed. The process is executed in the remote bot set by the user. |
Server
To change designer server settings, including whether to use system proxy, server IP, and OCR server URL, click Settings > Server Settings from the menu.
No. | Description |
---|---|
1 | [Server Address] Set the server address |
2 | [Server Port] Set the server port |
3 | [User System Proxy] Select whether to use a proxy on the system or not |
4 | When deploying a project with [Export > Deploy to Server], set the maximum capacity of the compressed package for the project. The capacity limit is determined by the server's settings or network policy. |
5 | Set the path to download the file. |
Help
Sample
You can check the library samples provided by Designer. In the menu, click Help > Sample.
Sample files are not included in the installation file. You can download the sample files to a specified path to view them. For more information about viewing sample files, see Using Samples.
Update Manager
In the menu, click Help > Update Manager
Update Manager is available only after designer login.
See Update Manager for more details
Home screen
You can check the home screen by clicking the icon on the designer title bar.
Home
No. | Description |
---|---|
1 | Displays the New Project popup. |
2 | Displays the New Headless Project popup. |
3 | Displays the New Process Flow popup. |
4 | Displays a list of recent files. |
5 | Displays a list of recommended tutorials. |
6 | Displays a list of samples. |
7 | Go to https://brityworks.ai/solution/casestudies/list. |
8 | Go to https://www.youtube.com/c/BrityRPA. |
9 | Go to https://brityworks.ai/community/forum. |
Learning
No. | Description |
---|---|
1 | Viewing the designer configuration again. |
2 | Displays a pop-up list of recommended tutorials. |
3 | Displays the New Process Flow popup. |
4 | Displays a sample list popup. |
5 | Go to https://brityworks.ai/community/learn. |
6 | Go to https://www.samsungsdsbiz.com/help/RPA_User_2_5_0#3909fad467fcc826 page. |
7 | Go to the https://brityworks.ai/community/forum?board_id=1&category=109&offset=1&limit=6&pageType=list&isPrivate=false&isGroup=false&selectedAll=false&moreClickFlag=true. |
8 | Go to https://brityworks.ai/solution/marketplace. |
Open
Click Open, and Windows Explorer pops up. After selecting the selected project file, click the Open button to open the selected project.
Toolbar
The toolbar includes tool buttons required to utilize Designer, such as Record and Run, and icons for the save, copy, delete, collapse, and expand features.
No. | Description |
---|---|
1 | [Run] Run the currently open process or task. |
2 | [Record] Record the screen control on a PC to automatically design a process. |
3 | [Save] Save the currently open process or task. |
4 | [Save All] Save all open processes or tasks. |
5 | [Undo] Cancel the last action executed on the canvas. |
6 | [Redo] Run the canceled action again. |
7 | [Paste] Paste the copied or cut node. |
8 | [Copy] Copy the selected node. |
9 | [Create Block] Create a block that surrounds the selected activities. Blocks are useful when you design a long, complicated process because they can be collapsed and expanded. |
10 | [Small View] Decrease activity card size. By decreasing the activity card size, you can utilize the canvas screen more effectively. |
11 | [Collapse Group] Select vertically connected nodes and collapse them. |
12 | [Disable] Deactivate the selected activity. Deactivated activities will not be executed during a run. |
13 | [Reverse] Select all activities other than the currently selected ones. |
14 | [Search] You can search activity name, variable name, description, etc. |
15 | [Navigate Forward] Moves to the activity card in front of the currently selected activity card. |
16 | [Navigate Backward] Moves to the activity card behind the currently selected activity card. |
17 | [Move Mode] You can use a move mode and mini-map that allows you to move the chart. |
18 | [Chart View] Display a preview screen at the bottom of the canvas. You can select the [Chart View/Grid View] displayed on the button. |
19 | [View Recent Reports] Click or double-click this icon to view the reports of recently executed processes or tasks in a tab or pop-up window. |
20 | [Maximize] Maximize the canvas screen and hide the Project, Library, and Properties panes. |
21 | [Init Layout] Initialize the screen to the default layout that is provided when Designer is run for the first time after installation. |
22 | [View scale] Adjust the view scale to magnify or shrink the canvas screen. |
23 | [Login/Logout] Log in to or log out from the server. |
24 | [Notice] It is used for receiving notice from the RPA portal if any. |
25 | [Cut] Cut the selected node. |
26 | [Delete] Delete the selected node. |
27 | [Copy History] Copy the history. |
28 | [Move Mode] You can use the move mode to move the chart. |
29 | [Mini Map] It displays the mini map screen at the bottom of the canvas. |
30 | [Open Activity Grid View] View the activities on the canvas in grid view. |
31 | [Chart View] View the activities on the canvas in chart view. |
Project
The hierarchy structure of a project created on Designer is displayed in this area. The structure consists of process, task, shared task, event, custom libraries, and resources.
For more information about each component of a project, see Project components, Process flow components, or Headless project components.
Library
You can design automation tasks by dragging and dropping activities from the library onto the canvas.
Library view
Activities used to create automated processes are displayed in this area, classified by target apps or features. Libraries are grouped into 25 categories. You can drag the activities under a library and drop them on the canvas to design automated processes.
Automated Task Type
It is classified by the type of task that includes the automation task.
Library Search
You can find a library by entering a search term at the top library search bar. You can still search through search terms if you are not using the library.
Library Settings
You can configure library settings by clicking on the Library tab .
No. | Description |
---|---|
1 | You can select the library view. |
2 | Displays the library list. You can add/remove libraries by selecting/deselecting them from the list. |
3 | Displays a list of selected libraries. You can remove a library by clicking the X button in the selected list. |
4 | You can change the library group sort direction. |
5 | You can change the sort criteria for activities within a group. |
Canvas
The canvas area is where you can create a flow chart by placing the activities included in the libraries by drag-and-drop.
Chart Movement Menu
Click the menu button located at the bottom right of the chart view. Usually, it is collapsed, but when you click it, it expands to reveal a menu with choices. Each button operates as a toggle. You can select Horizontal Scroll (Shift+Scroll), Move mode, and Mini-Map.
Shared Resource, Variables, Output
Shared Resource
The list of shared resources that can be used in projects is displayed here. After distributing frequently used files or text strings to the Orchestrator server, you can allow all users to use them in their projects. Shared resources are shared across users within the same tenant, and are created, edited, and managed by administrators on the Admin Portal. Normal users can import shared resources on Designer to use them. However, shared resources can be imported only when you are logged in on Designer because access to the Orchestrator server is required to use them.
While logged in to the server, you can click Click here to add new item to display the list of shared resources as shown below. You can select a shared resource from the list and import it.
Shared resource features
Shared resources imported from the server cannot be edited on Designer.
On Designer, you can use shared resource with variables by calling then in the form of "
Asset.VariableName
.”Shared resources are dependent upon the tenant. If you log in to the server with another tenant, the previously imported shared resources will be indicated as #REMOVED# and become unavailable.
Categories and encryption types of shared resources
Classification of shared resources (category)
File
String
Application of security policy
File | String | |
---|---|---|
General | O | O |
Secure | O | O |
Credential | X | O |
Encryption types - difference between “Secure” and “Credential”
For “Credential” data, a stronger encryption module than the encryption module used for the “Secure” data is applied. Therefore, it is recommended that you apply the “Credential” encryption for essential data that must be secured, such as passwords.
Secure: In the [App] MessageBox activity card, assign
Asset.'SharedResourceName'
to Arguments, one of the MessageBox activity card properties, to view the decrypted string.Credential: Because it is impossible to view the decrypted string, the “Credential” encryption is used to protect data that must not be exposed externally. Only four activity cards can utilize the credential strings by calling them with variables. ([App]CredentialSetText, [App]CredentialTextInput, [SAP]CredentialSetText, [Chrome]ChromeCredentialSetText)
Variables
This area is where you can define the variables used in the project you are creating.
Each time you add a new variable, the variable name will be automatically created as var+number
.
No. | Description |
---|---|
1 | [Name] Set the variable name. |
2 | [Initial Value] Set the initial value of the variable. After the initial value has been set, you can allow the variable to carry the set value without assigning one. You can click , select Any or Script as the editor type, and enter the initial value. |
3 | [Type] Select one of the eight data types that matches the type of data. - Any: All data types that can be supported in Designer, including String, String Format (DateTime, DirectoryPath, ...), Integer, Double, etc. - String: Supports text string values. Enter the value between two single quotation marks (‘’). - Boolean: Supports one of the two values - true or false. - Integer: Supports integer number values. - Double: Supports numbers with decimal points. - Date: Supports date-type values. The date format must be entered as YYYY-MM-DD. - Array1D: Supports one-dimensional array. (Ex.: ['a', 'b', 'c']) - Array2D: Supports two-dimensional array. (Ex.: [[1,2], [3,4], [5,6]]) |
4 | [Scope] On the drop-down list, select one of the four options that matches the scope and purpose of the data. - Normal: This variable can only be used within the same process or task and can be called in format. - Input: This variable is used as a parameter for transmitting a value between processes or tasks. It stands for the input value received before executing a process or task and can be called in format. - Output: This variable is used as a parameter for transmitting a value between processes or tasks. It stands for the output value received after a process or task has been executed and can be called in format. - Global: This variable can be used in all processes or tasks in the project and can be called in format. |
5 | [Description] You can add descriptions of variables. |
6 | Displays the marker at the step where the Marker variable is used.When clicked to set it to the On state, the marker is displayed, and when it is set to the OFF state, the marker is released. Right click on the variable and click 'Change Color' in the context menu to change the color of a marker. |
Log
This screen shows the outputs log when the process or task is run. You can view the current progress and error messages.
Log Type
You can click and view the INFO, NOTICE, WARN, and ERROR entries in the logs.
Log Settings
You can click the Setting icon on the right side of the screen; It specifies the color for each log type, designates keywords, and select whether to use the debug log view.
No. | Description |
---|---|
1 | Change the INFO log color |
2 | Change the NOTICE log color. |
3 | Change the WARN log color. |
4 | Change the ERROR log color. |
5 | Specify keywords. |
6 | You can change the color of the specified keyword. |
7 | You can select whether to view the debug log or not. When Enabled is selected, DEBUG, TRACE log buttons are displayed on the right side of the log window. |
8 | You can change the maximum number of total log entries to display in the output window. |
Log Search
Enter Ctrl+F in the log screen, and the search window is displayed; you can search by entering the search term.
No. | Description |
---|---|
1 | Enter search term. |
2 | Browse your search terms. |
3 | Previous search. |
4 | Find the next one. |
5 | Exit search bar. |
Copy, Select All, Clear All Log
You get the option to Copy/Select All/Clear All Log by right-clicking on the log screen.
View Log Files
Click the View Log File icon on the right of the output window to open the file where the log is currently written in a text editor connected to your system.
Properties
Properties screen allows you to view or specify the detailed information of an object selected on Designer. Different properties are displayed depending on the selected object (project, process, task, event, activity card, etc.).
Project properties screen
Process properties screen
Library properties screen
Activity card properties that must be filled in are marked with “*.” If the required fields are not filled, the property fields will be indicated with red borders.
If no sub-activity card is selected in the Libraries tab, a library description is displayed in the Properties window. If a sub-activity card is selected, you can check the library description in the properties window by selecting another library and then selecting the library again.
Activity card properties screen
Activity card properties that must be filled in are marked with “*.” If the required fields are not filled, the property fields will be indicated with red borders.
If the required fields of an activity card are not filled, the activity card will also be displayed in a red box on the canvas.
The properties vary depending on the selected activity card. For more information, see the properties screen of individual activity cards.
Activity card's properties screen: quick setup with minimal input
While entering the properties of the activity card, check Quickly set with minimal input; only the main properties that the user needs to check are displayed, and you can easily enter the property values.
The text is displayed in red at the top in the incomplete property state, as shown below.
When all required properties are entered, and in an executable state, the text at the top of the properties window changes to blue, as shown below.
Variable and Attribute Input Assistant
The variable and attribute input assistant helps you enter the initial value or attribute value of a variable. Various value editors are provided according to the value format of a variable or property, and variable or property values can be entered at once without using the DataConverter activity by using variables and built-in variables and value conversion functions. In addition, you can write JavaScript code directly through the script editor to generate and input the necessary values.
See Property Assistant for more details.
Enter values according to the format
If you select [Enter a value according to the format], a list of available [Value input format] is provided according to the value format of a variable or property, and the value input screen changes according to the selected [Value input format]. The value's format is checked when the user enters a value, and an error message is displayed if the input is abnormal.
Using Variables (User Generated Values)
If you select [Use variable (value created by the user)], you can use the [created variable] created in the variable window as an input value. You can use the selected variable directly or select [Available Functions] to convert the value of the variable to use. Depending on the selected function, you may need to enter additional parameters.
If [Use variable (user-created value)] is displayed only in the input of properties, it is not displayed when inputting the variable's initial value.
Using built-in variables (default values provided by the bot)
Select [Use built-in variable (default value provided by bot)]; you can use the default value provided by the bot in the same way as a variable.
Entering values directly into the script
If you select [Enter a value directly in the script], you can enter the value of a variable or property by writing a JavaScript code that generates the desired value.
Pattern
A pattern is a collection of library activities that can be reused The user can directly compose a flowchart within the project and use it as an activity card. Flowcharts in library patterns can be configured using processes, tasks, shared tasks, libraries, and other library patterns. Library patterns have the same components as tasks (tasks), but unlike tasks (tasks), declared can bring variables in regardless of scope (Normal/Global/Input/Output).
Creating custom patterns
There are two different ways to create a pattern.
1In the Pattern Repository tab, create a new pattern and complete a flow chart.
In the Pattern window, right-click User Patterns and click New Pattern.
2. In the New Pattern pop-up window, enter a pattern name and description and then click OK .
2 In the existing flow chart, select the area and create a pattern.
In the flow chart, select the area to create a pattern and right-click the selection.
In the context menu, Click Convert to Pattern.
3. In the New Pattern pop-up window, enter a pattern name and description and click OK .
Using patterns
Add the desired user pattern into the process by dragging and dropping the mouse.
No. | Description |
---|---|
1 | In the flow chart, select the area to create a pattern and right-click the selection. |
2 | Drag and drop it onto the desired target link within the process. |
Process flow screen overview
A process flow allows you to design by combining a number of processes published to the server. A process flow consists of the following components:
Menu and toolbar
Process flow
Process search
Library
Canvas
Shared Resource, Variables, and Output
Properties
No. | Description |
---|---|
1 | Menu and toolbar |
2 | Process flow |
3 | Library |
4 | Shared Resource, Variables, Output |
5 | Canvas |
6 | Properties |
7 | Remote Process |
Menu and toolbar
You can create, open, and save process flows and configure the designer settings. Unlike projects, process flows can only be executed on the server after it has been distributed to the server. Process flows cannot be executed on Designer because the Designer works in a client environment. You can execute process flows on the User Portal provided by the server.
Menu
Because process flows cannot be executed on Designer, the Recent Report, Record, and Run features are disabled in the menu.
Toolbar
Features of the toolbar buttons are identical to those of the project screen toolbar. However, the Run and Record buttons are disabled in the toolbar because process flows cannot be executed on Designer.
Process flow
Process flows can only have processes. Processes under a process flow project are displayed on a list with a hierarchy, as shown below.
Add Remote Process
Right-click on a remote process and select Add Remote Process; you can search for processes deployed on the server in the import window. You must be logged in to the Designers to connect to the server. The discovered process can be added as a child of the working process flow.
Right-click on the remote process and select Add Remote Process menu.
2. In the import screen, enter the search term 'purchase'. Processes with 'purchase' in the process name are searched. Select the process you want to add to the process flow and click the Import button . The process is then added as a child of the process flow. 3. In this case, select the execution type. Then you can search by execution type.
Library
While a process can utilize many libraries, a process flow can utilize only the “'ProcessFlow” library. For more information about libraries dedicated to process flows, see The internal link is invalid..
No. | Description |
---|---|
1 | Favorite (bookmark)* *A collection of frequently used activities (Click the star icon next to the activities in a library to add them as your favorites.) |
2 | Process Flow library |
Canvas
The canvas area is where you can create a flow chart by placing the activities included in the libraries by drag-and-drop.
Shared Resource / Variables / Output
The features of these windows are identical to those of the Shared Resource, Variable, and Output windows on a project screen. For more information, see Project components.
Properties
Properties screen allows you to view or specify the detailed information of an object selected on Designer. Different properties are displayed depending on the selected object (project, process, task, event, activity card, etc.).
CallProcess activity card property window
Below is the window for the process flow-dedicated CallProcess activity card. In the following example, it calls a process named “BaseProcess.”
Project
Project overview
Project is a unit that binds components for process automation. A project consists of the following seven components:
Process
Task
Shared task
Event
Custom libraries
Resources
Creating a project
In the menu, click New > New Project.
In the "New Project" pop-up window, enter the project name and description, select Start from an empty project, and then click Next.
[Precautions for entering project names]
- Spaces are not allowed.
- The first letter cannot be a number.
- Special characters (!,@,#,$,(), ...) are not allowed.
- "-" (bar) cannot be used; use "_" (underbar) instead.
3. You can select a library view to use in an empty project. If you select the library group view, the default library group list is displayed on the right, and if you select the task type view, the automation task type list is displayed on the right side list.
4. You can add/delete libraries by selecting or deselecting libraries in the library settings pop-up. Click Ok after completing the library settings. For more information about library settings, see the Library page.
5. Click the Create button after completing the library settings.
6. An empty project is created, and only the selected library group is displayed in the library view.
7. The library view is configured if you select the Automated Task Type View, as shown below.
Example of creating a Project - Create from Template
In the menu, click New > New Project.
2. In the New Project pop-up window, enter a project name and description, select Start from Template Project, and click the Next button.
[Precautions for entering project names]
- Spaces are not allowed.
- The first letter cannot be a number.
- Special characters (!,@,#,$,(), ...) are not allowed.
- "-" (bar) cannot be used; use "_" (underbar) instead.
3. Click Next, and select the template you want to use.
4. A list of library groups set in the selected template project is displayed on the right. To add/remove a library to use , click Set Library .
5. You can add/delete libraries by selecting or deselecting libraries in the library settings pop-up. After completing the library settings, click the OK button. For more information about library settings, see library settings.
6. Click the Create button. After checking on Automatically start the activity helper in the Assist option.
Help Option: Start the activity assistant automatically. After checking, click the Create button to start the activity assistant after creating the project automatically. For more information see Activity Assistant.
7. A project is created based on the selected template; only the selected library group is displayed in the library view.
Project components
Process
A process is an automation scenario, which is the unit of the tasks performed by Bot.
When you create a new process, a process named “MyProcess” will be automatically created.
Creating a process
In the Project window, right-click PROCESS and click New Process.
In the "New Process" pop-up window, enter the process name and description, and then click CREATE.
[Precautions for entering process names]
- Spaces are not allowed.
- The first letter cannot be a number.
- Special characters (!,@,#,$,(), ...) are not allowed.
- "-" (bar) cannot be used; use "_" (underbar) instead.
※ The requirements are identical to those for project names.
Example of creating a process - create from template
1. Right-click Processes in the Projects screen and select New Process .
2. In the "New Process" pop-up window, enter the process name and description, Check Create from Templates and then click Next.
[Caution when writing process name]
- No spaces (spaces)
- Numbers cannot be entered in the first letter
- Cannot input special characters (!,@,#,$,(), …)
- Can't input '-' (bar), '_' (underbar) can be input
※ It is the same as the precautions when writing the project name.
3. Select the template you want to use and click the Create button.
Help Option: Start the activity assistant automatically. After checking, click the Create button to start the activity assistant after creating the project automatically. For more information, see Activity Assistant.
Example of process configuration
Processes can import and organize other processes, tasks, and libraries .
Task
Task is a module of a process in operation. A process is a unit of automation that is performed by Bot. On the other hand, tasks cannot be performed by Bot.
Creating a task
Create a new task in the lower left task tab of the project and complete the flowchart.
In the Project window, right-click Task and click New Task.
In the "New Task" pop-up window, enter the task name and description, and then click CREATE.
[Precautions for entering task names]
- Spaces are not allowed.
- The first letter cannot be a number.
- Special characters (!,@,#,$,(), ...) are not allowed.
- "-" (bar) cannot be used; use "_" (underbar) instead.
※ The requirements are identical to those for project names.
Creating a Task - Creating from Template
Use the template to create new tasks and complete flowcharts.
In the Project window, right-click Task and click New Task
2. In the "New Task" pop-up window, enter the process name and description, Check Create from Templates and then click Next.
[Precautions when creating a job name]
- No spaces (spaces)
- Numbers cannot be entered in the first letter
- Cannot input special characters (!,@,#,$,(), …)
- Can't input '-' (bar), '_' (underbar) can be input
※ It is the same as the precautions when creating the project name.
3. Select the template you want to use and click the Create button.
Help Option: Start the activity assistant automatically. After checking, click the Create button to start the activity assistant after creating the project automatically. For more information Activity Assistant See page.
Creating a Task - Creating from Flowchart
Select the area you want to create as a task from the already created flowchart and create it.
Select the area created as a task in the flowchart and right-click.
Click Convert to Task in the shortcut menu that appears
Example of creating a task
As it is with a project, you can create a task by utilizing processes, import and organize processes, other tasks, and libraries.
Shared task
You can import shared processes or tasks distributed to Orchestrator into Designer and use them as modules of automation processes.
After distributing a project to the server, the project cannot be used as a shared task until activated. You can import only processes or tasks that have been activated after the distribution to the server.
Use cases of shared tasks
Shared tasks can be used to address the following cases:
Duplicated tasks by different users: When two or more users within the same tenant need to utilize the same process or task.
Duplicated tasks by different processes: When two or more processes within the same tenant need to utilize the same process or task.
Importing a shared task
Log in to the server on Designer.
In the Project window, you can right-click SHARED TASK and click Import From Server.
In the "Import" pop-up window, select a process or task under a searched project and click IMPORT. You can select two or more processes or tasks while pressing the Ctrl or Shift key to import multiple shared tasks at once.
No. | Description |
---|---|
1 | [Run Type] Select “Normal” or “Headless” to display only processes that run in the foreground or background. |
2 | [Type] Select “Process” or “Task” to filter the search result. |
3 | [Project Name] Project names are displayed |
4 | [Process/Task Name] Names of processes or tasks under projects are displayed. |
5 | [Version] The version of the process or task is displayed. |
6 | [Author] The ID of the user who modified the process/task last is displayed. |
7 | [Updated] Uploaded date and time of the process or task is displayed. |
8 | [Description] Description of the process or task is displayed. |
9 | [Search Text] Search by project or process/task. |
Example of shared task utilization
Shared tasks are used when you create a flow chart with processes or tasks on Designer. Shared tasks can be used in the same manner as ordinary tasks. Therefore, when you utilize the shared tasks after importing them, they are described as "Task" regardless of the original types of the shared tasks.
Event
You can utilize events in a flow chart, just like you utilize processes or tasks, and have them called at a specific time point while the process, task, or activity is performed, as shown in the following table.
Object that calls the event | OnBefore | OnAfter | OnError |
---|---|---|---|
Process | O | O | O |
Task | O | O | O |
Activity | X | X | O |
- OnBefore, OnAfter: Call the event regardless of errors.
- OnError: Call the event only if an error occurs during a run.
Creating an event
In the Project window, right-click EVENT and click New Event.
In the "New Event" pop-up window, enter the event name and description, and then click CREATE.
[Precautions for entering event names]
- Spaces are not allowed.
- The first letter cannot be a number.
- Special characters (!,@,#,$,(), ...) are not allowed.
- "-" (bar) cannot be used; use "_" (underbar) instead.
※ The requirements are identical to those for project names.
Example of event utilization
Events are called to perform a specific action before or after an automation process, or when an error occurs while an automation process is performed. In the Project window, when you double-click a process or task to call an event, the onBefore, onAfter, and onError combination boxes will be displayed in the Properties window. Also, in a flow chart, you can double-click a process, task, or activity to display the onError combination box. Each combination box is used to set a different time point to call the event, as follows: · onBefore: Before a run · onAfter: After a run · onError: When an error occurs during a run
Create an event and configure it to display a message box saying "This is a test" on the flow chart.
Custom library
The custom library feature allows you to refer to external libraries.
The available external libraries are as follows:
JavaScript library
MS Workflow activity library
MS.NET library
Resource
You can register frequently used files within the project as resources and call them via the specified paths.
Adding a Resource
In the Project window, right-click RESOURCES and click Add Resource.
On File Explorer, select the file to register as a resource and click Open.
Utilizing resources
You can utilize the specified paths via variables to call resources.
Global.ResourcesDir + 'ResourceName.extension'
Group
When there are many sub-components under a project, you can group them in different folders according to their purpose. A group can also include multiple subordinate groups. Project components that can create folders are as follows:
Process
Task
Custom library
Library template
To create a new group, complete the following steps:
On the project screen, right-click TASK and click New Group.
In the "New Group" pop-up window, enter the name for the new group you want to create and click CREATE.
A new group is created.
Navigating between groups
You can navigate between the processes, tasks, custom libraries, and library templates in the groups or navigate between the groups. Select a task to move and drag-and-drop it to the desired position.
Make sure to close an open task before navigating.
Process flow
Process flow overview
Process flows are used to implement automation of process flows. One process flow can call multiple processes and control the flows between the processes.
Difference between a regular process and a process flow
[Regular process - Automation of tasks] In regular processes, one process works as the unit of performing an automation process. The automated individual tasks stand for task units that can be completed without human intervention. [Process flow - Automation of process flows] You can combine existing processes to compose the order and flow of processing. You can also control the process flows that require human interactions on the process flow server.
Process flow features
[Creation/Execution]: Process flows can be created on Designer, but can be executed only on the server. (※ Scheduled tasks are executed based on the server time [UTC].)
Library: Process flows have the “FlowControl” library which is dedicated to process flows.
Management: After distribution to a server, process flows are activated, executed, and monitored separately from normal processes.
Adding Waiting Action
A process flow is an asynchronous method that is not performed in order. If a process must be performed in order, an action of waiting until the previous process ends must be applied. For example, if a mail writing process must be performed after completing a login process, add the WaitForMultipleEvents activity card between these two processes.
No. | Description |
---|---|
1 | Logging In |
2 | Waiting for the completion of the "Logging in" process |
3 | Writing email |
4 | Waiting for the completion of the "Writing email" process |
Creating a process flow
In the menu, click New > New Process Flow.
In the "New Process Flow" pop-up window, enter the process flow name and description, and then click CREATE.
[Precautions for entering process flow names]
- Spaces are not allowed.
- The first letter cannot be a number.
- Special characters (!,@,#,$,(), ...) are not allowed.
- "-" (bar) cannot be used; use "_" (underbar) instead.
※ The requirements are identical to those for project names.
Process flow components
You can compose a process flow with processes that have been distributed to the server and automate the process flow by combining the processes imported from the server with the dedicated process flow library.
Process
Before you can add processes to a process flow, two prerequisites must first be satisfied. 1 The process to add must be distributed to the server and approved in advance. - You can view the list of process flows and the approval information on the User Portal. 2 You must be logged in to the server on Designer. - At the top-right corner of Designer screen, click the user profile icon to log in to the server.
Process flow library
The key activities of the process flow library are as follows:
Category | Key activity |
---|---|
Process flow control | If, IfThen, Loof, For, Foreach, While, Delay, TerminateFlow, Break, Continue |
Data configuration | AddDateTime, Assign, AssignDateTime, RequestAsset, ExecuteScript |
Wait for events | WaitEmail, WaitHttp, WakeUp, WaitForMultipleEvents |
Process execution | CallProcess, CallRestAPI |
For more information about individual activity cards, see Process Flow-dedicated library.
Headless project
Headless project overview
What does “headless” stand for?
The “headless” design allows for parallel, background operations of multiple tasks without occupying the screen. Utilizing the headless design, you can enhance the processing speed and make better use of your bots because it allows one bot to execute multiple tasks. Also, because errors related to unexpected actions resulting from occupying the screen can be eliminated, you can ensure reliable operation of the automated processes.
Category | Regular design | Headless design |
---|---|---|
Bot | One bot performs one task. | One bot can perform up to 10 tasks simultaneously. |
Operation | The bot occupies the screen. | The bot operates parallel processes in the background, without occupying the screen. |
Application | Tasks that require screen occupation for processing. | Processing of large amounts of data that do not require screen occupation. |
Features | The operator can visually verify the processes. | Eliminates the possibility of errors related to unexpected mouse or keyboard inputs during the process. |
Headless project features
Headless projects do not support the following libraries for recognizing objects or images:
Image recognition library
App library
SAP library
Before you can start creating headless projects, the following settings must be preceded.
The project must be created as a “headless project.”
In the Bot Client Setting pop-up window, the Headless Mode checkbox must be selected on the Server tab.
Creating a headless project
In the menu, click New > New Headless Process.
In the "New Headless Project" pop-up window, enter the headless project name and description, and then click CREATE.
[Precautions for entering headless process names]
- Spaces are not allowed.
- The first letter cannot be a number.
- Special characters (!,@,#,$,(), ...) are not allowed.
- "-" (bar) cannot be used; use "_" (underbar) instead.
※ The requirements are identical to those for project names.
Headless project components
Headless projects have the same components as regular projects. However, they have different libraries and operate in different ways.
For more information about headless project components, see Project.
For more information about libraries dedicated to headless projects, see Headless-dedicated library.