1. Applications Administration Guide
  2. Modifying LOVs in Integration Workspace in DR Environments

Modifying LOVs in Integration Workspace in DR Environments

There is no workspacing of LOVs at the development Workspace level in DR environments. However, each integration branch (including the MAIN branch) has its own full copy of seed data or LOVs and there is complete isolation of the seed data across the integration branches (there is parallel development isolation at the Integration Workspace level, not at the development Workspace level). As a result, LOV changes carried out by any user are immediately visible across the entire scope of a specific integration branch – that is, changes are visible at the integration branch level as well as at all the development branches under it.

Up until Siebel CRM 20.2 Update release, it was mandatory to create a development Workspace in order to modify LOVs, even though there was no isolation at the development Workspace level. To make LOV development in DR environments more intuitive, given that LOV modifications happen at the scope of the Integration Workspace, LOV modifications should be performed directly against the Integration Workspace. This would eliminate the necessity of creating a development Workspace if the user wants to make LOV changes only (and is consistent with the isolation model used for seed data). Also, this is required for executing scripts that update LOVs on MAIN or Integration Workspaces.

As of Siebel CRM 20.3 Update release, you can modify LOVs by opening either the development Workspace or Integration Workspace in a DR environment. When you open the development or Integration Workspace in a DR environment and modify LOVs, the changes will always happen at the Integration Workspace level. This is the default behavior. You can enable or disable LOV modification in the development Workspace of DR environments by setting the DisableSeedUpdOnDevWS system preference as follows:

  • If DisableSeedUpdOnDevWS is set to True, then LOV modification is not allowed in the development Workspace. In this case, LOVs are read-only.

  • If DisableSeedUpdOnDevWS is set to False, then LOV modification is allowed in the development Workspace. By default, DisableSeedUpdOnDevWS is set to False.