CI Assignment Attribute Dynamic Field Map

Table of Contents

This feature makes it possible to link configuration items (CIs) from the OTRS CMDB with services and SLAs, thereby both providing service agents with a better overview and making it possible to offer purely configuration item oriented services. This is especially helpful for companies that provide services for a wide range of different devices or products and that must conform to strict SLAs.

In addition, the feature also makes it possible to map and link configuration item attributes to previously created dynamic fields. If the fields are merely text fields, it is possible to carry out simple mapping in the system configuration. If the configuration item has multiple values that must be displayed in a drop-down dynamic field in the ticket, an extended mapping must be configured.

Assign Service and SLA

It is possible to add definition of two configurable fields in configuration items which contain service and SLA information.

Whenever a configuration item is linked to a ticket or unlinked from a ticket, these fields are used to update or remove service and SLA of the linked ticket.

To add the fields for configuration items:

Go to the Configuration Items screen.
Select a configuration item class and click on the Change class definition button.

Add the new fields to the class definition.

- Key: TicketServiceName
  Name: Service
  Searchable: 1
  Input:
    Type: Text
    Size: 50
    MaxLength: 50

- Key: TicketSLAName
  Name: SLA
  Searchable: 1
  Input:
    Type: Text
    Size: 50
    MaxLength: 50

Note

The Key values must be the same as set in ITSMConfigItem::ServiceField and ITSMConfigItem::SLAField settings.

After this is configured correctly, just create a configuration item with both fields filled out. If you are going to link this newly created configuration item to a ticket, service and SLA from configuration item attributes are taken into the linked ticket.

Requirements and limitations for service and SLA linking:

Service functionality must be enabled.
Configuration item fields for service and SLA must be configured.
Linked configuration item must contain valid service and SLA names.
Service and SLA names of configuration item must be allowed for the linked tickets (e.g. not restricted via ACL).
Linking a configuration item when another configuration item is already linked will update service and SLA again.

Requirements and limitations for service and SLA unlinking:

Service functionality must be enabled.
Configuration item fields for service and SLA must be configured.
Service and SLA of ticket and configuration item must match.
After unlinking, service and SLA of ticket will be removed, not changed to values before linking.

Assign Dynamic Field Values

It is possible to add definition of a configuration item attribute to dynamic field mapping.

Whenever a configuration item is linked to a ticket, it is checked if the configuration item has attributes defined in this mapping and if so, assigns these values to the dynamic fields of the corresponding ticket. Whenever a configuration item is unlinked from a ticket, the dynamic field value remains unchanged.

To configure the mapping:

Go to the System Configuration screen.
Search for the setting ITSMConfigItem::TicketDynamicFieldMapping and set the mapping between configuration item attributes and ticket dynamic fields.

For example:
```
NIC::IPAddress         → IPAddress
NIC::IPoverDHCP        → IPoverDHCP
SerialNumber           → SerialNumber
WarrantyExpirationDate → WarrantyExpirationDate
```
Note

If you want to use configuration item attributes nested into a deeper structure, add the chain of attribute keys separated by ::.
Search for the setting ITSMConfigItem::TicketDynamicFieldValueMapping and set the mapping between configuration item attributes and the values of ticket dynamic fields. We have to specify mappings for this to solve a mismatch between possible values of configuration item attributes and possible values of ticket dynamic fields.

For example:
```
NIC::IPoverDHCP → No  → 2
                  Yes → 1
```
The numbers define the order in which the values are shown in the drop-down dynamic field. If you would store the values Yes and No into a dynamic field with the configuration shown above, the system would try to store the value Yes or No whereas the dynamic field would expect key 1 for Yes or key 2 for No.

Note

This mapping can also be used for other fields, if the configuration item attribute value does not match a dynamic field key. In this case write the configuration item attribute value into the key part of the hash and the dynamic field key inside the item tag.

After this is configured correctly, just create a configuration item with the mapped fields filled out. If you are going to link this newly created configuration item to a ticket, the ticket dynamic fields are populated with configuration item attributes. The configuration item attributes can be shown in the Properties widget of the ticket detail view. The dynamic fields will be automatically updated when the CMDB is modified.

Limitations of the dynamic field assignment functionality:

Dynamic fields are just filled if they do not have content yet.
If a configuration item is unlinked from a ticket, the dynamic field values do not get deleted.
If a configuration item attribute contains a list of values (for example multiple IP addresses of a computer configuration item) only the first value of this list is assigned to a dynamic field.

Facebook X LinkedIn