![Logo.png]](https://help.demostack.com/hs-fs/hubfs/Logo.png?height=19&name=Logo.png){kind=logo}
Stateful Demo Flows
When a demo flow is cloned that has a beginning and end state, we will sometimes see the end state first on playback.
As an example, let's pretend we cloned a shopping application with an "Add to Cart" button. When we start cloning, our shopping cart is empty. We add an item to the cart and end the clone. Upon playback, we see that the shopping cart is full even though while cloning we had to trigger this action.
-
-
Start State = Shopping Cart Empty
-
End State = Shopping Cart Full
-
How do we configure the playback correctly?
We can simplify these actions by considering what needs to be triggered and what depends on that trigger. In the example above, the trigger is the "Add to Cart" button, and the dependency is the Shopping Cart.
Your Demostack support team will create a configuration rule that will advance the state of the dependency ONLY when triggered.
Finer Details
- In most cases, we make these rules using regex patterns, so you don't need a special configuration for every new clone.
- In rare situations we may need to add rules specifically per clone.
- Multi-step flows are also supported. These typically take a little more time to configure due to the complexity.
- The dependency in a stateful flow is always predictable. Using the same example above, if I added blue shoes to my cart while cloning, I will always expect to see blue shoes in my cart after clicking the "Add to Cart" button in playback. However, the trigger is not specific to the blue shoes. I could click the "Add to Cart" button on red shoes, but still see that the blue shoes were added to my cart.
What we need to build the Configuration
- A video recording of the flow while cloning. It's important to know the exact actions taken in order to build a quality rule.
- Access to the application and the ability to reclone the actions multiple times.