Upgrading › Planning Your Upgrade › Retaining Your Customizations

Retaining Your Customizations

Before you upgrade to CA SDM Release 12.7, consider the following information for your customized product:

Note: When you close the Migration Console before the upgrade completes, then the process continues to run in the background.

• Custom Reports—When you customize the reports that access database tables from previous versions and that have been moved to renamed tables, the column names have been changed in Release 12.7.

  Note: For information about the tables, see the CA SDM Technical Reference Guide.

• Customized Forms—Upgrading to CA SDM Release 12.7 retains the customizations of the forms from the previous release of CA SDM. However, you cannot view the CA SDM Release 12.7 functionality on the customized forms after you upgrade.
• Customized Admin Tree—When you customize the Admin tree in Unicenter Service Desk r11.0, then these changes are not upgraded due to modifications in the architecture to support the role-based user interface. These Admin tree customizations include the addition of new nodes, renaming of existing nodes, modifying access types, or other data alterations. To use the customizations, do the following:
  1. Before you upgrade, review your Unicenter Service Desk r11.0 Admin tree and note any customizations that you want to use after upgrading.
  2. After the upgrade completes, identify which roles have Admin tree customizations.
  3. Apply the customizations to the appropriate CA SDM Release 12.7 role-based Admin trees.
  4. Review and test to verify that the desired functionality has been retained.
• Customized Form Buttons—After the upgrade completes, buttons on customized forms in /site/mods/htmpl that did not have quotes around the msgtxt(n) part of the code result in an error message, instead of the button name.

  For example, in the detail_cr.htmpl form, modify msgtxt(441) with quotes as follows to display the correct button name:

  ImgBtnCreate("btnchg", “msgtext(441)”, "detailSave('NEW_CHANGE')",
  true, 0, msgtext(440)); // Save and Create Change Order
  

• Retaining Customizations—When you need the CA SDM Release 12.7 functionality and would like to preserve your customizations from a previous release then redo the customizations on a base CA SDM Release 12.7 form, which has the Release 12.7 functions.

  Note: When you customize the acctypedtl.rpt and acctypesum.rpt reports, then the return data in CA SDM Release 12.7 is obsolete.

• Notification Rules—When you remove the default activity notifications Contact, Object Contacts, and Contact Types from the previous installation of CA SDM and want to retain this functionality, then note the default contacts removed before migration. After you upgrade to the new version, remove the default Notification contacts again.
• Role-based Functionality—Upgrading can cause issues with the role-based functionality. Consider the following information:
  • When you customized any of the following forms, then they are considered read-only by the Web Screen Painter in CA SDM Release 12.7 and they include an xxx_site.htmpl version where you can use custom code:
    • ahdtop.htmpl
    • menu_frames.htmpl
    • reports.htmpl
    • std_body.htmpl
    • std_footer.htmpl
    • std_head.htmpl
    • styles.htmpl
    • msg_cat.js
    • menu_frames_role.htmpl
• Customized HTMPL Files—Consider the following information:
  • All customized HTMPL files retain their default menu bar settings after you upgrade. A pop-up window inherits its menu bar from the main page tab, as a result of the role-based user interface. Customized HTMPL files are not available on the customized forms from the previous release after the upgrade.
  • CA SDM Release 12.7 does not use some customized HTMPL files from previous releases. The migration script executes the perl script $NX_ROOT/bin/migrate_to_r12_7_web_check.pl that appends the files with the incompatible_for_r2_7 extension. After migration completes, open $NX_ROOT/site/web_check_files.txt with a text editor to see the list of incompatible forms for Release 12.7.
  • If you customized the list_dblocks.htmpl file in a previous release of CA SDM, this form does not work in CA SDM Release 12.7. If you customized the Admin Tree to display the list_dblocks.htmpl in other parts of the tree, the customization does not work after you migrate. Modify the form manually to use the new URL and form. To complete this modification, click Security and Role Management, Menu Tree Resources and open Current Locks. Update the resources with the following CA SDM Release 12.7 string:

    OP=SEARCH+FACTORY=record_lock+QBE.NN.lock_time=NULL 
    

• Foreign Keys—When the upgrade process detects referential integrity issues while attempting to reset foreign keys then the errors appear in the migration.log file. The associated foreign key sets to a predefined valid reference.
• Primary/Secondary Server, Web Director Configuration—When your previous installation was configured to use secondary servers, or web directors, then run $NX_ROOT\samples\pdmconf\pdm_edit.pl after upgrading. Follow the steps defined in pdm_edit.pl to complete the configuration.

  Note: The secondary servers and web directors work when you run pdm_edit.pl on an upgraded system.

• CA Support Automation Divisions—When you migrate the divisions to tenants, then convert this data before enabling and configuring Support Automation in CA SDM Release 12.7.