There are several types of project templates that can be selected to create a new automation project in the Start panel, as follows:
A project template based on a Flowchart, optimized for basic automation processes.
This template contains several pre-made containers, as follows:
This container is connected to the Start node and is meant to hold all the activities related to retrieving the data necessary for running the project. The read transaction parameters are stored in the predefined
NewTransaction variable of type
The Flow Decision activity is meant to analyze the data that was retrieved based on the condition represented by the data stored under the
NewTransaction. The True branch of the Flow Decision leads to the Transaction Processing Flowchart, while the False branch leads to the End Process Sequence.
- a Transaction Processing Flowchart that processes the transaction items and then loops back to the initial Data Input Sequence.
- an End Process Sequence which is meant to contain all steps that must be taken at the end of an automation process, such as saving the workflow.
Please take into consideration that whenever you wish to copy a large number of activities from one sequence to another, it is recommended to scroll down to the bottom of the Designer panel beforehand. This is due to a Windows Workflow Foundation limitation.
Agent Process Improvement is a project template based on a Sequence, that is tailored to monitor a certain trigger such as a mouse or keyboard event and deploy an automation. This sequence contains a Monitor Events activity that contains triggers for clicks, keystrokes and hotkeys, a Get Source Element activity to retrieve UiElement objects and containers for Screen Scraping and Data Entry.
Robotic Enterprise Framework is a project template based on State Machines. It is created to fit all of the best practices regarding logging, exception handling, application initialization and others, being ready to tackle a complex business scenario.
The template contains several pre-made State containers for initializing applications, retrieving input data, processing it and ending the transaction. All of these States are connected through multiple Transitions which cover almost every need in a standard automation scenario. There are also multiple invoked workflows, each handling particular aspects of the project.
User-defined processes or libraries can be saved as templates to be used in other automation projects. Such templates may contain a particular set of dependencies and built-in workflows with already defined variables and arguments that can later be used in various projects.
Private workflows part of library projects are also included in templates.
The Save as Template button is available in the Ribbon and it opens the New Template window:
The project’s name in the list of templates in the Studio Backstage View.
The template’s description in the list of templates.
Default Project Name
The default name of the project to be created using this template.
Default Project Description
The default description for the project to be created with this template.
The New Template window also displays a Preview of exactly how the new template looks like in the Start panel. The templates are arranged according to the most used or recently created.
Unsaved changes made in files are automatically saved in the project before the template is created.
Templates may be permanently removed from the Start panel by clicking the Remove Template button next to the template.