GUI changes in 5.4?

[wolpert]

This is a minor question… but did the UserTask object change in the 5.4 release of designer? Specifically, an activiti diagram I had pre-5.4 has rectangle blue-shaded objects to represent user tasks. On that diagram which I opened with the 5.4 release of designer, when I add a new UserTask, its now shaded yellow and the rectangle has more rounded corners.  I'm only really asking because it looks different enough. If that's what it should look like, is there a way to get all the user tasks to look the same?

[trademak]

Hi,

Labels of connectors could be an issue yes. Could you provide a test diagram that I could use?
Emptying the activiti:formKey fields is really a bug, so that should be fixed, shouldn't be too difficult.

Best regards,

[wolpert]

I'll see if I can make one. I can't use our current process due to proprietary issues. I've updated them and new versions are working fine.

[wolpert]

Actually, its easy to reproduce. I just created a brand new diagram using the 5.4 version of designer, making sure the formKey was set. Quit the designer, and verified the key was in the xml file. Then remove the my_bpmn2_diagram.activiti file and restarted the 5.4 version of the designer. Sure enough, the formKey for the user task was empty…. saved the project and the xml file didn't have the formKey anymore.

[wolpert]

I found a new issue on when I delete the original activiti file, and have it regenerate from the xml one. I inserted a new user task after an existing one in long chain of tasks. I can validate the diagram and its fine. But the xml fails due to the ID of the new task (and flows) already exists. Specifically, it gave it the ID of 'usertask2' even though there are 5 usertasks already. (Coincidently, I did place the task after the first usertask.)

Let me know if you can reproduce it. If not, I'll come up with an example for it.

[trademak]

Hi,

I've committed a fix to the trunk a few minutes ago for the formKey attribute.
The generation of the IDs is also improved in the trunk so you shouldn't be running into these problems starting from version 5.5.

Best regards,

[wolpert]

Very nice, thank you!