@nikku Is there any way to save the event log of the token simulation in a way that a playback is possible (without having to trigger the play buttons for events, gateway selections, etc.)?
Of course the token simulation can be recorded as video, but that is comparably heavy and prevents any interaction like zoom in/out.
Btw. what is the easiest way for you to create the animated gifs that are used to showcase examples? So far I haven’t found a nice way and any hint would be appreciated.
Yes there is. Essentially any test case is a play back scenario.
Details however really depend on your case. What do you need the record + playback for? How much human interaction is required?
Btw. what is the easiest way for you to create the animated gifs that are used to showcase examples?
I’m a GIF dude so I setup my very own little recording facilities. There does exist a couple of good recording tools out there, simply search for them (depending on your OS).
I am currently still exploring the possibilities and the current advances in the token simulation project are opening multiple avenues (kudos). Some of the use cases I see for me:
Integration in Reveal.js for slidedecks explaining BPMN (possibly via a new plugin for Reveals.js). Here, it would be nice to be able to showcase different token flows for the same process without any user interaction except for start playback/stop playback.
Tutorials for custom extensions of BPMN for which the token flow at custom elements may have a special behaviour.
Visualisation of token flows logged from an execution engine.
I’ll try to understand the test case implementation and will see whether I can make any of the above work.
The logic with triggerElement( name ) and await elementEnter( name ) looks quite intuitive. But where would I put this if I have a setup like this?
Just came back to this and was asking myself whether the API of the simulation support module should support an (optional) parameter for the id of the token to be advanced.
I think this makes sense, aligns with other things we did recently to make the simulation support module more versatile. This would probably not be the TokenID, but the ID of the parent scope.