a6e5b969-be6e-4756-ae53-47d3cb899ca4.png

360e968e-8a87-4b54-9882-cab6be089b4f.jpg

Technical Account Manager

a76bd2f0-9e67-4103-8252-b2deb466a53f.nupkg

1. Storing values and asset names in a config file - loading them into the config dictionary.

One of our recommended best practices is to start each automation using a template.  In essence, it doesn't make sense to start with a blank project in most cases.  Using a template creates reuse and adds functionality to your automation with minimal effort.  

There are different profiles for automations that determine what template is best to start with.  For instance, if you are processing many transactions or you want to split the work across many robots you would use RE Framework as the template.  Many customers customize the RE Framework and make their own versions as well.  

Many customers create automations that don't have transactions.  Maybe they run a couple of reports in the ERP and combine them in Excel.  Maybe it's a single transaction per day.  Particularly when the COE program is just getting started, the big templates can be intimidating and quite unnecessary for that automation described above.  At the same time there are basic functionalities that are also best practices that you don't have to recreate in every new automation.

This template can be used when there is only one transaction and a queue is not required.  It provides best practice features:  

1. storing values and asset names in a config file  - loading them into the config dictionary.

This template can be used when there is only one transaction and a queue is not required.  It provides: config file, retry, exception handling, and exception screenshots.

Simple Single Transaction Process Template

Simple Single Transaction Process Template