Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

General settings

Updated on January 13, 2022

The configuration of the module is maintained in the D_ReqConfigurationdata page. 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 LoadConfiguration_Ext extension point to make changes to following settings (the most relevant properties, that are available in the D_ReqConfiguration data page):

Pega Client Lifecycle Management for Financial Services Implementation Guide
LastGeneration
Source: DSS – PegaCLMFS Requirements/LastGeneration
Default Value: 2

Use to determine the last version of the requirements functionality that is installed in the system. It is set through the deployment of the requirements functionality and must not be maintained by consumer applications.

ActiveGeneration
Source: DSS – PegaCLMFS Requirements/ActiveGeneration
Default Value: 2 (8.5 installs), 1 or <empty> (upgrades to 8.5)

Use to determine the active generation of the requirements functionality in CLM application. If the setting is set to 1 or blank, the application uses the legacy version of the module. A value of 2 indicates that the new version must be used.

LocatorModifierUseDefault
Source: DSS – PegaCLMFS Requirements/LocatorModifierUseDefault
Default Value: true

The requirements synchronization engine uses 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

Use 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

Use 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, is used as the prefix of the requirements being added.

RNGDocPrefix
Source: Initialization Data-transform (LoadConfiguration)
Default value: D

During the maintenance of requirements, is used as the prefix of the documents being added.

pyRuleSet
Source: Initialization Data-transform (LoadConfiguration)
Default value: <empty>
The Requirements Portal uses to determine the ruleset where new and updated rules are saved.
pyRuleSetVersion
Source: Initialization Data-transform (LoadConfiguration)
Default value: <empty>

The Requirements Portal uses to determine the ruleset version where new and updated rules are saved.

pySelectedApplicationName
Source: Initialization Data-transform (LoadConfiguration)
Default value: <empty>

The Requirements Portal uses to determine the application where new and updated rules are saved.

pySelectedBranchIdentifier
Source: Initialization Data-transform (LoadConfiguration)
Default value: <empty>

The Requirements Portal uses 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.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us