I'm fairly new to Playbooks and I'm trying to understand the recommended approach for the following scenario.
I have a three-level record structure:
Activity → Task → Action
Conceptually, it's very similar to:
REQ → RITM → RITM Task
An Activity can have a dynamic number of Tasks, and each Task can have a dynamic number of Actions.
Each Action is fairly simple. The fulfiller needs to open the Action, make a decision/set a few fields, and save/complete it. Once all Actions belonging to a Task are completed, the parent Task is marked as completed.
What I'm struggling with is how to represent this dynamically in a Playbook.
Ideally, the Playbook Experience on the Activity would work through each Task and allow the fulfiller to complete all of the Actions belonging to that Task. However, since both the number of Tasks and the number of Actions are dynamic, I can't define them as fixed Playbook activities ahead of time.
Is there a recommended pattern for implementing this with Playbooks?
For example:
- Can a Playbook dynamically iterate over the child Tasks of an Activity?
- Can each Task dynamically expose its related Actions as steps/activities?
- Or should the Playbook live at the Task level instead, with some custom UI/activity responsible for handling the related Actions?
I'm mainly trying to understand the intended Playbook architecture for this type of dynamic parent/child structure.
I tried to look into Activity definition and the related UI Layout record, which has connection to macroponent etc, looking at the built in ones like Form etc.
And I tried adding my own activity definition and create my own UI Layout record, but whatever I do I don't get the UI Layout tab on the activity.
