When you create processes, you have many choices to make and questions of style to consider. This chapter recommends guidelines and defaults for automating workflows with Signavio Workflow Accelerator. You can use these guidelines, with your own modifications, to help a team create processes more consistently without forgetting things.
Key: 😀 usability, ⚙️ maintainability, 🌸 cosmetic
- 😀 Set a process name that summarises the process goal for one case as an active verb phrase.
- 😀 Select one or more labels to categorise the process.
- 😀 Use the Process description field to document the process goal, as a single phrase describing the desired outcome.
- 😀 Set the Case name template to generate a concise readable unique name for each case.
- 😀 Restrict See process permissions for processes that are quick experiments, to avoid filling the Processes page with processes called Test
- 😀 Restrict Start process permissions for processes that are under construction and not yet ready to be used.
- 😀 Restrict View cases permissions for processes whose cases include sensitive information.
- ⚙️ Specify access for organization groups instead of individual users, so you can edit groups to grant access, including for existing cases.
- 😀 Include a form trigger by default, rather than using a manual trigger.
Form trigger - Form¶
- ⚙️ Description field: add a Markdown heading to describe creating a new case for this process, e.g.
# Submit new change request.
- 😀 Button label to start new cases: customise the start button text to either describe the action that starting a case represents, e.g. Send feedback, or to describe the submitted form, e.g. Submit vacation request.
Form trigger - Confirmation message¶
- 😀 Add a confirmation message, when the first process task is not assigned to the case creator, to indicate what happens next.
- ⚙️ Follow the Signavio BPMN Modeling guidelines.
See also: Signavio Process Manager Modeling Conventions.
- 🌸 Check spelling.
- 🌸 Use sentence case for action names.
- 😀 Name the action with an active verb phrase, e.g. Review request.
- 😀 Make the action name as specific as possible.
- 😀 Name the event after what happened, e.g. Request submitted.
- ⚙️ For processes with more than about ten actions, use Milestone events to identify process phases.
- ⚙️ Prefer exactly one start event.
- ⚙️ Name the event after the new status at the end of the process.
- ⚙️ Avoid multiple events with the same name; instead join the sequence flows.
- 😀 Set the Candidates for this task using users or groups, to generate notifications.
- ⚙️ Prefer specifying candidates using groups instead of individual users, so you can edit groups to make changes, including for existing cases.
- ⚙️ Set Assign using a role for every user task.
- 😀 Use a Task name template to disambiguate repeated task names.
- ⚙️ Prefer roles that match organization roles, captured in Dictionary.
- 😀 Use the Description field to summarise the purpose of completing the form.
- 😀 Start the form with read-only fields that provide context for the information or decision the form requires.
- 😀 Set a Reminder and Escalation by default with relatively long time periods to catch forgotten tasks, e.g. 1 week and 2 weeks, respectively.
- 😀 Escalate to the original candidate group, or a management group.
Send Email action¶
- 😀 Set the Sender name to the role for whoever the information comes from.
- 😀 Set the Reply to address to match the Sender name.
- 😀 Append the case name to the Subject to disambiguate email notifications for different cases.
- 🌸 For regular notifications, consider removing greetings and sign-off, and using concise wording, to make it clear that it is an automated notification and not a personal email, and to reduce reading time.
- 🌸 Use title case for manual decision transition/button names.
- 😀 Order manual decisions with happy path decisions first, e.g. Approve, Reject.
- ⚙️ For automatic decisions, configure one transition as per default, to avoid none of the conditions matching, and to simplify the configuration when there are two conditions.
- 🌸 Use sentence case for field names.
- 🌸 Limit field name length to a few words, and use field descriptions for longer explanations.
- 😀 Remove ‘Enter’, ‘Select’ and ‘Upload’ from the start of trigger form field names.
- 😀 For File type fields, use the default value to provide a document template.
- 😀 For User type fields, use organization groups to specify candidates.
- ⚙️ Avoid duplicate field names.
- 🌸 Remove the default ‘Hello World’ console log statement.
- ⚙️ Adopt a consistent coding style.