Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Assets Data Manager for Jira Service Management Cloud is currently rolling out in Open Beta and will be available to all Premium + Enterprise sites by end of October 2024.
The Computed Dictionary is a feature that allows users to standardize the terminology from multiple data sources by comparing it against a list of normalized values when an Import is run.
Computed Dictionaries use a specific type of Attribute called a Computed Attribute. These attributes get data from a data source and compare it with a list of possible Dictionary Values. If a Dictionary Value is found that matches the source data, it will populate itself with the normalized value, which is the name of the Dictionary Group. If a new or unexpected value is found the data will not be changed, but this information will be sent to Compute Issues to be reviewed.
In Assets Data Manager, there are Default Computed Dictionaries and Custom Computed Dictionaries.
Default Computed Dictionaries include values for each Default Attribute in each Default Object Class. These can be automatically synchronized to keep them up-to-date. The Computed Dictionaries for each Default Object Class are listed in the topics for each Default Object Class. Learn how to configure Default Computed Dictionaries.
Custom Computed Dictionaries are created manually and stored locally. They hold extra information that you want to normalize in your system. Learn how to configure Custom Computed Dictionaries.
Computed Dictionaries can be modified in three ways:
Default Computed Dictionaries can get data from Syncing. Syncing is when the Computed Dictionary receives updated data from a server. Only the Default Computed Dictionaries for each Object Class can be Synced.
Both Default Computed Dictionaries and Custom Computed Dictionaries can get data by being manually updated. Users with the appropriate permissions can use Data Manager to modify the Computed Dictionaries, Computed Dictionary Groups, and Computed Dictionary Values, to manually to add new values, or edit or delete existing ones.
Both Default Computed Dictionaries and Custom Computed Dictionaries can get data through Computed Issues. When Computed Dictionaries are used to normalise data during the Import operation, any discrepancies found between the dictionary and your data will appear in Computed Dictionaries. For each issue, you can choose to ignore the new value or update an existing dictionary.
Computed Dictionary | Usage | Source Attribute/s | Destination Attribute |
---|---|---|---|
Compute Object Class | |||
OSVersion | Used to normalize the various operating systems into one clean label. For example, our data source might contain values like WinXP, OS_WinXP, and Windows XP Professional x64, three separate values that actually refer to the same thing: Windows XP. | OperatingSystem | OSVersion |
Platform | Used to group the OSVersions into platforms like: Windows, Linux etc | OSVersion (Computed) | Platform |
InfrastructureType* | To enable grouping of end points into a type like: Physical , Virtual or Cloud Servers, Containers, Laptops or Desktops, etc | Manufacturer, ModelName | InfrastructureType |
Network Object Class | |||
IsVirtual* | Identifying if a network device is virtual or physical | Manufacturer, ModelName | IsVirtual |
InfrastructureType* | To enable grouping of end points into a type like: Physical, Virtual or Cloud Servers, Containers, Laptops or Desktops, etc | Manufacturer, ModelName | InfrastructureType |
Peripheral Object Class | |||
InfrastructureType* | This allows you to group your peripherals into major categories of Print / Scan, Audio Visual, Consumables and Other. | DeviceType (Computed) | InfrastructureType |
DeviceType* | To enable grouping your peripherals into more granular groups that sit below the InfrastructureType. | Manufacturer, ModelName |
|
* Raw data for these Computed Dictionaries are not provided, but the Computed Dictionary fields are set up. Upon your first Import, the system will generate the Computed Issues, which will then require mapping.
Was this helpful?