When the "Collaboration Hub Homepage" is activated, two new icons or menu entries are displayed in the navigation tree: Home and Search. In addition, in the main window, a preview of the entry-level diagram is displayed, the last changes are displayed, etc. We cannot use the new homepage in the current version without further configuration options, so we wish the following optimization: Idea 1: The icons / entries ...more »
The display of the attribute fields "multi-line text" on diagram or element level always takes place in the "collapsed view". In many cases, however, it makes sense to display the attributes in the "expanded view", eg when images or graphics are included (see screenshots). Therefore, an additional configuration option would be desirable. For example, in the standard system, a checkbox "collapsed" is activated for each ...more »
The detailed display of an activity is extremely confusing for the hub user as soon as extensive information is stored in the documentation field. Proposal to display the field documentation in triple width, so over the entire width. Negative example see attached screenshot. (Vision: Ideally, there is a config tool that adjusts the field positioning itself.)
In collaboration hub, it should be possible to use alphabetical tabs to go directly to the list of items starting by a given letter: eg all roles starting by "I" instead of browsing pages from A to I.
This is feature is available in the Dictionary Editor and is very convenient.
In the diagram view is not clear whether a start or end event linked to another chart. This information is obtained in the portal only when one opens the corresponding pop-up (attribute predecessor / successor processes). In the expression of a diagram, this information is not available. Since this is an important piece of information, the name of the predecessor or successor processes should be automatically displayed ...more »
Identification of own role: A portal user wants his responsibilities can be viewed by clicking on the portal. Either in search of the role or the glossary entry for that role all linked charts are displayed. The reader (eg. Buyer) will at a glance see what processes he has the overall responsibility or holds only role of an informer.
I can in specific views reduce the details, when opening a chart the user sees but first everything, he can then switch to a reduced view. This form "kills" the user only with too many details, and only the "survivors" Users can see the compressed views. Proposal: The editor will determine which groups which view as "standard representation" looks and what other views are offered to the user group. So I can also control ...more »
Subprocesses can not be opened in the comment view via mouse click (even if they are specified in the invitation). The usual links in the process portal should also be applied here.
In the process overview in the portal sub-processes appear on the same level as the main processes, to which they belong. Subprocesses could be displayed indented a tree view of the main processes. Subprocesses could easily be made visible in the overview also with its own icon. Representation in the Explorer would also be helpful.
SOLL: One should Comments can reply directly and clearly with any evident reference to comment. By setting the flag colors should therefore be an e-mail sent to the commentator. It should be able to post a comment directly associated Feedback addition. eg reason why discarded. On these, the commentator should also be able to answer back, etc. In the end you have such a group of associated conversation on a specific process ...more »
If a process map extends over several levels, the navigation becomes increasingly more difficult. From a certain amount of sub-processes the navigation through the folder view on the left, or the famous "browser back button" becomes very unwieldy.
Would be desirable, therefore, "Back" - "Level higher" - or "Top Level" buttons, which facilitate the navigation.
It should be possible that everyone, who is invited to comment, can configure whether he generally wants to receive e-mail notifications, in case of changes (Comments vs. new version), how often (once / daily / weekly) and for which diagrams he has been invited to.