Automation as a technical bracket
In the future, d.velop process studio will make it possible to bundle individual components into so-called automations. Automations represent a technical bracket in which components belonging to the same topic can be grouped together.
An automation called “Vacation Request” could, for example, include the processes of "requesting vacation" and "canceling vacation", as well as all associated forms, scripts, and business rules.
Displaying automations in d.velop process studio
Overview of all automations
Go to Modeling > Automations to access the overview of automations. Only those automations for which you have permissions are listed (for more information, see Visibility of automations).
The context menu also gives you access to the usual actions such as downloading, editing, deleting, and viewing details.
Creating an automation
Use the + NEW button in the automation overview to create a new empty automation or upload an existing automation.
When creating an automation, you must enter a name and a short description. This is the information that will be displayed in the automation overview.
Once you have created an automation, it will open immediately.
Details of an automation
If you click on a specific automation in the automation overview, the respective automation will open.
The main area displays the components that have already been assigned to the automation. If you click on a component, the respective editor for that component will open. If no components have been added to the automation yet, the overview will be empty.
The All Components option is available in the sidebar under Components. This option is selected by default when you open an automation. You can access the overview of the automation components at any time via All Components. Use the BACK TO OVERVIEW button to leave the automation details and return to the overview of all automations.
Adding components to an automation
Use the + NEW button in the main area to create a new component and assign it directly to the automation. You can also add an existing component to the automation or upload a component and add it directly to the automation.
Important: A component can only be part of one automation. This means that only components that are not already part of another automation are offered in the selection lists.
Visibility of automations
Anyone who has access to d.velop process studio can also create automations. In addition, the previous component permissions apply.
Once an automation has been created, it is only displayed in the overview to persons with the Administration role and the person who created the automation. If several persons are to work with the automation, they can be easily added via the Members entry in the sidebar.
You can select individual persons or groups.
Every person who works on an automation can see all components of the automation. However, access to the components is only possible with the appropriate permissions.
Documentation within automations
Within an automation, there is also a Documentation section in the sidebar under Settings. Here, you can enter any information about the automation in Markdown format.
Click Edit to enter the editing mode for the documentation. Once the changes are saved, they will be rendered correctly in the interface.
Exporting and importing automations
You can download an automation using the context menu in the automation overview.
When an automation is downloaded, the following elements are included:
- Processes, forms, scripts, and business rules that were added directly to the automation
- Information about the automation, such as the name, ID, and short description
- The documentation
Important: An export only contains the processes, forms, scripts, and business rules for which the person downloading the automation is authorized.
Persons in the Administration role can upload a downloaded automation using the + NEW button. After selecting the automation to be uploaded, a dialog box displays the components contained in the file. Here you can select the components to be imported if you do not want to import the entire automation.
If individual components cannot be imported, this will be indicated in the dialog box.
Quickly switch between components using the sidebar
When an automation is open, the components from the automation are also displayed in the sidebar. This allows you to quickly switch between individual components of the automation. The first 4 components are displayed (sorted alphabetically). You can display the other components by clicking Show more.
If you are currently working actively with individual components, you can also pin them so that the corresponding components are directly accessible at any time.
To pin a component, click on the pin icon (Pin element) for the respective components. The pin icon appears as soon as the entry is selected in the sidebar. Pinned components can be unpinned in the same way. The pinned components are saved in the browser and are available again the next time the automation is opened in the same browser.
Display of automations in the overview lists of components
In the overview lists of components, such as forms, you can also see that the respective component is part of an automation via the automation icon. The tooltip for the icon also shows which automation the component is included in. If the person calling up the automation is not authorized to see it, the tooltip text simply states that the component is part of an automation but does not specify which one.
Additional new features in d.velop process studio
Saving sorting and filtering in overview lists
The filter values and sorting settings in the overview lists are now saved within the browser session. This means that these values are retained when, for example, you open a process from a filtered overview list and then navigate back to the overview. If the browser tab is closed, the settings are discarded again.
Name of the current studio area as title for the browser tab
The title of the browser tab in which d.velop process studio is open now has a descriptive name instead of d.velop process studio. The title of the browser tab is now the name of the studio area that is currently open. This allows you to see what you are currently working on from the title of the browser tab without having to open the browser tab.