Dussehra - Special Offer - Upto 50% OFF | OFFER ENDING IN: 0 D 0 H 0 M 0 S

Log In to start Learning

Login via

  • Home
  • Blog
  • UiPath Reframework architec...
Post By Admin Last Updated At 2020-09-21
UiPath Reframework architecture and usage

UiPath is a global leader in the RPA market that offers complete software solutions to business organizations for automating their processes. For this, it uses UiPath reframework or Robotic Enterprise Framework. The UiPath reframework is useful to the developers to build quick and efficient RPA processes. Moreover, by using this reframework many businesses benefit from getting rid of human errors within processes.

Let us go deep into this blog to understand about UiPath reframework and its architecture along with its usage.

What is UiPath Reframework?

Reframework or Robotic Enterprise Framework is a template project useful for building automation workflows for organizational deployments. The UiPath framework is built on the templates of static systems. The UiPath reframework is an addition to the existing one. Reframework helps to make the developer’s job simpler, smarter, and easier. There are different types of templates that Uipath reframework offers. By using these templates, developers can make complex automation tasks easily. Moreover, it saves a lot of time for the developer to think over different processes and designs.

The templates in this framework offer to read and store the config data, applications needed, etc., features. Furthermore, it also logs all the status relating to the various transactions happen. Thus, using this framework a developer can create wonders in his job process.

UiPath Reframework Architecture

UiPath ReFramework architecture includes four different stages. Such as;

  • Init (Initialization)
  • Get Transaction
  • Process Transaction
  • End Transaction

It includes a main.xml file that uses the state machine workflow. Here, each stage links with other states for the process of workflow.

However, the system can be in a single state at a time. In this case, at least one transition condition from a given state must be true for it to move to another state. In case, it fails in any of these states, the ReFramework is there to use it in a different way. It may be either to retry it or end the process and send a deviation log with the relevant reason.

However, UiPath ReFramework architecture includes 3 state activities. Such as, one final state action and seven transitions are there. Here, each state is linked to another state with transitions.

Get hands-on experience on UiPath reframework with expert knowledge through the UiPath Online Course at Onlineitguru.

Now, let’s understand each stage of the UiPath reframework in a better way:

Init -

Init or initial state is useful to read and store the config data within the dictionary. It closes all the unimportant apps and opens the required one only. We will take an example of this. In case, in the process, we need to upload an attachment within SAP. At first, we need the robot to collect the login details from Orchestrator. Later, we have to open the SAP application and then log in to that using the login details.

The best part of UiPath ReFramework is that the users can start all the applications important within the Init state. Later, if the conditions that have built are met, the robot will move forward with transaction processing.

In case, there is an error while starting the applications or the login details provided are invalid. An anomaly notification will be sent from Init State to end the process.

Get Transaction -

This is the recovery state useful to get the transaction from the queue, folder, data table, and other sources. Once the robot is successfully started it needs all the applications necessary for a process. Hence, it focuses on any transaction items within the Orchestrator Queue for processing.

UiPath ReFramework pre built function inspects for a Stop Request. This will end the process despite there are items still in the Queue for processing. Moreover, it becomes useful in conditions where users notice the Bot is not working as expected to do. Thus, users want to stop the process before it works on any other transaction items.

Process Transaction-

The process transaction is the state where the transactions are fetched from the earlier state. Further, in case there is no data to process, the Bot automatically moves to the end process state. In case, the user looks again at the document attachment within SAP example, The Bot that has now got the Transaction Data from the Queue should now upload the attachment to SAP.

Within the Process State, all the activities necessary to attach the document will be called on. For instance, a workflow inspects whether the document exists or not on the Shared Path, a workflow including activities like clicking on suitable GUI Elements for the robot to direct through SAP, type within the file path, and look for the confirmation that the document has been attached.

Re Framework includes prebuilt SetTransactionStatus workflow useful to set the Transaction Status of an item. This is useful to either success, Business or Application Anomaly. Later, among them, Business Anomalies are prebuilt deviations. They are built into the script and examined by a robot.

After the completion of the transaction successfully, the bot will now move forward with the next Queue item.

End Transaction-

The “End Transaction” is the final stage of this framework that stops the bot successfully and closes all the apps. After the robot completes the processing of all the transaction items from the Queue, it will log out itself. It will move out whether the transaction is failed or successful.

UiPath Reframework examples

Let’s discuss some of the most common examples where Uipath Reframework is making things easier for the business units.

Web Scraping 

The re framework structure is much useful in web scraping. Whenever users need to scrap data from multiple locations and want to feed them in a particular excel sheet. Such as in the case of stock markets, e-commerce, and others for a particular purpose within a large scale, then it becomes very useful in making the process fast and error-free.

Inventory management

Many retailers rely on their old legacy systems for stock management. The re framework robots can execute regular checks on the systems providing data on key metrics. Such as items with low stock levels or the stocks changing continuously are the examples.

Customer/User onboarding

In many B2C business enterprises, customer onboarding is very difficult. And using this automation framework, customer onboarding activities can be finished at once. It is much useful in businesses that depend on legacy systems that largely improve the consumer experience.

Generating huge emails

A huge number of emails depending on the data from different systems are tenacious to generate manually. Hence, for businesses that need to send them frequently, this automation framework helps to ease the process.

Online loan applications process & validation

Users can use this framework to build mediator robots between the online system and the mainframe. It uses business logic to ask the user to fix invalid entries. Moreover, it allows for making loan decisions and produces confirmation letters.

