As a Signavio user, I would like to be able to print views of a BPM in order, for example, to print simplified processes or make them available as PDF.
We use different glossary categories to document different types of items. The hub does not show which example: Information objects (upper category in the glossary) are subdivided into documents and data records (subcategories). We use different glossary categories for this purpose. You can now assign documents as well as records to an activity. In the editor / glossary view, the color coding immediately shows which category ...more »
TranslationTranslated (Unverified) View Original
This summer we have migrated our business processes from QualiWare to Signavio. The feedback we have been getting from end users has been largely great. However, there is one feature most end users are missing: A Searchable table of a diagram's external documents and products (data objects) in Collaboration Hub. In both QualiWare and Signavio you can attach external documents, such as procedures, templates, check lists ...more »
Given Labels on connectors provide useful information, and sometimes the connector itself is wrong, I want to be able to make comments on connectors, not just nodes.
Breadcrumbs are an essential navigation tool. Currently, the breadcrumbs in Signavio show the shortest part to the top node. That's a good rule. However, we need more options. We suggest that "shortest part" is just one of several rules you can select when configuring Signavio. The other rules we need are: - Path-based breadcrumbs (the crumbs are the previous diagrams (nodes) you've visited in this session) - Defined ...more »
When a user clicks the 'Register' link on the login screen, he/she will be redirected to the general Signavio registration form. This prompts the registration for a 30-day trial version, leading to questions from the Sales team if these (future) users actually should belong to an existing workspace but are unaware of the process of being registered in their company workspace. I would like to: - have the link 'Register' ...more »
When navigating through the tabs "Overview", "Activities" and "Diagram" each click will be saved in the browser log. In other words, if you click through the tabs a few times and then wish to return to a previously opened diagram, you may have to click the back-button a few times. The breadcrumb path only gives you the quickest way to the top, but does not necessarily follow your navigation path. My idea is to refrain ...more »
Split input/output documents on activities/tasks into "Input documents" and "Output documents". The system, using the direction of the association, already knows, as shown by the document usage matrix, which are inputs and which are outputs to an activity/task.
In the diagram view in the Collaboration Hub, when a user clicks on an element (task, xor gate etc.), an information pop-up comes. For intermediate process links this is not the case - it goes directly to the other process. I'd like to have the option to have the a similar pop-up for the process which the link refers to (info from the Overview tab) for easy reference so you can quickly check out which process the link ...more »
The current list of activities (tasks) in the Activities tab appears out of order at times. It would be great to be able to set the order or have a well-defined default.
- In process order (preferred, requires a consistent way of following branches)
- Left-to-right and top-to-bottom regardless of the process flow
- Sorted alphabetically
- Sorted by role
Currently there are three ways the roles are represented in the model Acitivities tab:
- only one role involved: no selection
- few roles involved: clickable buttons
- many roles involved: pulldown menu showing RACI involvement
If find the last display (pulldown) the most helpful as it gives at a glance the aggregated involvement of each role in the process and is much easier to read than the second (buttons).
We would find it useful if there was also a possibility for the users in the hub to be able to start a kind of revision comparison. Probably you should limit it in the hub to the revisions published in the past. For interested users, it can be helpful and useful to be able to understand the changes in the process lifecycle and to understand what is different about the new version.