Use > Widgets > Learn about Widgets > Change Request Widget

Change Requests Widget

The Change Requests widget presents the Change Requests related to the selected CI. CI Overview mode displays the total number of Change Requests for each Change Request state. Widget Details mode displays a list of all the Change Requests related to the CI and all their details. The Change Request widget is presented only when Micro Focus Service Manager (SM) configuration element is enabled and configured in the Infrastructure Settings in UCMDB. All data presented is taken from the UCMDB federated RequestForChange CI and its relationships.

Note The Create Time for federated CIs will show the Open Time of the Change Request in SM. Using non federated RequestforChange CIs (populated with other integrations) will cause the Create Time to be the time when the Change Request was created in UCMDB and not the time when the Change Request was opened in the external data source.

A Change Request is considered related to a CI if it meets one of the following criteria:

  • All Change Requests linked directly to the CI.
  • If the selected CI is a Model: All Change Requests linked to all the CIs contained in that model (meaning, any other contained model or CI).

  • If the selected CI is a Person: All Change Requests that are connected to all the CIs owned by that person.

  • In all other cases: All Change Requests that are linked with a composition link to the selected CI (for example: Running Software to Windows Server).
ClosedCI Overview Mode

In this mode, change requests related to the selected CI that have one of the following statuses are presented:

  • Recent. All Change Requests that terminated in the recent time frame (default – 3 days, is refreshed if the selected time frame is changed in the widget details).
  • In Progress. All Change Requests that are currently in-progress. A Change Request is considered In Progress if it is open, meaning that its planned start date has passed and its planned end date has not yet passed. Also, its phase must qualify as In Progress, meaning that it is defined in the In Progress list in the XML configuration file.
  • Overdue. An overdue Change Request is a Change Request that was In Progress but whose planned end-date has passed.
  • Planned. All Change Requests that are planned to start in the recent time frame (default – 3 days, is refreshed if the selected time frame is changed in the widget details.
  • Delayed. A Change Request is Delayed if it was a Planned Change Request but its planned start-date has passed.

The UCMDB administrator can define which IT SM RFC Phase is mapped to each one of the Change Request statuses Recent, In Progress, and Planned (the Overdue and Delayed statuses are automatically calculated by the UCMDB Browser). The UCMDB Browser is configured by default in the following manner:

UCMDB Status IT SM RFC Phase
Recent Evaluation, Closure
In Progress Implementation
Planned Approval

If a Change Request’s phase does not exist in the configuration list it is ignored, meaning that it is not included in the Change Request summary or detailed list.

If a Change Request’s planned start date or end date are not defined, the UCMDB Browser uses the current date for both planned start/end dates (in both the CI Overview and Widget Details modes).

ClosedWidget Details Mode

This mode adds the following to the summary displayed in the CI overview:

  • Timeline Span toggle: +/-3 days , +/-1 week, +/-1 month. Selecting a timeline span details all Change Requests related to the selected CI that are contained within the selected timeline (that is, either their start date or due date are within that timeline). Note that changing the timeline should change the summary displayed in the CI overview.
  • Show toggle: All/Late. Selecting All details all Change Requests related to the CI in the selected timeline, selecting Late presents only those Change Requests that are either overdue or delayed (as explained above).
  • All relevant Change Requests, sorted by their status (Recent, In Progress, Overdue, Planned, and Delayed). The internal sort within each status group is according to Change Request phase and then planned start date.

The following information is provided per each Change Request:

  • ID. This is a clickable field that refocuses on the RequestForChange CI when selected
  • Phase
  • Planned Start Date. Is emphasized if the Change Request is Delayed.
  • Planned End Date. Is emphasized if the Change Request is Overdue.
  • Affected CIs. Up to 10 CIs within the context of the selected CI are presented, with a link to show all results in the event that there are more than 10 affected CIs within the context of the selected CI linked to the Change Request. Affected CIs can be refocused.
  • Affected Service. The first BusinessService CI, within the context of the selected CI, connected to the Change Request CI through a membership link. If no such CI exists, the Affected Service header is not displayed. The Affected Service can be refocused.
  • Severity

  • A direct link to the Service Manager system with the context of the selected change request is presented per each change request, if this link is configured by the system administrator. For instructions on how to configure this direct link to Service Manager, see Configure a Direct Link to Service Manager for a Selected Problem, Incident, or Change Request.