To automate processes with RPA Designer, it is required to understand the general structure of displayed workflows. The scope-based modulation principle of RPA Designer must be considered in every case.
Follow the Golden Rule of modulation within RPA Designer. To build your processes, use the following scopes:
-
Scope 0 - The Microbot
Scope
Microbots/Buildingblocks
Structure your processes so that the top layer of your Hyland RPA Designer flowchart contains only the basic logic of your process. In a best case scenario, scope 0 will only contain Microbots, Buildingblocks, and Decisions.
-
Scope 1 - The Application Scope
Applications, Decisions, Microbots
This scope is intended to give an overview of the different applications used for the corresponding Microbot/Buildingblock. In here, Try to use the necessary Decisions, Loops, and Microbots.
-
Scope 2 - The Window Scope
The Window Scope will illustrate the logic taking place within the corresponding parent application. Try to use only windows, Decisions, Loops and Microbots
-
Scope 3 - The Activity Scope
The activity scope is meant to be your lowest scope level. In this scope all activities for a certain window/application take place such as Get Cell Value or Click Element. Besides the Activities Loops, Decisions or Microbots can be placed in this scope.
The Activity Scope is intended to be your lowest level of scope. In this scope all activities for a specific window/application take place, such as Get Cell Value or Click Element. Besides activities, loops, decisions or microbots can also be placed in this scope.