Import of Specification rule with Business Impact' fails in DB2
A specification [RULE-APPLICATION-USECASE] rule which has any value selected under 'Business Impact' drop-down fails import in a DB2 instance and on saving the rule.
Steps to Reproduce
- Open any specification rule.
- Save as this rule with any new name, select any value under 'Business Impact' drop down and save it into any unlocked ruleset version.
- Create a product rule to just extract jar for the above created new rule.
- Try importing in the same instance, say by deleting the newly created rule. Notice that there is an error thrown.
A defect in Pegasystems’ code or rules.
Perform the following local-change:
Special quotes which are present in the Business objectives are causing the issue.
Re-entering the data from keyboard instead of copying from Word will solve the issue.
Also create a DASS setting with the following values:
Owning Ruleset: Pega-Engine
Setting Purpose: prconfig/database/batchUpdates/default
0% found this useful