Btw, I noticed that the Condition Expression Language property is forced to http://www.jboss.org/drools/rule.
If I replace it to null and I save changes, then I will find the above url as soon as I will refresh the diagram.
This in turn raises buil package errors when the associated Condition Expression property does not refer to rule syntax (for example, a plain java boolean expression).
First, we are putting alot of time into adding designer documentation, so bear with us until this is done. In addition we are working on pretty editors for process and node properties - currently alot of them are text-based.
To answer your questions:
** process variable types **
Under Properties(BPMN Diagram), your process properties you will find a property called "Variable Definitions" where you can define process variables. Here you can define both the process variable names, as well as their type. For example if you enter there:
this will produce the property definitions:
<bpmn2:property id="x" itemSubjectRef="_xItem"/>
<bpmn2:property id="y" itemSubjectRef="_yItem"/>
as well as the corresponding item definitions with the provided structureRef attribute values:
<bpmn2:itemDefinition id="_xItem" structureRef="java.lang.String"/>
<bpmn2:itemDefinition id="_yItem" structureRef="java.lang.Object"/>
So the sructure follows $varName:$varType and the whole list is comma-separated
** Condition Expression Language **
Yes, if you do not enter a value in this field, Designer will default to http://www.jboss.org/drools/rule. You can enter in values here which are either "drools" or "mvel". For script tasks and onEntry/onExit actions of tasks, the allowed values of the script language are drools and java, with the default value set to http://www.java.com/java if you do not enter in the value
Hope this helps.
Thank, that's what I was missing.
>>> Yes, if you do not enter a value in this field, Designer will default to http://www.jboss.org/drools/rule <<<
No, I tried several times to edit that field and to save changes: the above value appears hardcoded whether I put anything or not.
Raised Jira JBPM-3323.
Another issue concerning constraints: according to the users manual, priorities play an important role for xor/or outgoing branches.
There is a priority field on Eclipse plugin branches, but I cannot find any equivalent property in the Designer.
You are correct. Designer currently does not set the "priority" extension attribute to sequenceFlow elements --> https://issues.jboss.org/browse/JBPM-3324. The difference is going tobe that you would set the priority on the sequence flow itself, rather than the gateway as you do in Eclipse now.
Hope this helps.