Once a custom module is enabled, the activities you created in it can be added to business processes. However, there is a number of specific considerations regarding custom activities.
Escalation
For custom activities, you need to add an escalation transition to the process. This allows you to avoid errors during the execution of a business process if the module is disabled.
To set up escalation, double-click on the activity on the business process diagram. Open the Error handling tab.
- Notification. Select this option if you want ELMA365 to notify the responsible users in case of an error. Specify these users: the current user, a context variable such as an initiator, a group, or an org chart item. Please note that the current user is the executor who completed the task that is placed just before the custom activity on the process diagram.
- Interrupt. When this option is checked, the system will stop trying to execute the activity in case of an error, and the process will continue along the selected connector.
Map activity context to process context
The context of an activity can be mapped to the context of a business process it is added to. The output parameters can be passed both to process context variables and directly to the fields of any app that is added to the process context.
To configure mapping settings, double-click on the business process activity on the diagram. On the General tab, in Bind output attributes to, select the option you need.
- Process context. The values of the output parameters of the business process activity can be assigned to the context variables of the business process.
- App. The values of the output parameters of the business process activity can be assigned to the fields of an app added to the business process context.
- Variable*. Select an app from the process context. The output parameters of the activity will be mapped to its fields.
Open the Inputs and Outputs tab. Map the activity’s context to a process or app. The mapped variables must be of the same type. For tables, you can also map columns. If you configured a custom binding form, it will be displayed instead of the Inputs and Outputs tab.
Call process vs Start process
The Call process activity type and the standard Start Process activity are similar, but there is a number of differences between them. They are shown in the table below.
|
Call process custom activity |
Start Process system activity |
Tracked in the Process Monitor |
No |
Yes |
The history of each step is available to users |
No |
Yes |
Asynchronous start |
No The transition to the next step of the business process is possible only after the business process activity of the Call process type is completed. |
Yes You can continue running the main process without waiting for the subprocess to finish. |
Display |
Activity does not appear in the list of processes in the Administration workspace. You cannot start it directly in the ELMA365 interface by clicking the Start Process button. It can be executed only by an activity of the Call process type |
Independent business process. Displayed in Administration > Business Processes. |
Update a business process activity
When a module is updated, business process activities may also be updated. Outdated activities cannot be used on new process diagrams. They will no longer be available on the right-side panel of the business process designer. However, outdated activities will continue to work as usual in previously created processes. When you modify the logic of a process with an outdated activity, for instance, change its participants, you will see a warning that the process contains outdated activities when you publish the process.
Found a typo? Highlight the text, press ctrl + enter and notify us