Roles:
- You can name roles specifically created for your solution as you see fit (like "Approver" below), but refrain from using spaces - use underscores instead.
- Do not rename System Roles.
In future releases, these will not be editable but until this measure is in place please refrain from changing the System Role names. You may experience unintended outcomes in the event that you do.
...
- Level Name should be a noun, and the Status should describe that noun. For example:
...
- Please adhere to the Fiori guidelines for buttons where possible.
- Try to ensure that the 'main' button (used most often) is defined first, as the buttons will appear in the Process Flow toolbar (left to right) as they are defined in the designer (top to bottom).
System
...
(background) tasks:
- We recommend using System Tasks where an action (approval, document posting, etc.) may require authorisations that the current user may not have. Note that when using a system task, no feedback is presented to a user - this will have to be catered for explicitly in your solution. You can set a task to be a system/background task by clicking in the "More" button on the Tasks tab (far right):
: