Variable modification restriction + form generation

[juanignaciosl]

I miss some data restriction specification at jBPM. I think defining restrictions like "variable x can only be modified at task A" it's quite neccesary. The "task forms" feature could be an option, but I don't actually want to open jBPM console to final users.

I think I'm going to implement a variable-task permission matrix plus an automatic form generation in order to do this, but it's hard to believe there's nothing already done...

Any ideas?

[kukeltje]

This was in jBPM 3 and I have no idea how much it was used. It was not implemented in jBPM 4 and there does not seem to be a issue in jira. There is one for variable declaration and I would not mind if you made a jira issue for this.

Even better would be if you want to discuss the thing you want to implement in the dev forum and maybe contribute it?

Personal remark:

I'm more in favour of using





and all should support EL for the value, not just static booleans

[kukeltje]

Sorry...

Personal remark:

I'm more in favour of using

<variable read="true" write="false" required="true" name="var1" />

instead of

<variable access="read,required" name="var1"/>

and all should support EL for the value, not just static booleans

[juanignaciosl]

Ok, I'll do it as soon as I have a design for it. Your idea seems similar to what I was thinking on.