Bug 800324
Summary: | User task: Task name is required by validation in Guvnor BPMN designer | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Radovan Synek <rsynek> | ||||
Component: | BRM (Guvnor) | Assignee: | manstis | ||||
Status: | VERIFIED --- | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | BRMS 5.3.0.GA | ||||||
Target Milestone: | --- | ||||||
Target Release: | BRMS 5.3.0.GA | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | Type: | --- | |||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Radovan Synek
2012-03-06 10:15:48 UTC
Created attachment 567900 [details]
process definition
Designer is not a modelling tool. It is an editing tool for creating executable BPMN2 process for the jBPM runtime. As such, for jBPM, an user task which does not have a TaskName associated with it is not executable. We need the TaskName attribute to associate the user task with it's task form, among other things. We should not remove this check. Hope this helps. Thanks. (In reply to comment #2) > Designer is not a modelling tool. It is an editing tool for creating executable > BPMN2 process for the jBPM runtime. As such, for jBPM, an user task which does > not have a TaskName associated with it is not executable. We need the TaskName > attribute to associate the user task with it's task form, among other things. This means we have our proprietary extensions of the BPMN2 standard. This bug must remain open either to be fixed, or to be properly documented. Yes, we do have a very small number of extension elements and attributes. The BPMN2 specification allows to be extended which is one of the best benefits of this standard. The implementations of the specifications (all of them) have some sort of extension elements/attributes which are needed to complement the standard (which btw. was not very thought out for actual implementations outside of just modelling). jBPM focuses on only adding extension attributes/elements when its completely necessary. TaskName (and packageName for example) are some of them. Very few, but needed. I don't see this changing any time soon. (In reply to comment #4) > Yes, we do have a very small number of extension elements and attributes. > I don't see this changing any time soon. Alright, I'm leaving this issue open so that these extensions can be properly documented. Is there a list of those by any chance? This is all in the docs: http://docs.jboss.org/jbpm/v5.2/userguide/ch06.html#d0e1995 Thanks. Hi Lukáš, the same table exists in the product docs: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_Business_Process_Management_Guide/chapter_BPMN2.html Thanks Lee Please verify this issue on ER5. Thanks! |