Q1) Why UiPath is the Best in all Robotic Process Automation Tools?
RPA UiPath is an enterprise computing platform dedicated to automating business process.
It provides the below options full compliance with the enterprise security and governance.
- Process modelling
- Change Management
- Deployment Management
- Access Control
- Remote Execution
- Execution monitoring
Q2) What are the components in UiPath ?
UiPath Studio :
This is mainly used to implement Process, Automation or Bot Designer.
UiPath Robot :
This is used to Execute Process (Run Automation) in the studio
Uipath Orchestrator :
This is Central repository of the Bot. This is Web Based application is used for remote control, governance and execution of robot. i.e deploy, Schedule, Monitor.,
Spying Element Tool – Used to get the selectors
Q3 . Explain UiPath Robotic Enterprise Framework Template in the Main workflow
UiPath Robotic Enterprise Framework Template Main workflow contains 4 States. They are …
2.Get transaction Data State
3.Process Transaction State
4.End Process State
1.Init state : Re Framework main workflow, in this Init state Bot automatically reads configdata from excel or orchestrator and that config data will add to dictionary. It will initialize the application based on configdata. Configdata is in dictionary, in the form of key and pair values(mapped values). We have to use dictionary key values in our process implementation. No need to create Dictionary by default dictionary was created. Just we have to use it. After successfully initialization of the Application it will go to Get transaction Data state.
2.Get transaction Data State:
It reads transaction item that transaction item comes from where the data is store whether data is in Excel or orchestrator Queue. According to config data we have to change Arguments at invoke Get Transaction Data and as same as change It in Argument panel. Replace QueueItem with DataRow (Brose for type…system.Data.Datarow…Select..DataRow) If the Transaction data is in excel. TransactionItem type is QueueItem when data is in Orchestrator Queue. TrasactionItem Type is QueueItem by default at Argument panel. Get Transaction Data State send one by one TransactionItem(Data) to ProcessTransactionState upto end of total Data. After Ending data(There is no data in Get Transaction Data) It will Redirect to EndProcess
3.Process Transaction State:
We are implementing Business logic In this Process Transaction State. Process Transaction State has three connectors..1 Success, 2 Business Exception, 3.System Exception
The transaction successfully is done in this Process Transaction State. It will Redirect to Get Transaction Data to take an other transaction item. Get Transaction Data will send Next Transaction item to Process Transaction State
In case any error Raised in this Process Transaction while processing transaction item this is called as Business Exception. Whenever Business Excepton raised that time It will again Redirect to GetTransactonItem to take an other TransactionItem.
System Exception occur whenever Application is not responding…Etc. It will redirect to InitState to Reintialize the Application. After re initialize the application again, it will go to GetTransactonState. If there is no data in this GetTransactionData, It will be redirected to EndProcess to close the Application.
4.End Process State:
We use this state to close the application
If any system Exception occurs in InitState, it will redirect to EndProcess to close the Application And In Get Transaction Data, After completing all TransactionItems(Total Data)(means no data in Get Transaction state) at this time also Redirect to EndProcess to close the Application.