General settings
The configuration of the module is maintained in the data-page D_ReqConfiguration. Most of the settings are loaded from dynamic system settings that can be changed as required. The remaining settings are set through the data-page initialization data-transform (use the extension point LoadConfiguration_Ext to make changes to these settings). This is a summary of the most relevant ones (all properties available in data-page D_ReqConfiguration).
- LastGeneration
- Source: DSS – PegaCLMFS Requirements/LastGeneration
- Default Value: 2
Used to determine the last version of the requirements functionality installed in the system. It is set through the deployment of the requirements functionality and should not be maintained by consumer applications.
- ActiveGeneration
- Default Value: 2 (8.5 installs), 1 or <empty> (upgrades to 8.5)
- Source: DSS – PegaCLMFS Requirements/ActiveGeneration
Used to determine the active generation of the requirements functionality in CLM application. If the setting is set to 1 or blank, the application will use the legacy version of the module. A value of 2 will indicate that the new version should be used.
- LocatorModifierUseDefault
- Source: DSS – PegaCLMFS Requirements/LocatorModifierUseDefault
- Default Value: true
Used by the requirements synchronization engine to determine the use of default sets. During that process, the system tries to find the sets marked with the locator, key and modifier passed by the application (for example, a CIP, Entity, UK). If there is no match and this setting is set to false, the engine does not create any requirement. If this setting is set to true, however, the system performs another query, this time using the same locator and key and with a modifier 'Default' (for example, a CIP, Entity, Default).
- RNGSkipApproveStage
- Source: DSS – PegaRequirements Requirements/SkipApproveStage
- Default Value: false
Used during the processing of requirement cases to automatically skip the approval stage. It can be used in combination to the extension point RNGSkipApprovalStage_Ext, which can be configured to skip the approval in specific circumstances.
- RNGSkipValidateStage
- Source: DSS – PegaRequirements Requirements/SkipValidateStage
- Default value: false
Used during the processing of requirement cases to automatically skip the verification stage.
- IsDMSDocLibraryEnabled
- Source: DSS – PegaRequirements Requirements/DMS/DocLibraryEnabled
- Default value: false
Use to display additional tab to allow users to select documents from DMS repositories.
- IsDMSOutboundEnabled
- Source: DSS – PegaRequirements Requirements/DMS/OutboundSynchronizationEnabled
- Default value: false
Use to enable the outbound synchronization of document metadata with DMS systems.
- IsDMSOutboundAsyncModeEnabled
- Source: DSS – PegaRequirements Requirements/DMS/OutboundAsyncModeEnabled
- Default value: false
Use to enable the asynchronous mode of the outbound synchronization of document metadata with DMS systems.
- LegacyDocUpgradeStrategy
- Source: DSS – PegaCLMFS Requirements/LegacyDocUpgradeStrategy
- Default value: OnDemand
In upgrade scenarios, it determines the active upgrade strategy (OnDemand and Bulk).
- RNGReqPrefix
- Source: Initialization Data-transform (LoadConfiguration)
- Default value: R
During the maintenance of requirement sets, used as prefix of the requirements being added.
- RNGDocPrefix
- Source: Initialization Data-transform (LoadConfiguration)
- Default value: D
During the maintenance of requirements, used as prefix of the documents being added.
- pyRuleSet
- Source: Initialization Data-transform (LoadConfiguration)
- Default value: <empty>
- Used by the Requirements Portal to determine the ruleset where new and updated rules will be saved.
- pyRuleSetVersion
- Source: Initialization Data-transform (LoadConfiguration)
- Default value: <empty>
Used by the Requirements Portal to determine the ruleset version where new and updated rules will be saved.
- pySelectedApplicationName
- Source: Initialization Data-transform (LoadConfiguration)
- Default value: <empty>
Used by the Requirements Portal to determine the application where new and updated rules will be saved.
- pySelectedBranchIdentifier
- Source: Initialization Data-transform (LoadConfiguration)
- Default value: <empty>
Used by the Requirements Portal to maintain new and updated rules in a branch.
- RequirementAssetsConfigurationClass
- Source: Initialization Data-transform (LoadConfiguration)
- Default value: <empty>
Set this value in the LoadConfiguration_Ext rule to use a specific class for all the rules.
- ReqCaseWorkClass
- Source: DCR - D_AppExtension.WorkClass_Requirement
- Default value: PegaCLMFS-Work-Requirement
Name of the class that implements the requirement case.
Previous topic Migrating document metadata Next topic Configuring client outreach