These are the deployments that can be seen on large scale in manufacturing, healthcare industries, banking, E-commerce, and many other industries.

UiPath Reframework Features

The UiPath reframework includes many different features and gives the maximum advantage of using it.

Reusability

The framework works for any type of process and business. Moreover, as the logic code is detached from other aspects of this Reframework it is again reused effectively.

High Scalability

UiPath Reframework has the ability to work on the failed transaction several times and send anomaly notifications. This makes the framework highly scalable.

Effective logging

The framework provides an effective logging process to look after the process and problem management.

Error screenshots

Uipath ReFramework includes the function to take a screenshot of the screen at the point of failure. This feature informs the user to know the ignored automation and overall troubleshooting.

Anomaly Handling

ReFramework easily handles the anomalies that occur while in the process. It includes the feature to take action when an anomaly comes. This makes the user not to worry about process standby or anything else.

Consistency

The variables, assets, and settings are constant across UiPath ReFramework. It makes this easy to understand well. Moreover, the code standards also enable an easy handover to another developer.

Uipath re framework exception handling

UiPath reframework provides a high-level exception or anomaly handling appliance to the users. It does so by retrying a failed transaction, application recovery, and by ending the process. It actively works where continuous running the robot may do more harm than good. Moreover, Uipath reframework allows users to put the external settings in a Config.xlsx file. And also allows the Orchestrator Assets instead of hard coding configuration.

The exception/anomaly management mainly deals with handling errors with respect to different activities within UiPath. Error handling action provides four different options. They are Rethrow, Terminate Workflow, Throw, and Try Catch.

  • The Rethrow option is useful when users want activities to appear before the anomaly is thrown.
  • Terminate workflow activity is useful to terminate/end the workflow the moment the task faces any error.
  • Throw activity is useful when the user wants to throw an error before performing the step.
  • Try Catch activity is useful when the user wants to test something and handle the anomaly likely. So, whatever a user wants to test he can put it within the try section. And then if any error comes in, then it is managed using the catch section. It is based on the user input to the catch section. Apart from the try-catch, the user also has a ‘Finally” option. Moreover, this is useful to mention those actions that need execution after the try and catch blocks are performed.

When users do not provide the name to the activities:

This is often noticed that all the people who work on UiPath reframework just drag and drop the actions. But nobody makes an effort to name those actions taken. This makes it difficult to understand the source of errors.

Solution:

The easiest and simple solution here is to use the name of the actions taken. Once users name the activity, they will not get any error that Main has thrown any anomaly. But they would see that the name of action has thrown an anomaly.

When another application is open in front of the main application:

It happens sometimes when the users work on the “N” number of applications on their system. But, when they perform the project they forget to ensure that the main app in which the automation has to be done is still open. Besides, no other window or application is open in front of that app.

Example: If the user wants to scrape data from a website and if he has Notepad++ open in front of that. Then the UiPath will not be able to execute the automation process.

Solution:

To avoid such type of errors, users have the below options like:

●      Making the main app visible to others and close all other windows or apps.

●      If the user has any click activities, then modify the Input Method, and select to “Simulate Click”.

●      Moreover, users can make sure that the right selector values exist. Hence, UiPath is guided to the right window. This helps it to perform the automation process.

When the user has timing and synchronization problems:

This happens occasionally that the users rely on some other application to execute some task. And that application may take much loading time. In such conditions, if the user does not mention the waiting time, then UiPath presumes that the application is not opening and throws an anomaly.

Solution: To manage those errors, specify the wait time within the Timeout MS parameter. The default value would be around 30. Apart from that if the user wants to manage syncing problems, then he has the below three options:

  • Element Exists Activity – The element exists activity returns a TRUE or FALSE value based on the presence of a particular element. So, the user can use this if he just wants to ensure whether an element exists or not.
  • Find Element Activity – This action will stop/end the automation process until an element is found.
  • Wait for Element Vanish Activity – This action waits for an element to vanish before continuing.

||{"title":"Master in UiPath", "subTitle":"UiPath Certification Training by ITGURU's", "btnTitle":"View Details","url":"https://onlineitguru.com/uipath-online-training","boxType":"reg"}||

When the user’s browser gets crash:

Sometimes, when the user works with the browser and it gets crashes. In such conditions, UiPath reframework will not understand the dependency of the data. It will just throw an anomaly that it cannot load or open.

Solution:

To resolve these types of errors, users can use a Try-Catch block. Hence, users can put the browser part within the Try section. Later, they can either put a Message box or any other activity within the catch section. After this users can specify the important activities, within the “Final” block. Thus, these actions would execute after the Try-Catch block action.

When users don’t select the right activity:

Sometimes it happens that the user may select the wrong activity. For example, if the user searches for each activity. Then he will notice that there are three selections for each activity that may be chosen.

Solution: Select the right activity, likely to the need. To do this, users need to understand the working principle of each and every activity.

Need for Exception handling:

Whenever an anomaly takes place most coding languages and tools will crash the performance of the existing task. This may cause serious issues when users are dealing with sensitive data such as financial transactions.

Hence, users have to eliminate the crash by giving alternate ways of performance. They can also stop the program elegantly with removing the sensitive data. So, either way, are useful here.

Conclusion

UiPath reframework usage gives the developers to make the tasks much easier with automation. This helps the business Org’s to scale higher with faster process delivery with RPA. Thus, it is the best part of the UiPath and also offers many uses with easy to handle processes. Get more insights from the UiPath Online Training through an expert’s voice.