This documentation supports the 19.02 version of Remedy with Smart IT.

To view the latest version, select the version from the Product version menu.

Creating a change request


You create change requests by selecting Create New > Change Request. Your administrator might also have configured the system so that you can generate certain kinds of change requests through the Smart Recorder by submitting a service request. You can use a change template that the administrator provides, or you can create a new change request. In both cases, a wizard in Smart IT helps you enter the necessary information, as described in the example below in this topic.

While searching for a template, the template appears if you type the exact name (including symbol) of the template as it was given in the ITSM while creating the template. For example, if you have given the template name in the ITSM as "Template<", you should search the template with the exact text as "Template<".

You cannot enter the Target Date while creating change requests for Emergency and Latent classes.


To create a change request by copying information from an existing ticket

The following steps describe how to create a change request by copying information from an existing ticket:

  1. Open an existing change request ticket.
  2. From the menu, click in the Universal Client or Copy Change option in the iOS and Android applications to copy information.

    Universal client

    iOS

    Android

  3. The Copy Change Request screen displays the field information that you can copy. Based on your selection, the information is copied and populated in a new change request in draft mode.Create a new ticket based on the copied information.
  4. Provide the remaining information to create a change request. A work note is added for this activity in the Activity tab.

    In the Universal Client (UC), the Risk Level and Risk Questions and Answers are not copied in the draft screen of the newly created change request. In the Smart IT applications of Android and iOS, the Risk Level is copied from the source change management ticket.

    If you copy a change request that has the Service Impact Assessment document added to it, it will not be copied even if you select the Document and attachment checkbox in the Copy Change screen.



Supported fields

Currently, you can copy the following field information: Request for customer, Impacted area, CI, Documents/Attachments, Related change, Tasks, Title, Impact/Urgency/Priority, Change class, Affected service, Change reason, Operational Category, Product Category, Description, and Location.

Limitation

You cannot copy the following information: Date, Risk Level, Assignment, Location, and Work Notes.

Example of creating a change request by using Smart IT

Allen Allbrook is a specialist in the network infrastructure group. His manager, Mary Mann, asks him to reconfigure the routing table of some networking equipment. Because this activity might affect technical or business services in the company environment, Allen must submit a change request according to his company's policy. The change must be properly documented, assessed for risk, and approved.

Allen determines that this reconfiguration will be a normal change that affects the Network business service. Because no change template is available for this type of change, Allen must create the change from scratch:

  1. Allen opens Smart IT from his desktop browser and selects Create New > Change Request.
  2. He chooses the option to create a change request from scratch, and selects Normal from the available change classes.
    The wizard opens with some information pre-populated and required fields clearly marked.

    To use the change template option, Allen would need to search for a template by entering keywords that are part of the template name. For example, searching for network routing returns a list of change templates with names containing the words "network routing."

  3. In the Basics section of the wizard, Allen provides a short summary of the change needed, and he records the impacted site. Type-ahead functionality allows him to correctly populate the Requested For and Affected Service fields. Allen chooses to let the system select the best match for the change assignment.

    If Allen has the functional role of Change Coordinator, by default he is assigned as the change coordinator for change requests that he creates. If he were using a template, the change coordinator specified in the template (if any) would take precedence.

  4. In the CI section, Allen performs a few concurrent searches to locate the affected network device and then relates the CI to the change request.
  5. Allen decides to enter additional information that is not required to create the initial change request:

    1. In the Dates section, Allen specifies a range of dates approximately 3 weeks from today.

      Allen notices that there are several detected collisions, but he knows he will have the opportunity to run an impact analysis when he saves the change request. He will run the impact analysis first, relate any additional impacted CIs, and then manage collisions. Calculations are displayed in-sync with the creation of the change request.

    2. In the Risks section, Allen answers a few questions that the system uses to calculate risk.
    3. In the Documents section, Allen selects the Requirements and Backout Plan documentation types and records some initial notes for each. Your organization might require specific types of documents depending on the class of change (such as Normal or Standard). For each type of documentation, you can record simple notes or upload files.

  6. Allen saves the change request.
    The change request is created in Draft mode. A dialog is displayed that gives Allen the option of running an impact analysis now, or returning to the change request later to run the analysis manually.
  7. Allen clicks Submit and Prepare Impact Analysis.

While the impact analysis is running, Allen launches a new Smart IT window to continue working. He will receive a notification when the impact analysis is ready.

Allen is notified about future updates to this change request in his Updates feed. When adding notes to the change request, he can reference additional team members with "@" mentions so that they receive notifications in their Updates feeds.

When you create a change request, the calendar does not show any other existing changes for the same period. In Smart IT only individual change request, and in case of collision, the corresponding change requests that have collision are displayed. When you create multiple change requests and add the same CI to the change requests, it pushes the calendar to show the collisions. In Mid tier, change calendar shows changes happening regardless of collision.


