Field mappings


Refer to this topic for information about how data flows from BPPM to ITSM at the time of incident creation. The following tables summarize what information is mapped to each slot and field at each stage in the integration.The first table documents the fields that are used for ALL incident create operations. The mappings defined in the subsequent tables are additive to the first table. From these tables, you can trace the flow of information from an event all the way through to the fields they get mapped to on the resulting Incident.

For example, when an impact-based policy is used for an event that results in creation of an Impact Incident, the component_ID from BPPM is mapped to the component_ID field on the INT:Staging form, which is mapped to the HPD_CI_ReconID and Service_CI_RecodID on the HPD:IncidentInterface_Create form. These fields are finally mapped to the HPD_CI_ReconID and Service_CI_RecodID fields respectively on the HPD:Help Desk form.

Success

Tip

Press F to view the table in full screen. Press Esc to cancel.

Base field mappings for incidents created through iBRSD

Refer to the following table to understand base field mappings when incidents are created through iBRSD.

Additional field mappings for Causal and Impact incidents

Refer to the following table to understand additional field mappings for Causal and Impact incidents.

Additional field mappings for Event incident

Refer to the following table for additional field mappings for event incidents.

Field mappings for incident to create Work Info record

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Intelligent Ticketing 2.0.00