DataCollector and Processor

Please note: We will shut down the Helpdesk soon. Please update your releases to Hyland RPA 22.2. To view the latest documentation for Hyland RPA 22.2 release visit Hyland Docs.

To enable high scalability with your automation, we differentiate between two process types: the DataCollector and the Processor. In this section, we would like to describe the interaction between these two types.

The DataCollector (DCO) collects all available tasks on a predefined frequency. The DCO is triggered by any defined event. An example of this could be when the clock reaches 8:00 or every 30 minutes, for example. The DCO then begins to evaluate all work items in the inbox. This could be Outlook items, Workitems in SAP, or new rows in an excel sheet, for example. Depending on your predefined rules, the DCO then creates a Processor-task (PRO) on the database for every work item, labeling it with a unique identifier such as a MailID, a ticket ID, etc. The DCO’s primary purpose is to create and supply the database with those tasks, and once it is finished, it will close each application. The Processor tasks are now created and can be executed. Depending on their skills, the robots will, as soon as they are out of work, pull the next processable task. In this case, skills are defined by the licenses and authorizations a client has in their unique system.


When creating a new project, you have always the ability to choose your type of process in the skeletons (1) and also in the workspace (2).




Was this article helpful?
0 out of 0 found this helpful