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.

Troubleshooting: "Cannot save Index-CircumstanceDefinition" when saving Circumstance Definition

Suggest edit Updated on May 2, 2008

Symptom

When you attempt to save a Circumstance Definition rule, the following error and warning appears at the bottom of the rule form:

>>General Error>>  **Save failed:  Cannot save instance of class Index-CircumstanceDefinition; it belongs to fully exposed table pr_index_circumstance_def in database PegaRULES, but the instance has properties which do not correspond to columns:  property1, property2
When you attempt to save a Circumstance Definition rule, the following error and warning appears at the bottom of the rule form:

>>General Error>>  **Save failed:  Cannot save instance of class Index-CircumstanceDefinition; it belongs to fully exposed table pr_index_circumstance_def in database PegaRULES, but the instance has properties which do not correspond to columns:  property1, property2
>>Warning>> Can’t create Circumstance Index because the following columns can’t be created:  property1, property2

 

These messages indicate that the database account you are using does not have CREATE TABLE and ALTER TABLE privileges in the database (see How to restrict default database privileges ). 

The General Error indicates that the rule was not saved.

The warning condition does not prevent you from saving the circumstanced rule, but the circumstance information is not added to the index table in the database, so this rule will not be found for the Find by Circumstance report.

 

Solution

Workaround

The General error prevents this rule form from saving. 

  1. Have your DBA create the appropriate column or colum in the pr_index_circumstance table.
  2. When the columns are present, you can save this rule.
Resolution

This General Error does not occur in V5.4SP1+. In addition, the warning message provides the explicit Data Definition Language statements needed by a DBA.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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