How PostInstallDBSetup Fully Workspace Enables List of Values

PostInstallDBSetup has to transform the LOVs in MAIN and other integration Workspaces into the fully Workspace enabled format.

When you apply an update that fully Workspace Enables List of Values, PostInstallDBSetup examines your Repository and updates LOVs in the following ways.

• Determines the parent LOV for all the modified versions.

• Removes duplicate records once the parent is identified.

• Finds Integration Workspaces with modified LOVs.

• Creates a new version of the Integration Workspaces where LOVs have been modified and puts the modified LOVs in those versions.

  • If a modified LOV is in Submitted for Delivery or Rebase-in-Progress when PostInstallDBSetup runs a new version of the integration Workspace is not created for these LOVs. These modified LOVs are tracked in the latest version of the Integration Workspace.

• Adds records to the S_RTC_MOD_OBJ Table for Workspace tracking.

  Note: Only the LOVs that are not delivered into the parent are tracked.

PostInstallDBSetup will do the following when converting LOVs to fully Workspace enabled LOVs.

1. In MAIN, PostInstallDBSetup determines the one true LOV record by comparing versions of the same LOV record and identifying the record with the highest version by the value found in WS_MIN_VER. This record’s WS_SRC_ID will be the value used by all modified version of this LOV so that modifications are all made to this one parent LOV.

2. Once PostInstallDBSetup has determined which LOV record is the main record, all copies in other Integration Workspaces will be deleted from the S_LST_OF_VAL Table. Now the S_LST_OF_VAL Table will have no duplicates. Only those LOVs modified in a Workspace will have a record in S_LST_OF_VAL for that Workspace.

3. Now that MAIN has been organized and S_LST_OF_VAL has been trimmed of duplicate LOV records, PostInstallDBSetup will look at your Integration Workspaces and determine if LOV records have been modified in those Workspaces. Since we track updated records in Workspaces, the utility will then make sure there are the appropriate records in the S_RTC_MOD_OBJ Table for each Workspace where LOVs have been modified.

4. It does this by creating a new version of the Integration Workspace with the changed LOVs. This will create records in the S_RTC_MOD_OBJ Table allowing each Workspace to display what was changed in that Workspace. It will not create new versions of the Integration Workspace for any LOV that was in Submitted for Delivery or Rebase-in-Progress. These are tracked under the latest version of the Integration Workspace in which they have been modified.

5. Deleted records will appear in the end user application such as Call Center as soft deleted. To see these records, open an integration Workspace. In the List of Values List Applet Menu click Show Deleted Records to display them.