Contexts

Custom Contexts

Defining your own contexts for a template.

For advanced flows you can define your own contexts. This allows you to define specific flows that relate to a particular aspect of your template.

When to use

If you understand contexts you'll be familiar with the built in contexts default, template, create, manage and all, in particular how they relate to the template and what you are building in Stubber.

Each context relates to a different high-level flow of that the template needs.
When you have some flow that doesn't fit into the built in contexts, then you can create a custom context.

Some areas where custom contexts are very usefull are when there are periodic processes that need to be mapped out, or intermittant housekeeping and administrative processes.

Some Examples

AI Evaulations

A common use case when building AI Conversations is to use a customer context to build out the evaluation flow.
An evaluation flow is another AI Conversational agent that engages with your default flow to test the responses and actions.

Housekeeping

You could create a context called housekeeping that contains actions to archive old stubs, or to send out reminders to users to complete their stubs.

Reporting

You could create a context called reporting that contains actions to generate reports on the data in the stubs.

A/B Testing

Sometimes the default flow needs to be tested with different variations.
A possible solution is to create a context called default_a and default_b.
This allows you to define two different flows for the default context and then you can create stubs in each context to test the different flows.
In this scenario you would also edit the create context to set a new stub to be created in either default_a or default_b context. This could be done randomly or based on some criteria.