Workflow model not saved (what are the minimum requirements to have it saved?))

[gilles]

Hi, I made a (quite simple) workflow with jbpm, and the properties of my workflow model are not saved between the tasks.
I'm setting the properties in a java class that is starting my workflow. And the values are correctly displayed in the (default) form, but I can not save it (in the share UI). Only the 'by default' bpm properties are saved properly.
I'm wondering what are the minimun requirements to have workflow properties handled by the workflow?
Just create the aspect in the workflow model and attach to one task? Do we need to repeat on each task to have it maintained between tasks? Do we need to configure the share-client-config to make it save the modified values? Do we need to save the values manually in scripts? Thanks in advance.

[romschn]

While defining the workflow content model, you can create an aspect containing the specific properties you want to apply on each task. Then there are two ways to have it applied on each task. One is - put them as mandatory aspect on each task. Second is create a base type on which apply the mandatory aspect and have your tasks be the child of the base type.
Then just configure the task entry in share-config-custom.xml, it should save the custom values on the task.

[gilles]

Tx. What I don't understand is that some properties of my workflow model are saved and some are not, although I didn't configured anything in my share-config-custom.xml. So, just by creating an aspect in my workflow model and adding it as mandatory on my tasks, the properties are saved when I click on 'Save and Close'. But not all.?! I will make some tests.

[gilles]

Seems that using hyphens (-) in workflow property names is preventing the property to be saved. Can someone confirm?