Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Porting customizations

When you installed BMC Cloud Lifecycle Management 2.1, you might have customized one or several components in the solution to suit your business needs. This section provides instructions for porting those customizations to version 3.0 when you perform the upgrade.

My Cloud Services Console (end-user portal)

If you customized the End User Portal or CMU:ServiceInstances form and its related workflow (CSM:USI:<workflow name>) when you installed Cloud 2.1, for example, added Operator Action customization or made any customizations, perform the following steps to port those customizations. If you did not perform any customizations to the CMU:ServiceInstances form or its related workflow, you can skip this topic.

Note

The full functionality of the Cloud 3.0 End User Portal or Service Instances workspace components might not be present if you do not perform the steps in this section.

After you upgrade the End User Portal component, the old form that was used for the Service Instances workspace (CMU:ServiceInstances) will be renamed to CMU:ServiceInstances_21. When you log on to BMC Remedy Developer Studio in the recommended customization mode, you should see the following changes:

  • If an overlay existed for the CMU:ServiceInstances form, it will be renamed to CMU:ServiceInstances_21.
  • Any custom workflow objects that were attached to this form will remain intact and will be attached to the CMU:ServiceInsatnces_21 form.
  • Any workflow objects with an overlay that are still being used by Cloud 3.0 will continue to exist and will be attached to the CMU:ServiceInstances_21 form.
  • Any workflow objects with an overlays that were deleted, will no longer exist.

To port customizations to the My Cloud Services Console (end-user portal) component

  1. Create a new overlay of the CMU:ServiceInstances form.
     For more information about how to create overlay forms, see?
  2. Copy any UI elements that you added in the BMC Cloud Lifecycle Management 2.1 overlay to the new overlay that you created in the previous step.
     UI elements that you added to the BMC Cloud Lifecycle Management 2.1 version of the CMU:ServiceInstances form will be preserved on the overlay of the CMU:ServiceInstances_21 form post upgrade. If you want to port these UI elements in BMC Cloud Lifecycle Management 3.0, you must copy them to the new CMU:ServiceInstances overlay.
  3. If required, reapply any customizations to the existing cloud fields, for example, additions to selection fields, rearrangement of fields, display property changes, and so on.
  4. Attach any custom workflow objects that were created in BMC Cloud Lifecycle Management 2.1 (which are now attached to the CMU:ServiceInstances_21 form) to the CMU:ServiceInstances form if they are still required.

  5. Review and compare any workflow objects with overlays (which are now attached to the CMU:ServiceInstances_21 form) to the new base workflow object that was installed with BMC Cloud Lifecycle Management 3.0.
     For example, if you have an overlay of workflow object CMU:USI:OnLoaded_CG that is attached to the CMU:ServiceInstances_21 form, you should compare it to the base object with the same name that is attached to the CMU:ServiceInstances form. 

    Tip

    To view the content of the base workflow objects, you must use the Base Development mode in BMC Remedy Developer Studio.

  6. After the comparison, if you determine that there are changes to the base workflow objects that were shipped with Cloud 3.0, BMC recommends that you delete your workflow objects that have an overlay and re-apply your customization by creating a new overlay of the base workflow object shipped with Cloud 3.0.

  7. If you determine that there were no changes in the Cloud 3.0 base workflow, attach your workflow object with overlays to the CMU:ServiceInstances form. 

    Note

    If you did not overlay any CMU:USI:xxx workflow objects that are not attached to the CMU:ServiceInstances form, the End User Portal might not function properly.

  8. Flush both the mid tier and your browser cache.
  9. Verify your customizations.

Porting BMC Network Automation API customizations

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*