Quick Actions
The CMS feature allows you to create the start process custom action or dynamic link for a CMS items. This feature allows you to start a process from a CMS items list. For example, when you want to send mailings from your contacts list.
You can now also map data to a specific property in case there are multiple possiblities.
As a result - User can Quick actions dropdown with added items:
Also User has ability to highlight quick actions:
Filter icon allows you to manage the selection conditions for the process to be started (e.g. only allow to start a mailing, if the contacts selected all have "email allowed" = "yes")
By clicking on the settings "filter" you will get to the preconditions side drawer for the corresponding CMS entity where you can set needed preconditions for quick process start
In case your selection meets with process quickstart conditions, you will be able to start the process, otherwise, the process will be greyed out. To check the conditions you can check the tooltip on hovering the process name and check its requirements by pressing 'View conditions'.
Quick actions — Opening behavior for Start process
1. What it is
Quick actions can be configured on both CMS objects and processes, and they behave differently depending on their type. A Start process action can now open in a modal, the same way Create record does. This is set with the new Opening behavior field.
Use case: a sales rep is making an offer for a customer and wants to add a test drive. They click the "Test drive" quick action, fill in the test drive fields in a modal, close it and are back on the same record to continue their work.
2. Where it is configured
Definition settings → Quick actions → open a Start process action → Opening behavior. The field is available on both CMS objects and processes.
Fig. 1. Opening behavior options.
- The field is optional. When nothing is selected, the behavior is the same as Run in background: nothing opens and the process runs in the background.
3. Run in background
Setup: select Run in background in "Opening behavior" and save.
Fig. 2. Setup: Run in background.
How it works: the user clicks the quick action and stays on the same page. Two notifications are shown: "Starting the process…" and "Process started".
Fig. 3. Result: Run in background.
The user is still on record TEST-30570; the notifications confirm that the process has been started.
4. Open in modal
Setup: select Open in modal in "Opening behavior" and save.
Fig. 4. Setup: Open in modal.
How it works: the started process opens in a modal on top of the current page. The user works with it there (for example fills in the manual task fields) and closes the modal with the X in the top right corner to return to the record they started from.
Fig. 5. Result: Open in modal. The new process TEST-30572 is opened in a modal on top of record TEST-30570, which stays open in the background.
5. Redirect
Setup: select Redirect in "Opening behavior" and save.
Fig. 6. Setup: Redirect.
How it works: the user leaves the current record and is taken to the page of the started process. To continue with the original record, they have to navigate back.
Fig. 7. Result: Redirect. The user is on the page of the newly started process TEST-30574.