Introduction to Uipath Reframework
Re-Framework is a Template that is used to design Automation workflows in a compatible approach for large-scale deployments. Re-Framework Full form: “Robotic Enterprise Framework”. Re-Framework is a template, which provides all the required basic needs of any process Automation, like reading and storing the Config data, initializes the applications, which are being used in the process, gets the transactions and process them, re-try the transactions if it’s required and logging the status of all processed transactions, Failed or successful and close all the applications. It helps developers to build processes Quicker, robust, and apply the best practices. It has many features: proper Exception Handling, Recovery abilities, Effective logging, Reusability, etc. In this topic, we are going to learn about Uipath Reframework.
Why use UiPath Re-Framework?
Re-Framework makes developer’s tasks much easier. It can be used for any type of business process. It can re-try the failed transactions, has the features to re-initialize the applications, and handle the Exceptions accordingly without human intervention.
In Re-Framework, every project has “Main .Xaml file” which uses the State machine workflow. It is used for a better presentation of the process flow.
It is prepared with 3 state activities, 1 final state Activity, and 7 Transitions. Each state has been connected with transitions.
We have 4 stages in Re-Framework.
Init is the first state that is used to initialize the required applications and all the settings by reading and stocking the config data in a dictionary, kill the applications, which are not required, and open the necessary applications.
The finest part of Re-Framework is that has the form in a way that you can make the required applications ready in Init State. If the settings that are designed in the process are not met, then BOT will move to the next state.
If there are any errors occurred while initializing the applications or the data stored in the Config file is wrong, then we can send the Exception warning message from Init State and stop the process.
If Init is completed successfully, then the transaction goes to next State, which is Get Transaction State, or Robot will end the process by displaying a System error
2. Get Transaction Data State
Get transaction Data State: Get Transaction data State is the data extraction method right after the Init state. It is used to fetch the transaction item from Queue, Database, Data Table, Folder, etc.
BOT will look for any transaction item in the Orchestrator queue to process once all the applications are initialized which are required for the process.
Re-Framework has pre-defined components, which look for stop request. BOT will end the process though if there are any transaction items in the Queue. This helps in analyzing the flow and if the user has identified any exception while BOT is processing and the user wants to end the process before it works wrong for other transactions.
If the state has new transaction item data, then it goes to the next state to process the transaction.
If there are no new items, then it goes to the End Process.
3. Process Transaction
It is Used to Process the transactions that are fetched from getting Transaction Data State (Previous state).
If the Transaction is with Success state, where the loop is performed and the next transaction data is taken into the Queue.
The Business Rule occurs when a specific action is performed after which the execution state goes back to the previous state.
The System Transaction Error transaction is used to take all the necessary steps through an error, which means all the applications will be closed and the robot will go back to Init state to initialize the required applications.
Also, in this process state, the documents will be invoked that are required to attach all the activities.
Re-Framework has the prebuilt Set Transaction Status workflow which is used to set the transaction status either Success or failure for each Item.
4. End State Process
It is the final state to end the process after all the states are completed.
Once all the transactions are completed successfully, then Robot goes to the End state process, close all the applications kill the applications and ends the process.
You can see the below screen once you open the UiPath studio.
Examples of UiPath Re-Framework
Re-Framework is the best solution method to use when the user wants to upload multiple documents in a particular website, onboarding or offboarding the user in a company, to scrape the data from hundreds of pages with less time, validating the applications, processing the applications, validating and processing the Invoices, clearing the constant errors in the process.
Let us see a few use cases where Re-framework is used to reduce human effort and make things easier.
Example #1 – Validating and processing the multiple Invoices
If you want to validate and upload, multiple invoices in a particular web application, which are in the format of PDF, Word, and other formats.
Please follow the below steps:
- Add all the required application credentials in Config File.
- Add the required applications URL’s in Config File, which is an easier way than changing the details in the workflow design.
- Store the Invoice forms in particular folders as per the format.
- Validate the invoice forms based on the keywords and upload them in Web Application.
- Re-try if Bot has failed to validate or upload the Invoice file.
Example #2 – Employee/User -On-Boarding/Off Boarding Process
In many companies, It is very difficult to update the User details manually, filling forms when a new employee joins. Employee On-boarding details can be processed very easily within less time using Re-Frame work even though the company is relay on the Legacy system.
Examples #3 – Generating the reports for any network Issue
Many companies have thousands of network servers that are being used for various types’ tools such as monitoring tools, Automation Tools, Remote Executors, Support tools, Data upload tools.
It is always difficult for humans to check manually when those servers utilization is more than the threshold as the checking process involves multiple steps.
In this case, BOT can easily log in to a particular server and check which process’s utilization is more, get exact values, and generate the ticket accordingly as per the steps given in the workflow.
Conclusion – Uipath Reframework
Users can easily automate multiple processes using UiPath ReFramework if you know how to invoke a workflow and managing with state machines as it’s user-friendly and has everything is pre-built functionalities.
This is a guide to Uipath Reframework. Here we discuss why to use UiPath Re-Framework and Re-Framework architecture along with the examples. You may also have a look at the following articles to learn more –