At the end, an email is sent with the status of the process, if configured.įor transaction-based processes (such as processing all the invoices from an Excel file) which are not executed through Orchestrator, local queues can be built ().If any exceptions are encountered, the Robot either retries to process the transaction a few times (if configured), or it marks the item as a failure and restarts.If any validation errors are encountered, the transaction status is updated and the Robot moves to the next transaction.If the transactions are processed successfully, the transaction status is updated and the Robot continues with the next transaction.The UI interactions to process the transaction data are executed.If no (more) input data is available, configure the workflow to either wait and retry, or end the process.The Robot checks the input queue or other input sources to start a new transaction.It retries a few times if any errors are encountered, then succeeds or aborts.The Robot fetches the required credentials and logs into all applications.The Robot loads settings from the config file and Orchestrator assets, keeping them in a dictionary that is to be shared across workflows.The template is built on a State Machine structure.
The Robotic Enterprise Framework Template proposes a flexible high-level overview of a repetitive process and includes a good set of practices described in this guide and can easily be used as a solid starting point for RPA development with UiPath. A framework helps you start with the high-level view, then you go deeper into the specific details of each process. Starting from a generic (and process agnostic) framework ensures you deal in a consistent and structured way with any process.
Home UiPath Studio Guide Recipes UiPath Studio Activities SDK Reference Guide Reference Changelog Discussions Page Not Found Search API Logs