Playbook activity state-mapping rules

Map playbook activity states to states from the given experience record.

Activity state-mapping rules are required for each Experience Status Table. These rules determine how to update the status for an experience record whenever a playbook user updates the state of an activity, such as when they complete an activity.

The out-of-the-box Global Playbook Experience includes default rules for the sys_flow_data and task tables. These sets of rules are enough for most playbook activities, but additional rules can be created for custom tables if needed.

Find the default mapping rules under the Status Mapping tab of a playbook experience.

Figure 1. Status Mapping tab

Experience status mapping records

A Experience Status Mapping record pulls the states (Experience Status value) for the given Experience Status Table. Map from:

• Experience Status to Activity State, or
• Activity State to Experience Status.

The Experience Status to Activity State tab controls which activity state is shown in a card for a given experience status record value. The Activity State to Experience Status tab controls how the experience status record is updated when a playbook user updates an activity state, such as skipping an activity.

Figure 2. Bidirectional status mapping between flows and playbook activity states

Note:

There is always a default set of activity states, but the set of states for an experience record depends on the table in your activity definition.

Figure 3. Task Status to Activity State Map and vice versa

Note:

The number values shown indicate these task statuses:

Default playbook activity states will always be set.