Currently, a new revision is made whenever a user saves changes made to a diagram. Thus a diagram will have hundreds of revisions during its lifespan. The diagram comparison tool doesn't communicate which, if any, of these hundreds of revisions were published. This results in it being difficult to identify what the diagram looked like when it was published, and thus difficult to identify what has changed from a previously ...more »
If all tasks in a subprocess are of a certain task type (e. g. service task), it would simplify diagram reading to be able to mark the collapsed subprocess with the same task type.
When creating process maps, there is the "process link" as a connector for the individual process elements. This one can not be labeled at the moment. Similar to the sequence flow at BPMN, we would like to be able to label this connector as well.
In the process editor, the areas for displaying the modeling elements and the attributes of the selected element can be opened and closed by clicking on the respective double arrow. This is very useful, but can currently only be done via mouse interaction. Here, similarly to the unfolding of the history in the Explorer with space bar, also defined shortcuts would be very desirable and helpful, by which the visibility ...more »
In our system, editors and hub users diligently capture comments on processes and process elements that are there to work through and discuss. The system supports the recording of comments well, if I want to talk through as editor or process owner with a commentary all comments submitted, the system offers me no way. In the process editor, the Advanced Search could be extended so that the user could be used as a criterion ...more »
Now, when a default visualization attribute has changed (e.g. line or fill color), this default is not applied automatically to all diagrams that use the default. Instead, each diagram has to be opened individually, saved and published as a new revision. Changes in default visualization attributes should not need to trigger a new revision (and especially not require each diagram to be manually touched), as this is counter-intuitive ...more »
Currently it is possible to show which users are invited to provide feedback per process. On the other hand it is not possible to get an overview, to which processes the user is invited to comment on. This would be a great solution due to a huge amount of people beeing involved into several process enhancements per comment function invitation. It would be easier to manage or get an better overview to which processes the ...more »
When saving charts, maps, etc., it would be very convenient if they were published in parallel and automatically in the Collaboration Hub by setting a checkmark (or similar). In addition, the admin in the user management should be able to enable this option only for certain users. Especially if diagrams are changed or corrected, they have to be released again and it would be very practical if the publication would happen ...more »
In complicated environments there is a need to have a "sub administrator" capability. Where you have a complicated organisation, there may be process architecture administrators required to move users to different groups or create groups for security rights to folders within a parent folder. At present if someone is given Admin rights they will have those rights across the whole of the workspace. This means they ...more »
We have defined attributes held at the process map level to hold design decisions applicable to the whole process. The attributes are in the form of a table and due to the type of information held, it makes no sense to hold these as dictionary entries. We want to include this information in the Process Documentation and as such it would help if we could format the text in the attributes. However, the text entry dialog ...more »
Currently, it is possible to show per process which users are invited and can provide feedback. The user is required to get an overview of which processes he is invited to provide feedback as he is involved in multiple processes.
If other applicable documents could also be linked to glossary entries, you would have a global administration and would not have to create a single document (which is used more frequently) individually (upload or link to a server, etc.). A glossary entry "document" can be linked as usual with a server and the document management is more or less advanced, efficient and simple. Of course I can upload a document in Explorer ...more »