Loading...

XML

Word

Printable

Steps to Reproduce:

Hide

1) Create the package A
2) Create a new Process BPMN2.0 in the package A with the trivial WF Start -> User Task -> End
3) Set the TaskName to MyUserTask
4) Generate task form templates

5) Create the package B
6) Create a new Process BPMN2.0 in the package B with the trivial WF Start -> User Task -> End
7) Set the TaskName to MyUserTask
8) Generate task form templates (different from the previous)

Executing the processes from JBPM console we can se always the same user form template.

Show
1) Create the package A 2) Create a new Process BPMN2.0 in the package A with the trivial WF Start -> User Task -> End 3) Set the TaskName to MyUserTask 4) Generate task form templates 5) Create the package B 6) Create a new Process BPMN2.0 in the package B with the trivial WF Start -> User Task -> End 7) Set the TaskName to MyUserTask 8) Generate task form templates (different from the previous) Executing the processes from JBPM console we can se always the same user form template.

Deploying two different processes using a different package cause a problem when the two processes have a user task with the same template name.

During execution JBPM uses always the same task form template for both processes ignoring their real package.

Repro the bug is pretty easy.