A B Testing Workflow
This workflow models comparing two versions to see which performs better.
This workflow models keeping large payloads external and only passing references.
user { # User
n1: circle label:"Start Claim Check"
n3: rectangle label:"Validate Claim Check conditions"
n5: rectangle label:"Record Claim Check outcome"
n7: circle label:"End Claim Check"
n1.handle(bottom) -> app.n2.handle(top)
n3.handle(bottom) -> app.n4.handle(top) [label="Processed"]
n5.handle(bottom) -> app.n6.handle(top)
}
app { # App
n2: rectangle label:"Receive Claim Check event"
n4: rectangle label:"Execute Claim Check action"
n6: rectangle label:"Monitor Claim Check status"
n2.handle(right) -> user.n3.handle(left)
n4.handle(right) -> user.n5.handle(left)
n6.handle(right) -> user.n7.handle(left) [label="Success"]
}
This workflow models comparing two versions to see which performs better.
This workflow models checking user permissions before actions run.
This workflow models an async operation that notifies a callback when done.
This workflow models rolling back work when a later step fails.