July 21, 2020



Ena Martinek

Based on consulting experience, we have developed a feature called procedures to help you manage big projects without copying the same code in multiple processes. Procedures contain a part of the code you want to share within processes or use multiple times.

Procedures are a smaller part of the process, therefore they have the same features as a process. Moreover, each procedure can have multiple input and multiple output parameters.

For example, we can extract the opening the application and logging in as a procedure. Input paramateres could be username and password and the output could be a boolean variable which denotes whether the login was successful. This procedure can then be reused in all processes that use this application. If we need to make a change to it, we just modify the procedure and it’s reflected in all the processes that are using it. So, procedures allows us to reuse the robot code and also make maintenance simpler.

Procedures can also be used within a bigger process to separate it in smaller parts for better control of the process. This way you can test each part of the process separately, if any process changes occur you can change only the procedure without changing the whole process. Procedures don’t have stages so any change you make will affect the process immediately. For executing procedures, you need to provide input parameters (as a fixed value or existing variable) and variables for output parameters.

Procedures can be local or external.
Local procedures are created inside one process and they can be used only in that process- they are not visible in other processes.
External procedures are shared within your tenant- you can use them in any process (in each department ) in your tenant.

There are no limitations of using procedures in the process, you can use them as many times as you want. Also, executing other procedures inside the procedure is supported.

Picture 1: Example of a procedurePicture 1: Example of a procedure

Some procedures are shared within the tenants. Those procedures are general processes that can be used for all tenants (for example: send email or file/folder manipulations). Those procedures are a part of the platform and they can be published and modified only by the team.

Picture 2: A list of external proceduresPicture 2: A list of external procedures
Thank you for leaving a message!
Other posts
  • Exception handling


    Ena Martinek


    June 18, 2020

    When the process is done manually, most of the time employees can recognize errors in the process but what about the robots? What will the robot do in those...

  • RPA Developer and Business Analyst – do we need both?


    Darko Jovišić


    June 16, 2020

    Very often in RPA team blueprints you will find two roles among others: RPA Developer and Business Analyst. In a nutshell, business analyst should talk to the...