When an autopopulated property defined by a key or parameter is accessed, the performance of the application during run time might be less than expected. The application constantly monitors changes in keys and parameters, which is not required all the time, and therefore slows performance.

In the latest version of the Pega 7 Platform, the application can automatically identify whether keys or parameters have changed. This functionality eliminates the need for constant monitoring of the keys and parameters resulting in better performance. However, if you recently upgraded to the latest version of the Pega 7 Platform, you must do the following steps to gain the performance benefits:

• Run the pzReSaveAutoPopulatePropertiesactivity. This activity enhances the existing ruleset performance by saving all the properties again.

• Save each property to a higher ruleset version.

Troubleshooting

Autopopulated property performance does not improve despite running the activity. Why?

When an autopopulated property has a key or parameter that is a backward chained expression or the expression has nested backward chained expressions, the application cannot detect changes. No performance improvement is seen in this case.

How do I know if performance has really improved?

You can try a simple exercise to verify. Change the value of an autopopulated property (for example, “CURRENTVALUE” to “VALUE1”) and run the activity that reads this property. Change the value again (“VALUE1” to “VALUE2”) and run the activity again. Use the tracer to analyze the number of times the data page is refreshed. From the results, you can deduce whether performance has improved.

Is it possible to configure selected properties this way?

No.

Will these performance improvements affect my applications?

No.

An error occurred when running the pzReSaveAutoPopulateProperties activity. What can I do?

Contact Pegasystems Global Customer Support.