SA-31780

Summary

User observes that after a migration a declare index rule is not populating all defined columns to the associated database table. 

Error Messages

Not applicable

Steps to Reproduce

Not applicable

Root Cause

Suspected environment issue.

Resolution

Perform the following local change steps:

1. Save the database table corresponding to the index class in order to verify that the pr_sys_decchg table contains a row with pxChangeProperty="ColumnName" (ColumnName used to represent an example column title). 
   1. After step 1 the "ColumnName" column will populate for new work items. However for existing work items the column will still have null values.
2. To correct the existing work items:
   1. Create a wrapper activity to open the targeted work page and call ReCreateIndexesForClass,​ passing that page, to recreate index values

Pega Help file says
(https://pdn.pega.com/sites/pdn.pega.com/files/help_v721/procomhelpmain.htm#rule-/rule-declare-/rule-declare-index/related.htm) 
 
"If the index instances in your system are incomplete, or become corrupted or suspect, you can recreate them:

• Execute the standard activity named @baseclass.RecreateIndexesForInstance to create index instances for one base instance."