summary

Enterprise process template is a robust and scalable Process template (hereinafter referred to as "template"), which draws on many successful RPA project practices: initialization Process starting point, external global configuration, robust exception handling (N retries, fault tolerance), meaningful logging; When implementing a large-scale RPA Process or large-scale deployment, the template can be used as the starting point of the Process, helping the RPA development team / developers reduce the RPA development and maintenance costs, and is conducive to controlling the quality of the implementation process. When it is used in a Process scenario with obvious transactional characteristics, the effect is better.

Facing the specific enterprise domain, the scalability of the template can be completely controlled by the RPA developers themselves. It is completely feasible to breed more upper level (domain specific) Enterprise process template from this template.

What are transactional features?

• The RPA process requires repeated operations to process independent transaction items.
• A transaction item is a single work unit that can be processed independently, and the processing steps of each transaction item are the same.

For example: for a form entry Process, the Process extracts some structured data from the Excel worksheet file specified by the user and enters it into the Web form system correspondingly. If you want to extract the same structured data from other Excel worksheet files, The user needs to perform the process again and take the new file as the extraction source; if a large number of Excel worksheet files are stored in the specified folder, the data in these files are extracted and entered into the form system in a circular manner, such a process scenario has "transactional characteristics", One of the excel worksheet files is a transaction item.

How to use

When using this template, there are roughly the following necessary steps:

1. Analyze the current Process automation scenarios and confirm whether they have "transactional characteristics".
2. If so, it is recommended to create a new Process based on the template.
3. In the new Process directory, open the configuration file Config.xlsx , fill or adjust the configuration values, add new configuration items and values (if any), and confirm the transaction source, such as selecting a data queue in the commander.
4. Open "get new data", finish getting the new transaction item from the transaction source and assign it to the Process diagram variable G_ dicTransactionItem。
5. Open the "execution Process" to complete the processing of a single transaction item, that is, to automate the specific Process steps. It is suggested to control the complexity of the Process and make it easy to adjust the operation and maintenance.
6. Commissioning and testing of the new process to ensure the quality of delivery.