Page History
| HTML |
|---|
<style>
.release-box {
height: 30px;
width: 100px;
padding-top: 8px;
text-align: center;
border-radius: 5px;
font-weight: bold;
background-color: #0ACA8B;
border-color: #FCE28A;
}
.release-box:hover {
cursor: hand;
cursor: pointer;
opacity: .9;
}
</style>
<meta name="robots" content="noindex">
<div class="release-box">
<a href="https://docs.perspectium.com/display/fluorineplus" style="text-decoration: none; color: #FFFFFF; display: block;">
Fluorine+
</a>
</div> |
The Common Change document is an XML schema that contains default fields for mapping change request form values from one system to another. In a nutshell, the The common change format mirrors what one would see in an ITIL view of the Change Request form with related lists expressed in embedded XML form.
A sample Common Change looks like this:
| Code Block | ||
|---|---|---|
| ||
<common_change>
<affected_cis>
<affected_ci>
<ci_class />
<ci_name />
<ci_id />
</affected_ci>
</affected_cis>
<approval />
<approvers>
<approver>
<created />
<approver_name />
<assignment_group_name/>
<approver />
<state />
<comments/>
<approver_email />
<assignment_group/>
</approver>
</approvers>
<assigned_to />
<assignment_group />
<attachments>
<attachment>
<data />
<size_bytes />
<file_name />
<sys_id />
<content_type />
</attachment>
</attachments>
<backout_plan />
<category />
<change_tasks>
<change_task>
<assignment_group />
<short_description />
<correlation_id />
<number />
<work_notes />
<comments />
<correlation_display />
<change_task_type />
<assigned_to />
<state />
<description />
<cmdb_ci />
</change_task>
</change_tasks>
<close_code />
<close_notes />
<cmdb_ci />
<comments />
<correlation_display />
<correlation_id />
<description />
<end_date />
<impact />
<impacted_services>
<impacted_service>
<operational_status />
<type />
<location_name />
<id />
<manually_added />
<name />
</impacted_service>
</impacted_services>
<implementation_plan />
<incidents_caused>
<incident>
<number />
<opened_at />
<category />
<caller_id_name />
<assigned_to_name />
<short_description />
<priority />
<id />
<state />
<assignment_group_name />
</incident>
</incidents_caused>
<incidents_fixed>
<incident>
<number />
<opened_at />
<category />
<caller_id_name />
<assigned_to_name />
<short_description />
<priority />
<id />
<state />
<assignment_group_name />
</incident>
</incidents_fixed>
<justification />
<number />
<priority />
<problems>
<problem>
<short_description />
<assignment_group_name />
<id />
<assigned_to_name />
<state />
<number />
</problem>
</problems>
<provider />
<psp_action />
<requested_by />
<requested_by_date />
<risk />
<short_description />
<start_date />
<state />
<test_plan />
<type />
<work_notes />
</common_change> |
Embedded records
Embedded records are fields in the Common Change document that cannot be mapped by singular values. Instead, they are entirely different records included inside the Common Change document to be created on the subscribing system. For example, the attachment field in the Common Change is an embedded record that, when populated, will create a new attachment on the system receiving the Common Change.
Similar topics
| Content by Label | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
