At the moment it is only possible to add a line at the end of your Editor for Attributes property of the Complex Class. This is very un user friendly. So if you want a line in between two other lines. You have to redo everything.
Our process map is structured in such a way that individual processes (eg enter A07.01 order) occur several times in the individual end-to-end processes (eg process for standard products or project business). All attributes (such as the description) must now be maintained individually for each end-to-end process, which is very time-consuming and error-prone, especially for changes. It would be useful if, at the level ...more »
Current: Title field is searchable in dictionary.
Future: Make custom attributes (configured) searchable in dictionary as well.
Internal to my organization, the editors need to label their information with different numbers. Their numbers have specific meanings and may change over time. Instead of having the number included in the [Title] field, a custom attribute is introduced to hold this information.
In the editor window, the "Attributes" bar on the right is hidden by default. We would like you to open by default. The preferred state should be configurable.
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 »
Autocomplete glossary entries should work better. This applies both to "in-line glossary links" (book symbol eg to activity) and to attributes of the type "glossary reference". - the (similarity) search does not work reliably: blanks, umlauts etc. distort the search results. - Even if multiple search results are found, "Create new entry" should be proposed.
It is very expensive to assign attributes of the type "Glossary entry (list)": each glossary entry must be searched, selected and added individually. Then the same game for the next, etc. For longer lists, this procedure is infinitely tedious. We therefore need a solution to how a list can be compiled efficiently. Ideas: - Quickly searchable list of all glossary entries of the allowed glossary categories so that an item ...more »
During the convention check of the process diagram, the list of notes, warnings and errors is displayed in the lower area as the result. After every change in the diagram resulting from the execution of the list from the convention check, the user is asked to update the list of notes, warnings and errors. As long as the list is not updated, no further entries can be clicked on and the errors are no longer displayed in ...more »
After a custom modeling convention is created, it can not be renamed anymore.
Switch a user from "Collaboration Hub" rights to "Enterprise Edition" directly within the setup menu.
Right now it is necessary to delete this user and to add it as new user afterwards.
For each dictionary category, custom attributes can be defined and displayed in Collaboration Hub. Existing capability is to display all custom attributes. Refer to existing capability of "Edit Collaboration Hub configuration", where visibility of custom attributes can be defined. Require a similar capability of Edit Dictionary Attributes Configuration, where visibility of some custom attributes can be defined for Collaboration ...more »