Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • You can name roles specifically created for your solution as you see fit (like "Approver" below), but refrain from using spaces - use underscores instead.



FAB 3.3 UI - Roles
1665pxImage Added

Levels:

  • Level Name should be a noun, and the Status should describe that noun. For example:

...

Please take note that the Level Name and Status fields are used in reporting and audit trail information, and should therefore be chosen carefully.


FAB 3.3 UI - Levels

Image Added


Tasks:

  • Where possible, a Task ID should be defined as a verb. Where necessary, use underscores (but never spaces) in the Task ID. For example:


FAB 3.3 UI - Tasks

Image Added


Note that the Task  ID gets used in the visual representation of the Process Flow (eg START, SAVE_DRAFT, etc.):

...