Playbooks: Saving examples with parameters and transitions

[Ian_Stack]

Background Info: I have a default flow which triggers a playbook (1 of 4 playbooks) the series of playbooks act as a virtual sales agent. From there the final playbook carries the params and into the final flow.

Question: When saving an example from the test simulator, it does not include the:
a.) Next playbook or flow that was triggered
b.) Does not include the parameters.

When saving an example, do we need to include the transition? if so what do we put as the state of the playbook of the newly transitioned playbook (can't be pending as it won't allow it to save)

And do we need to include the parameters as well?

[Homer-Ross · Accepted solution]

When you save an example from the simulator, it only captures what happened within the current playbook, transitions and parameters passed to the next playbook or flow aren’t saved automatically.

If you want a test example to reflect a transition, you’ll need to manually include the next playbook in the sequence by adding a playbookState object in the example JSON. That state can’t be pending, like you said, usually I just set it to something neutral like start or whatever the entry state is for your target playbook.

As for parameters, yes, you’ll need to explicitly include those too. The example won’t carry over context unless you define the key-value pairs under the params section. I’ve gotten around this by copying them from the logs after running the full test once, then injecting them into the example manually.