Using this function, you can create categorization schemas with related categories, and assign the schemas to applications such as service orders, service tickets, and complaints.
In addition, you can use a categorization schema to make additional functions and information available in your applications. For example, you can assign knowledge articles to categories. When you select a corresponding category in a service order, you can choose to add the knowledge articles that are linked with the category, to the service order.
Page Area | Function | Description |
---|---|---|
Search result list and |
| You can create categorization schemas. In some cases, you may not be able to change a schema because you do not have the necessary authorization. |
| When you create a new version of an existing schema, the original version of the copied schema remains but it is no longer changeable, and also cannot be used in future. Historical documents, such as service orders that refer to the original version of the schema, remain consistent. | |
| You can copy an existing schema, and make changes to the copy. When you copy a schema, you create a new schema with a new ID. The original schema remains unchanged. | |
Search result list |
| You can merge categorization schemas. |
| You can import categorization schemas. | |
|
| You can use this feature to translate categorization schemas in the WebClient UI. The translation function includes the following features:
|
|
| You can use either hierarchical categorization without multiple usage of identical categories within a schema, or attributive categorization with multiple usage of identical categories within a schema. |
| If you assign a schema to more than one application ID, you can use the authorization mode to control to which degree the authorizations that were predefined for each application ID, such as change authorization, are valid for this schema. | |
| If you assign a schema to more than one application ID, authorizations such as change authorization must be predefined for all application IDs for them to be valid for this schema. | |
| If you assign a schema to more than one application ID, all authorizations that are predefined for one application ID are transferred to the other application IDs, and are therefore valid without exception for this schema. | |
| Newly created schemas, or schemas in editing mode, have | |
| When you have finished editing a schema, set the status to | |
| The | |
| The The schema continues to exist so that completed processes that refer to this schema remain consistent. | |
|
| Using the fields |
| For service processes and for the interaction record, choose the subject profile that should be valid for this schema. You can then assign the individual subject codes for the profile in the schema, at category level. | |
|
| Enter the category name that you want to be displayed in the category selection fields in sections of the application, such as in the service process. |
| You can use this field to enter notes. For example, you could use it to differentiate between two categories with similar names. The description is displayed only in the category modeler. | |
| If you have assigned a schema in the page area | |
|
| You can assign extended attributes, to integrate time-based versioning at category level. |
| Category values can be defined locally, that is, at the level of the relevant category. | |
| The validity period of a category is passed down to its lower-level categories. | |
| The effective validity period of an individual category is always a combination of the inherited values and the locally defined values. If there is a conflict between two values, the more restrictive value is used. | |
| Various functions, such as | The assignment of objects to categories in the category modeler enables automatic suggestion of objects. In a service order for example, if you select a category to which a service order template is assigned, you can choose to automatically complete the service order, using this template. |