Applying the BMC Remedy IT Service Management post-DDM packages
When the source version of BMC Remedy IT Service Management is 8.0 (or earlier) and the target version is 8.1.00 (or later), fields in these ITSM forms are updated through workflow triggered by a staging form during the post-upgrade portion of the installer. To update the fields for the delta data, see To apply the BMC Remedy IT Service Management post-DDM packages.
The following data transformation changes are the results of updated functionality. These changes are already been done while upgrading BMC Remedy ITSM from version 8.0 (or earlier) to 8.1.00. To update the fields for the delta data, apply the package in your destination server.
Description of change
How to verify
Migrates all the data from the old Change Calendar forms to new Change Calendar forms. Because the schema structure is different from the old calendar to the new calendar, the user defaults of user were migrated to Filters and Preferences, and Saved Searches were migrated to new Saved Searches forms.
Check the user-specific data on the NGC:Filters, NGC Preferences and CHG:CHGNGC:SavedSearches% forms.
Removes the non-English data from the Derived Factors form for records where
Check the records in the Derived Factors form.
Corrects the customer data with respect to approval processes as Change Management deprecates the CI and IA of level processes and introduces a single CI-IA process. All records must be updated with the respective change.
Re-check your change requests for the CI or IA process. All of these approval processes will be replaced with the new CI-IA process. In the scenario where the record is in approval stage and using CI or IA process, you can see no changes have been done.
Corrects the APR:SYS-Approval Definition form data for release data where the "For Stage Number" & "For Status Reason Int" field is updated with corresponding enumid values. Because these changes were made in 8.0, the records before 8.0 must be updated accordingly.
Check the records on the APR: SYS-Approval Definition form.
Removed the records in the VIS:ProcessAcceleratorItem form, so that Approve and Reject options are not visible on Change or Release forms. Because Approving or Rejecting from the process flow bar causes some issues with re-loading the change, they were removed from the process flow bar. Hence this action is required.
Check the Change or Release form where it is in an Approval phase. No Approve or Reject buttons should be visible.
Corrects the value of Priority. Initially the value of
Check the priority of a new change request.
Corrects the records of the SYS:Notification Message form for Change Approval template where it updates the form with
Check the Approval-related notification template of the SYS:Notification Maessages form. For financials, check the Financial Association form for updates.
Corrects important Foundation form data. The People records are updated with AlternateID using LoginID. Also corrects the Approval Mapping for Individual based on the status of People records and for Group Mapping based on Group Status and Approval role. The Event name in the CFG:Assignment form changed from Assignee to Coordinator, so that Incident Manager becomes the Incident Coordinator, similar to Change Management and Problem Management. These changes were made because of issues observed in functions and processes of the consuming applications.
Check the People records, Approval mappings, and Assignments for corrected data.
Corrects the Predefined My Searches in the Asset Management console where it refers to the AST:Relation_BaseElement_Locale form for searches instead of AST:BaseElement. These changes were made to allow more locale specific searching capability.
Check the changes in the records of predefined searches.
MSM:MigrationTasks form runs the following tasks.
UPDATE_CHG_LEVEL_APR_PROCESSES_2_CIIA task that updates the following Change Level processes (which are being discontinued) to the corresponding Change Level CI-IA process:
In the APR:SYS Approval Definition (Approval Process Configuration) form, verify that the process name and sort order are changed for entries for the CHG:Infrastructure Change form.
If the Status is Proposed and the Sort Order field is empty, the procedure in "Updating fields in forms for delta data" does not update the Sort Order field.
UPDATE_FINAssociation_DATA_4_Classic_2_CHG task that changes the value in the Form Name 01 field from CHG:Infrastructure Change Classic to CHG:Infrastructure Change in the FIN:Association form.
If there was an entry in the FIN:Association form with CHG:Infrastructure Change Classic in the Form Name 01 field, verify that this value was changed to CHG:Infrastructure Change.
RMS_APR_POPULATE_STATUSREASONINTFIELDS task that updates the entries to populate the new status reason integer fields (FromStatusReasonInt and ToStatusReasonInt) with corresponding enumerated values for the status reason.
If an entry for the RMS:Release form exists in the Approval Process Configuration form for any phase that has a Status Reason for every status (Begin, Approved, Rejected, and No Approvers), export this entry into a .csv file, and verify that the FromStatusReasonInt (ID: 303554300) and ToStatusReasonInt (ID: 303804100) fields have values.
Verify the status is marked as Deleted if there is any duplicate entry in the APR:SYS Approval Definition (Approval Process Configuration) form.
UPDATE_CHG_DATA_2_SET_APR_PROCESSLIST task that updates and initializes the approval process list that is required for Approval Preview in the BMC Remedy Change Management application. This list was not persisted in earlier releases, but has been made to persist with version 8.1 and later versions to optimize the roundtrips to the AR System server.
Verify that the preview of approver list shows the approvers for change requests for which approval mapping was added and moved to the next review approval phase. (You may need to refresh the change request to check the approver list.)
Verify that the process name was changed to the Change Level CI-IA process for the change request for which an ad-hoc approver was added and where the approval process was not started. In addition, Verify the process name was not changed to the Change Level CI-IA process for the change request for which ad-hoc approver was added and where the approval process was started.
UPDATE_PRIORITY_BASEDON_URGENCY_IMPACT updates the value in the Priority field in the CHG:CFG-Prioritization (Prioritizations) for Global Company form based on the values in the Impact and Urgency fields. (In previous versions, Priority was based only on Urgency.)
Verify that the value in the Priority field (for example, Critical) in the CHG:CFG-Prioritization (Prioritizations) for Global Company form is updated based on values in the Impact (for example, 1-Extensive/WideSpread) and Urgency (for example, 2-High) fields.
APPR_MAPPING_FIX_ASSIGNMENT_AVAILABILITY corrects the Approval Mapping for individuals based on the Status in the People record and for groups based on the group's Status and the presence of anyone in the group with the approval role.
UPDATE_CHG_AP_PROCESS_CONFIG_N_NOTIFY identifies configuration changes (if any) in the AP:Process Definition form for all out-of-the-box approval processes, and notifies configuration users to review the changes manually.
Verify that configuration users are notified if any configuration changes were made in the AP:Process Definition form for all out-of-the-box approval processes.
To apply the BMC Remedy IT Service Management post-DDM packages
Run the Delta Data Migration Tool to migrate data for all applications, including BMC Remedy IT Service Management. After the migration has completed, install the BMC Remedy IT Service Management post-delta data migration package.
- Open a command window, and navigate to the Utilities\post_DDM\ITSM\patches folder.
Run the batch file with the following command-line options:
setup.bat "<destinationServer>" "<user>" "<password>" <port>
- Follow the prompts and wait for the batch file to finish.
- Check the logs located in the Utilities\post_DDM\ITSM\patches\Logs folder to ensure that the package installed correctly.
If there are any errors, correct them before re-installing the bundle.