actions.md

Actions

Action Life Cycle

Action Create, then...

• User (click) Dismiss → Action state = dismiss, user will never see that action again
  • Dismiss event created
• User (click) Complete → Action state = complete, user will never see that action again
  • Complete event created
• Action definition indicates action is deprecated -> Action state = deprecate, user will never see that action again unless un-deprecated
• Action definition indicates action is disabled -> Action state = deprecate, user will never see that action again unless enabled
• System Completion -> After an integration returns a set of actions, all actions for that content matching the generated action type that were not returned with the set will have an Action state = complete and systemCompletion = true

Completion Consistency Level

The Completion Consistency Level helps the flow of an actions lifecycle so that it may be completed under certain circumstances. After any user assigned to a action completes the actions, the Completion Consistency Level is consulted to determine if the action should be completed for all other users assigned as well.

There are 3 Completion Consistency levels:

1. All:
   • Every user assigned to the action must complete the action before the action state is changed to complete.
2. One:
   • One user assigned to the action must complete the action before the action state is changed to complete.
3. Quorum:
   • A majority of users assigned to the action must complete the action before the action state is changed to complete.