According to UiPath Best Practices, the For Each activity should be used for implementing the Classification Loop in the high-level solution diagram. The For Each activity enables you to iterate through a collection of items and perform an action for each item. In this case, the collection of items would be the invoices from various clients that require processing. The action for each item would be to extract data using the ML model, process the extracted data, update the information in the storage bucket, upload or move the SharePoint files, and add the document path to the processing queue. Alternatively, if the extracted data is not processed, the action would be to create a validation in the Action Center and wait for the SME to review it. The For Each activity is suitable for this scenario because it allows you to process each invoice sequentially and handle any exceptions or validations that may occur. The For Each activity also has a Body property where you can add other activities or invoke workflows that are relevant to the Classification Loop logic. References: For Each - UiPath Activities, Design Best Practices - UiPath Documentation Portal, Automation Solution Architect - UiPath Academy
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit