Persisting of modified properties

[lindleycb]

Possibly related to #16 and #17, we've been using your BPMN engine successfully now for a number of months with no glitches, but we recently had a requirement to modify rather than add one of the properties on a process instance. When we do this using setProperty, it shows as modified when using getProperties, but is left unchanged in the database. If there is a simple fix for this, we'd very much appreciate a patch.

[TomKaltz]

did you ever figure this out?

[lindleycb]

Hi Tom, I'm afraid not. We ended up working around it for our use case by writing the property change directly to the database ourselves as well as calling setProperty but an official fix would be better. It looked like setting the property and then triggering an event saved OK, but just setting the property without any form of state transition didn't persist.