REFramework in UiPath

REFramework in UiPath

The Robotic Enterprise Framework is a project template provided by UiPath which follows all the best practices involved in development. It can be used to design all kinds of processes from simple to complex level. It is mostly used for projects which require scalable processing.

It is a state machine-based template, containing default state containers for various stages or blocks. Different transitions are defined to jump from one state to another. A view of the template is given below: –

The different blocks and their functions are explained below: –

  1. Initialization: This state is used to initialize the configuration file and all the other applications that are being accessed in the project. In case of an error (system exception), the flow will move to the End Process state and in case of a successful initialization, the flow moves to the Get Transaction Data state.
  1. Get Transaction Data: This state retrieves the next transaction item to be processed. In case of ‘no data’ is present for processing, the flow moves to End Process state, else it moves to Process Transaction to proceed with further execution.
  1. Process Transaction: This state will perform the actual processing for the retrieved transaction item. There can be three outcomes of processing – Success, System Exception and Business Exception. In case of a system exception, the transaction is retried, in case of a business exception, the transaction is skipped and the next one is retrieved from Get Transaction Data state. Lastly, in case of a success scenario, the flow will again move to Get Transaction Data state to retrieve the next item for processing.
  1. End Process: This is the final state of REFramework wherein all the used applications are closed, and the project is stopped.

Each of these blocks contain invoked workflows holding a different purpose. All the xamls within these blocks are placed inside the Framework folder of the project.

The Initialization block

The Initialization block

Below are the xamls present in Initialization block: –

  1. InitAllSettings.xaml: This workflow will initialize and output a dictionary type configuration file which will be referred to in the entire process. This config file is put into arguments and passed between various workflows to access the values within it. The Settings and Constants sheets are read from the Config file, which is placed inside the Data folder of project. Assets are taken from the orchestrator itself. A try catch is implemented to catch any system exception and move the flow to End Process state.
  1. KillAllProcesses.xaml: This workflow is used to close or kill any background or foreground application running so that your process starts with a clean environment and no interference happens in further execution. Closing all applications is recommended instead of directly killing them because it might cause abrupt behaviour.
  1. InitAllApplications.xaml: This workflow is used to open up or start any processes or applications which your process might use later, such as activities like Open Application or Open browser. You can also open up any website whose URL can be mentioned in the Config file.

The Get Transaction Data block

The Get Transaction Data block

Below are the xamls present in Get Transaction Data block: –

  1. GetTransactionData.xaml:- This workflow will get a transaction item to process it from Orchestrator queues, databases, mailboxes, etc, depending on the type of method used to push data. If there are no items present for processing, the flow shifts to End Process state. By default, Orchestrator queues are considered as the source of transaction data. If queues are not being used in your process, then replace the Get Transaction Item activity with the appropriate sequence.

The Process Block

The process block

Below are the xamls present in Process block: –

  1. Process.xaml: This workflow holds the actual processing that is to be done in your process. You can include multiple sequences or workflows within this block, which support your execution. The main part of your automation lies here. This part will be followed for every transaction item that is retrieved.
  2. Process.xaml: This workflow holds the actual processing that is to be done in your process. You can include multiple sequences or workflows within this block, which support your execution. The main part of your automation lies here. This part will be followed for every transaction item that is retrieved.
  3. Process.xaml: This workflow holds the actual processing that is to be done in your process. You can include multiple sequences or workflows within this block, which support your execution. The main part of your automation lies here. This part will be followed for every transaction item that is retrieved.
  4. Process.xaml: This workflow holds the actual processing that is to be done in your process. You can include multiple sequences or workflows within this block, which support your execution. The main part of your automation lies here. This part will be followed for every transaction item that is retrieved.
  5. Process.xaml: This workflow holds the actual processing that is to be done in your process. You can include multiple sequences or workflows within this block, which support your execution. The main part of your automation lies here. This part will be followed for every transaction item that is retrieved.

The End Process block

The End Process block

Below is the xaml present in End Process block –

  1. CloseAllApplications.xaml: This workflow ends and close all the applications which were initialized in the beginning of the process.

Leave a Reply

Retype the CAPTCHA code from the image
Change the CAPTCHA codeSpeak the CAPTCHA code
 

SOAIS - Worksoft Newsletter

To view on your browser, click here
Facebook Twitter LinkedIn
Dear Default Value,
 

Welcome to SOAIS Newsletter of September 2021!

Continuous Testing with Remote Execution
 
The speed of innovation continues to increase, driving rapid and relentless change for today’s ever-evolving IT landscapes, creating greater risk as IT and business teams scramble to ensure timely delivery. How can your organization keep pace? Test more, worry less. With Worksoft’s Connective Automation Platform, you can easily build and maintain automated tests, accelerating testing time without losing scope or volume. You can schedule and execute remote, continuous tests to intercept defects sooner and prioritize remediation - without sacrificing your nights and weekends. Explore how continuous test automation and remote execution can empower your organization.

Click here to connect with us to get more information on our services.
 

Skip Costly Rework with Dynamic Change Resiliency​

Change resiliency is imperative in ever-evolving IT environments. Our patented object action framework streamlines change management by assigning object definitions to your shared assets. The same object may be used in a thousand automation steps, but it can be easily updated by making one simple change to the model definition. The change automatically propagates to every single instance where that object may have been used without a single line of code or manual human involvement. For more change readiness you can also engage our Impact Analysis for SAP to predict how changes in SAP transports will affect your business processes. 

Please click here to watch the video to get a gist.
 

SOAIS Blog – Nuts and bolts of Certify Database Maintenance​

One of the key thing, which is often missed by the organizations, who have invested in using Worksoft Certify for automating their Business Process Validation initiatives, is implementing a Database Maintenance Plan. While the business and the test automation consultants get excited about the shiny new thing that they have got and start building the regression suite; planning and executing a database maintenance plan for most of the customers gets pushed down the priority list. However, since all the test assets in Certify are stored in a Database, a robust database maintenance plan is very important to maintain smooth operation of Certify with acceptable performance criteria. The customers usually start facing issues once they have built significant number of Certify processes which they have started executing on regular basis. Such executions add a lot of data to the tables storing results data and increase the overall size of the Certify database.

Please click here to read the complete blog.
 

Worksoft Blog – Process Intelligence: A Multi-Dimensional Approach

The ability to extract process knowledge has become easier through the years. Technology has evolved to the point where we can deploy capabilities that connect at multiple levels to extract different types of process insight. In the past, organizations were forced to spend enormous energy extracting data manually from different applications and databases. Then, they would have to use things like spreadsheets to transform the data and convert it into meaningful information. 

Please click here and read the complete blog.
 
India
Unit 9, Level 5, Navigator, ITPL,
Bangalore - 560 066.
Phone: +91 80 40071234
US
Suite 101, 1979, N Mill St,
Naperville, IL 60563
Phone 1-800-262-2427
Please click here to Unsubscribe / Unsubscribe Preferences

Leave us your info