July 21, 2020



Ena Martinek

Based on our RPA consulting experience, we developed a "Procedures" feature to help you manage big projects without copying the same code in multiple processes. Those procedures contain a part of the code that you can eighter share within the process itself or use as many times as needed.

Procedure and Process in an RPA Platform

As procedures are a part of the process, they share the same features as a process. Furthermore, each procedure can have multiple inputs and multiple output parameters. For example, we can extract the opening of the application and login into that application as a procedure. Input parameters could be username and password, while the output could be a Boolean variable that denotes whether the login was successful.

Additionally, we can apply this procedure in all processes that use that application. If we have to make some changes to it, we can easily modify the procedure, and it would reflect in all the processes that are using it. In other words, procedures allow us to reuse the robot code and to make maintenance easier.

Procedure Manipulation

Also, procedures are used within a process itself to separate it into smaller sections. With it, we gain better control of the entire process. That way, you can test each part of the process separately, and if any process change occurs, you can edit only the procedure that caused it - without changing the whole process.

Keep in mind that procedures don't have stages, and any change you make will affect the process immediately. In case an error occurs, robotically automated processes are capable of handling them, too.


For executing procedures, you need to provide:
• Input parameters (whether as a fixed value or an existing variable.)
• Variables for output parameters.

Furthermore, procedures can be local or external:
• Local procedures are created inside a process and 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 every department) in your tenant.

There are no limitations for the number of procedures in the process - you can use them as many times as you want. Also, executing other procedures inside the existing one is supported.

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

In General

Some procedures are shared among the tenants. Those procedures are general processes that can be used for all tenants, for example, sending emails or manipulating files/folders.

These procedures are a part of the platform, and they can be published or 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 we're doing some processes manually, we can usually detect an error in it ourselves. However, what happens when the error occurs in the robotically...

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


    Darko Jovišić


    June 16, 2020

    Generally, in RPA team blueprints, you will find these two roles among others: RPA Developer and Business Analyst. In a nutshell, a business analyst should...