-
1. Re: Designer variable definitions and constrains
tomarenz Aug 9, 2011 5:46 AM (in response to tomarenz)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).
-
2. Re: Designer variable definitions and constrains
tsurdilovic Aug 9, 2011 10:32 AM (in response to tomarenz)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:
x:java.lang.String,y:java.lang.Object
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.
-
3. Re: Designer variable definitions and constrains
tomarenz Aug 9, 2011 10:46 AM (in response to tsurdilovic)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.
-
4. Re: Designer variable definitions and constrains
tsurdilovic Aug 9, 2011 10:50 AM (in response to tomarenz)You should be able to type in
mvel
into that property field and have it set to http://www.mvel.org/2.0, can you please check? If this does not work can you please raise a JBPM Jira in https://issues.jboss.org (setting Designer as the component would help a lot).
-
5. Re: Designer variable definitions and constrains
tsurdilovic Aug 9, 2011 11:00 AM (in response to tomarenz)Btw. you and anyone else are more than welcome to contribute any fixes/patches to Designer. To get started, create a fork of https://github.com/tsurdilo/process-designer and we can go from there (you will need apache buildr - http://buildr.apache.org/) installed to build the code.
-
6. Re: Designer variable definitions and constrains
tomarenz Aug 9, 2011 11:03 AM (in response to tsurdilovic)Just tried with BPMN2-ExclusiveSplit, which uses mvel expressions. Same result, after saving http://www.jboss.org/drools/rule comes back always.
I will raise a Jira.
-
7. Re: Designer variable definitions and constrains
tsurdilovic Aug 9, 2011 11:04 AM (in response to tomarenz)You can also reach us on IRC and ask questions there as well - more info here: http://www.jboss.org/jbpm/irc.
-
8. Re: Designer variable definitions and constrains
tomarenz Aug 9, 2011 11:37 AM (in response to tsurdilovic)Raised Jira JBPM-3323.
-
9. Re: Designer variable definitions and constrains
tomarenz Aug 9, 2011 11:59 AM (in response to tomarenz)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.
-
10. Re: Designer variable definitions and constrains
tsurdilovic Aug 10, 2011 12:39 AM (in response to tomarenz)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.