To search for CIs that are in Delete status

When you run a global search for CIs or when you relate CIs to an incident or a problem investigation ticket, by default the system does not display CIs in Delete status. However, you can search for CIs that are in Delete status from change requests and assets. On the Asset Console, to filter CIs in Delete status, you must select the Delete check box from the Status list.

To restore a CI that is in Delete status, when you create or edit change requests, on the CI tab, perform the advanced search and select the Delete check box to search for CIs in delete status. From the search result, relate the change request with multiple CIs that are in Delete status to track configuration changes made to the CIs.

Similarly, you can search for CIs in Delete status from assets. To do so, on the the Assets tab of the asset profile, click the Relate Existing Asset link. On the Relate Assets pane, perform the advanced search to search for CIs that are in Delete status. From the search result, relate the asset with multiple CIs that are in delete status.

If you do not want the system to search for CIs in delete status, you must select the check boxes for the statuses that you want to search, and clear the Delete check box.

By default, in the search result the system displays CIs in all statuses including the delete status.

To specify the change location

When creating change requests from scratch without using a change request template, in the Change Location field, you must specify the location where the change needs to be implemented. The change location depends on the following factors:

  • The company specified in the Company list.
  • The company and location of the customer specified in the Requested For field.
  • The company and location of the service desk agent who is creating the change request.

These companies might not be same. The location in the Change Location field is driven by the company specified in the Company list. A company can have multiple locations.

Example

Consider three companies—Company A, Company B, and Company C. The location details of these companies are as follows:

  • Company A—Texas and New York
  • Company B—Toronto and Vancouver
  • Company C—Shanghai

The following table indicates the basis on which the location is specified in the Change Location field on the change request profile.

Company and location of the service desk agentCompany specified in the Company listCompany and location of the person specified in the Requested For fieldLocation in the Change Location field
Company A (Texas)Company ACompany A (New York)Company A, New York. The location of the person specified in the Requested For field.
Company A (Texas)Company BCompany B (Toronto)Company B, Toronto. The location of the person specified in the Requested For field.
Company A (Texas)Company ACompany B (Vancouver)Company A, Texas. The location of the service desk agent.
Company A (Texas)Company BCompany A (New York)The Change Location field remains empty. To specify the location, in the Change Location field the system displays locations of the Company B.
Company A (Texas)Company BCompany C (Shanghai)The Change Location field remains empty. To specify the location, in the Change Location field the system displays locations of the Company B.

When creating change requests by using change request templates, if the company specified in the template and the company selected in the Company list are similar, the location specified in the template is populated in the Change Location field. If the companies differ, the company location is populated based on the details given in the table in the example. You cannot update the company name in the Change Location field for an existing change request.

Additional considerations about activity notes

In BMC Change Management, you can add work notes to change requests and select the type of work note from the Work Info Type list. By default, the following subtypes are displayed in the Work Info Type list:

Work Info type

 Work Info subtypes
Requirements

Business Justification, and Requirements

Analysis

Change Assessment, Potential Problems, Risk Assessment, and Service Impact Assessment

BuildBackout Plan, Business Design, Development, Install Plan, Technical Design, and Test Plan
ExecutionBackout Results - Details, Install Results - Details, and Test Results - Details
ClosureCancellation Information, and Post implementation Review
AuditConfiguration Audit, SLM Compliance Audit, and SLM Process Review
GeneralGeneral Information, Rejection Information, Email System, Paging System, and Chat

Work notes in BMC Change Management is named as notes in Smart IT and Work Info Type list is named as Type list.

The information in this section is also applicable to release tickets in Smart IT.

Similarly in Smart IT, on the Activity tab of change requests, you can add notes and select a subtype from the Type list. By default, the subtypes under Execution, Closure, Audit, and General are displayed under the Type list.

In Smart IT, the subtypes under Requirements, Analysis, and Build are available as document types in the Documents tab of change requests. Thus, on the Activity tab of change requests they are not listed under the Type list, and in the filters under the Show Note Types list.

You must consider the following points:

  • If you add a custom note type in BMC Remedy ITSM under the Requirements, Analysis, and Build types, the custom note type is displayed in the Type list in Smart IT.
  • If you add a work note to a change request in BMC Change Management, and specify a work note subtype under Requirements, Analysis, or Build, then in Smart IT, that work note is added to the corresponding document type on the Documents tab.
  • You cannot add custom document types on the Documents tab.

Difference in labels in Remedy IT Service Management and Remedy with Smart IT

The following table displays the labels that are different in Remedy with Smart IT in comparison with the Create Change screen of Remedy IT Service Management:

Remedy IT Service ManagementRemedy with Smart IT

Notes

Description
SummaryTitle
Manager GroupManager Support Group
ServiceAffected Service
ClassChange Class
Work InfoActivity
CategorizationCategory
Was this page helpful? Yes No Submitting... Thank you

Comments