The table below provides a summary of the field types and values you can select when mapping Internal Fields and External Fields to fulfil the requirements for a particular type of integration.
When you select , various options are presented to allow you to configure the mapping between the external and internal field.
The fields that can be mapped include standard, custom, and extension fields.
Some integration field mappings allow you to set the condition for updating the field, by selecting a value in the Update column.
Field Type
Examples
Field selector available value types
String, text, float, decimal, integer, date-time, and Boolean number
Acquisition Price
(Value) allows you to specify a particular value for the field. For a Boolean field the options are True and False. The way the selected value appears in the field indicates the area in which you are working, for example, {Event: Is Problem} if mapping an event field, or {Resource: Office} if mapping a Federated CMDB resource.
(Transform) allows you to define a property transform.
The multi-tier list of fields allows you to select any data field on the source using the multi-tier list of fields.
Profile
Manufacturer, Model Type
(Value) allows you to select a pre-defined profile value for the field. T
(Profile Map) allows you to map a value in a profile field to the value in a list-based field on the source.
Entity Reference
User
(Value) allows you to select an existing ASM Core entity.
(Search) allows you to search for an existing ASM Core entity.
(Resolution Rule) allows you to set up a resolution rule for importing or updating additional information about the entity.
(External Resource) allows you to select a field defined for the external resource. The internal field will be set to the value of the external field. This option is only available when configuring a resource mapping to integrate with the Federated CMDB.
Condition
Description
Always
populates the field automatically whenever this field mapping is picked up during a scheduled scan. This option is useful if the external source is the definitive place where this information resides.
On Initial Population Only
populates the field only when a new record is created. This option is useful if this item may be updated from integrations with various external sources.
Only When Blank
populates the field only when it is blank. This is useful if the field on the external source is not the definitive place where this information resides, and should not have the ability to overwrite the field value.
Create Discrepancy Report
does not populate the field automatically when the field mapping is picked up during a scheduled scan. Rather, an entry is added to the Discrepancy Report view in the Federated CMDB Administration window, allowing you to decide whether the field may be updated or not. This is useful to detect unauthorized changes on the source.
