The feature for generating labels on message flows (from send/receive tasks and message catch/throw events) should apply only to message flow and not sequence flows. This patch fixes the bug that added labels to sequence flow.
When process models get overly complicated, grouping tasks into subprocesses makes the model clearer and easier to understand. Process modellers can now use the 'Convert to subprocess' feature to do just that. How it works: Option 1: Hold down CTRL key on PC (or CMD on Mac) Click
Message flows are now automatically generated based on the object sent or received between the external participants and connected events and tasks in the process.
Previously, start event labels would change when the marker changed (e.g. from Message Event to Conditional Event). We now leave the label intact when you change the marker on the start event.
Fixed an issue that prevented users from opening Task Instruction snapshots in the version history when the task instructions were opened from a calling process model.
All process models and task instructions require an owner to be assigned before the first version can be published. We've made this required field more obvious by showing you an error when you try to publish. Previously the Publish button was disabled and it was hard to know why
Real estate is precious no matter where it is! That includes process models. So, we've reduced the size of the navigator so that it doesn't occupy as much screen real estate. PRO TIP: Did you know that you can collapse the navigator? Just click on the navigator icon in the diagra
Tasks often have multiple task performer candidates. Additionally, the same performers are usually needed for tasks in the same lane. We've made it easier to select multiple performers by using a different multiselect modal. This modal remains open until you click out of it, maki