Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Open any specification rule.
  2. Save as this rule with any new name, select any value under 'Business Impact' drop down and save it into any unlocked ruleset version.
  3. Create a product rule to just extract jar for the above created new rule.
  4. Try importing in the same instance, say by deleting the newly created rule. Notice that there is an error thrown.

Root Cause

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 
Value: -1

Published April 11, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us