Dear Signavio Community,
Today I raise the idea of a merge function for tasks including attached attributes.
After our migration from ARIS many process diagrams contain duplicate tasks. We are now looking for a functionality, that merges selected tasks to one task (not subprocess) including all custom attributes.
This merging function should have similarities to the dictionary entry merge functionality,... more »
Move Description-Fields from task,gateway,flow,etc. with CTRL+ARROW pixel by pixel - similar to powerpoint-functionality as it already works on Tasks, Gateways, documents in editor.
It would be great to have an Icon for a Bot similar to the standard IT-system.
Es wäre klasse, wenn der Zoom out im Editor bis zur vollständigen Modellgröße (vgl. 'Zoom to fit the model size') ginge, damit schrittweise herausgezoomt werden kann.
Zusätzlich wäre es hilfreich, wenn nach Click auf 'Zoom to fit the model size' das Zoom in funktioniert, um wieder auf die Detailsicht zu wechseln.
It would be really useful to visualize that a explanation / description has been done for a task so that you can directly see which task are not complete yet. A small "i" for information in the upper right corner of a task would solve the problem.
Add another column in the Quick Modeller tool to allow more complex models to be created, include with this the option to name the outgoing sequence flows and select which activities to link them to.
Signavio should support standard XML export AND import of both DMN and CMMN, if the tool can be said to support the nomenclatures.
We need the ability to move into more robust architectural tools as we grow the practice and need capabilities not on Signavio's roadmap.
When moving sequence flows, the gateway labels are sometimes fouled by the new route of the flow. Suggestion from client is to automatically move the gateway label to a more suitable location.
See attachment. Automatic and/or configuration "jumps" on overlapping connectors (flows, arrows, lines, etc) would make diagrams much easier on the eyes - especially for folks newer to such visual modeling.
A "folder" above all the existing Dictionary Types (for instance to sort the entirety of a dictionary by Company/Team or to have some Enterprise-Level dictionary entries and other Org. Unit-specific entries. Those entries could then be governed/made viewable or editable only by particular subsets of users.
Dictionary Entries are not bi-directionally linked. I have to create custom attribute on both entries, and manually cross-link them.
Grant access to MODEL but not to alter the repository structure.. The ability to give access to create/edit models in Shared Document but NOT edit/create folders would be very helpful for repository maintenance.