This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

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

Reconciling customizations to the multi-tenancy model

This topic describes how to reconcile the most common types of multi-tenancy model customizations. Perform this work before you run the multi-tenancy update to preserve the customizations.

Note

This information applies only to forms that are amendeded by the multi-tenancy update. If you made updates to any forms that are not overwritten by the update, you do not need to reconcile those changes.

The customizations covered by this topic include:

Modified workflow for setting existing dynamic group fields

If you modified out-of-the-box workflow that sets existing dynamic group fields (for example, field 112), you must perform actions to reconcile the customization before you run the update and after you run the update.

Before you run the multi-tenancy update

Open the Application Maintenance console, find the forms on which you made the modifications, and move the forms offline. For a description of how to use the Application Maintenance console, see Managing the multi-tenancy update

After you run the multi-tenancy update

Depending on the nature of the customization that you made, you might need to run a custom SQL script to apply the multi-tenancy update to the forms that you moved offline while at the same time preserving the customized multi-tenancy data. To understand how to do this, see the following example.

Example

Note

This is only an example. Any reference to what the multi-tenancy update does is hypothetical.

  1. You have an out-of-the-box form with the following field ID 1 permission values: Unrestricted Access and Assignee Groups (Field 112).
  2. The out-of-the-box workflow sets Field 112 to the permission groups of Company 1 and Company 2.
  3. You modified the out-of-the-box workflow to set Field 112 to include a custom Company field, Company 3.
  4. The multi-tenancy update adds an existing Company permission to Field 112 that was originally omitted, Company 4.
  5. Because the multi-tenancy update overwrites Field 112 with the Company 1, Company 2, and Company 4 permission groups, the custom Company field that you added, Company 3, is not included in the updated form.
  6. To add the Company 3 permission group to Field 112, you create a custom SQL update that adds all four company permission groups to Field 112.
  7. You also reconcile the out-of-the-box workflow that sets Field 112 with the workflow changes that you made in step 4; that is, you change the workflow to include Company 4.

Disabled workflow that sets existing dynamic group fields

If you disabled out-of-the-box workflow that sets the parameters for existing dynamic group fields (for example, the permission groups), you must open the Application Maintenance console, find the form on which you disabled the workflow, and move the multi-tenancy maintenance record offline. This action prevents the record from being overwritten by the multi-tenancy update. For a description of how to use the Application Maintenance console, see Managing the multi-tenancy update.

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.

Comments