This feature is only available for customers with an Enterprise license.
You can define attributes for dictionary entries, like you can define them for diagrams. You can also define custom dictionary categories and subcategories.
Category types have two purposes:
- They are used by the system when creating reports (for example, RACI, document use, or process documentation reports) to identify objects of a certain category.
- They act as filters when dictionary references are suggested while modeling. For example, dictionary entries of the type IT System are only suggested when the user attempts to label an IT System element. Entries for which no type is set are suggested for any element.
Category types can be defined for both root level categories and child categories. The following category types are available:
|Organization||Organizational entities, that can be used to assign responsibilities for actions. Examples would be whole organizations (for example 'ACME Inc.'), organizational units or departments (for example 'Finance'), roles (for example 'Chief Financial Officer'), or even external process participants like partners, suppliers, government institutions or customers.|
|Document||Anything that can hold information and that is used or created during processes. This can be physical documents (for example printed applications), digital files (for example PDF forms), entries in databases, or variables in a computer program.|
|IT-System||Anything that can process documents or data, from standard software, individualized applications, and custom scripts, to hardware systems, like individual server instances, data centers, and hand-held devices, to integrated systems, like application servers, scanners, printers, or personal computers.|
|Event||Anything that can trigger a process, either during the execution or as the result of a process. Events are usually described by defining the situation or state reached once the event has occurred, for example "Customer order received" or "Goods sent".|
|Activity||Actions that are performed within processes. Actions usually connect all other types of objects. They are performed by organizational units or roles, can read and create documents or data, can use IT-systems, can cause events, and usually achieve certain goals.|
|Goal||The reasons behind why processes are executed at all and why they are designed the way they are: business goals to be achieved, key performance indicators to be met, or stakeholders to be satisfied.|
|Requirement||Typically descriptions of the differences between as-is and to-be processes or IT-systems, for example change requests, functional or non-functional specifications, or tickets in a requirements management system.|
|Others||Categories with this type have no defined meaning attached to them and are recommended to users for diagram elements that don't match more specific types. One example is the BPMN group element.|
Create a new category
To create dictionary categories, follow these steps:
- In the explorer, go to Setup> Define notations/attributes.
- Open the Dictionary tab. The dialog to configure dictionary attributes opens. All categories are listed.
- To create a sub-category, first select the parent category.
Sub-categories can't be parent category of other categories, a category path is either one or two levels deep.
- Click Add. In the dialog, set the following:
|Name||Specify a name for the category (mandatory)|
Select the parent category.
|Use for data modelling||Activate if you want to use the category for DMN input data (see Set up a dictionary category for DMN modeling ).|
Determines whether dictionary entries should be published in SAP Signavio Process Collaboration Hub manually or automatically.
After enabling manually, you need to explicitly grant users the right to publish dictionary entries, as described at Manage access rights.
|On change, linking diagrams are||
|Color||Select a color for the category.|
|Type of category||Select a category type.|
- Click Create. The new category is created.
- To edit, remove or rearrange categories, click the corresponding icon in the toolbar.
- To deactivate a custom category, disable the checkbox between the category's color and its name.
Dictionary categories for risks and controls
For risks and controls, it is not possible to use subcategories. If you need more than one category for risks and controls, we recommend using multiple risk attributes. This means you create one dictionary category for each type of risk, for example financial risks, legal risks, or health risks.
Manage custom attributes for dictionary entries
You can manage custom attributes of dictionary categories in the same way you manage custom attributes of elements. Read more in section Add and manage custom attributes.