Use activity state-mapping rules to control which activity state is shown in a card for
a given experience status record.
Activity state-mapping rules are required for each Experience Status Table. These rules
determine how to update the experience status record when a playbook user updates an activity
state, such as completing an activity.
Out-of-the-box Global Playbook Experience includes a default rule set for the
sys_flow_data table. This rule set is enough for most playbook
activities, but additional rules can be created for custom tables if needed.
Activity state-mapping rules for a given Experience Status Table are unique for each Playbook
Experience and can be accessed in the related tabs by clicking Status
Mapping. Figure 1. Status Mapping tab
Experience status mapping records
Each Experience Status Mapping record specifies which field on the Experience
Status Tables contains the Experience Status value.
Experience Status Mapping records also have the following related lists.
Experience Status to Activity State rules
Activity State to Experience Status rules
Figure 2. Experience Status Mapping record related lists
The Experience Status to Activity State form controls which activity
state is shown in a card for a given experience status record value. The form populates the
Experience Status Record Value list with the choice values of the
Experience Status Field.Figure 3. Playbook Experience Status to Activity State Map
Activity State to Experience Status form controls how the experience
status record is updated when a playbook user updates an activity state, such as skipping an
activity. The form populates Experience Status Record Value list with the
choice value of the Experience Status Field.Figure 4. Playbook Experience Activity State to Experience Status Map