Document Extensions

[jpgilchrist]

I'm intrigued in this project. I see it's pretty much just you driving this project. Kudos to you. It's very difficult to document, test, write new code, and maintain a project on your own. So, you may not have time to do this, but I figured I'd ask. I see you have extensions used in the examples for the instantiation of the Engine.

Would you be able to document this a little further. I have a hunch, that the extensions is what I would need to use in order to incorporate a DB for persistence.

Couple additional questions:

• if extensions is not the right place for applying db persistence, do you have a recommended approach.
• any idea if it would be feasible to provide the ability to "getImage" of the current state of an activity (similar to camunda)

[jpgilchrist]

I see bpmn.io has the bpmn-image package, which I can use for that.

[paed01]

I have added an example on how to persist state through an event listener (b3a05fd).

Since BPMN flows can be quite extensive it's kind of hard to know when to persist state automagically. But, one approach I have used is to build persistence into the flow itself by decorating an activity with an extension. Then add an extension function to let the engine know how to handle that extension.

[jpgilchrist]

Interesting, I appreciate the feedback.