These errors go away once the User Task variables "Task Name", "Priority", etc. are set. I assumed these were all mandatory. Please let me know which ones are mandatory and which are optional. Also, I suppose this error could be a little more descriptive, such as "The User Task attribute 'Task Name' is missing" etc.

Would it be acceptable to provide reasonable default values (even if they're just an empty string) for these I/O Parameters so the validation problems go away?

@Bob - task name is mandatory but I'm not so sure about the others. That would be a good question for Kris. 

Anyway - default values non-mandatory attributes are fine by me.

@Kris - could you please specify which attributes are considered mandatory from the engine perspective?

Thx!

Hi Bob. Modeled process is still not valid, even if I fill all fields like 'Task Name', 'Priority' etc. I think the reason is this:


BPMN2 modeler currently generates for each user task:

<bpmn2:userTask id="UTID" name="UTName">
...
<bpmn2:dataInputAssociation id="_DataInputAssociation_9">
    <bpmn2:targetRef>_DataInput_8</bpmn2:targetRef>
</bpmn2:dataInputAssociation>
<bpmn2:dataInputAssociation id="_DataInputAssociation_10">
    <bpmn2:targetRef>_DataInput_9</bpmn2:targetRef>
</bpmn2:dataInputAssociation>
...
</bpmn2:userTask>

I think, it should be like this:
<bpmn2:userTask id="UTID" name="UTName">
...
<bpmn2:dataInputAssociation id="_DataInputAssociation_9">
    <bpmn2:targetRef>_DataInput_9</bpmn2:targetRef>
</bpmn2:dataInputAssociation>
<bpmn2:dataInputAssociation id="_DataInputAssociation_10">
    <bpmn2:targetRef>_DataInput_10</bpmn2:targetRef>
</bpmn2:dataInputAssociation>
...
</bpmn2:userTask>

Hi Jozef, can you attach the process to this BZ? I'd like to take a look at it. It's possible that the Data Inputs align with the Input Associations positionally but don't have the same sequential ID numbers.

Created attachment 984394 [details]
usertask skippable

Hi Bob. Theory about wrong ID's was my mistake, sorry for that. My confusion origins from attribute 'Skippable'.

Currently:
If I create process with 'User Task' node, attribute 'Skippable' is not checked by default. I consider this logically equivalent to false. But in fact, If I want to set 'Skippable' to false, I have to check it to true, then uncheck it back to false and save process. 

Desired behaviour:
I think, at least attribute 'Skippable' should have default value 'false', because currently setting it to false is very counterintuitive. 
In general I agree with empty strings for non-mandatory attributes.

In the attachment:
UserTask.bpmn2 - generated process, no property changed for any element
UserTaskSkippableFalse.bpmn2 - 'Skippable' set as false

Both files are logically equivalent if I compare their properties in 'Properties view'. But 'UserTaskSkippableFalse.bpmn2' is created from 'UserTask.bpmn2' after chcek 'Skippable' to true and then back to false.

Hi Jozef, these two files look OK to me also. Note that I have changed the initialization of these User Task variables:

Task Name = "Task Name"
Priority = 1
Skippable = "true" (the default value assumed by the engine if no assignment expression is present in the DataInputAssociation!)
Locale = "en-UK"

Let me know if you think any of these should have different values.
I'm going to assume this BZ is now resolved, and ready for QA, unless you tell me otherwise ;)

Fixed with Luna build 1.1.1.201501262023

Looks ok!

Verified on BPMN2 Modeler 1.1.1.201501282123

BPMN2 Modeler 1.1.1.201501282123 NOT included in jbds-8.0.2.GA_jbdsis-8.0.0.CR2

Verified on jbds-8.1.0.CR1_jbdsis-8.0.1.CR1 - BPMN2 Modeler 1.1.2.Final

Fixed and included in the latest release.