Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Delete LookupList Cache to Refresh LookupList features

Updated on December 28, 2007

Symptom

The LookupList cache is a series of XML files that Process Commander saves on disk. Process Commander then uses this cache of XML files to display features such as List View reports and SmartPrompt lists.

The LookupList cache reduces the number of database searches and provides quicker response times.

If the contents of a cached lookup list become stale or out of date, Process Commander deletes the lookup list file and rebuilds the file the next time the information is requested. This occurs automatically during normal Process Commander processing and when using tools on the standard Process Commander portals.

For example:

  1. Import a new or updated RuleSet.
  2. A message displays stating the import process was successful.

The new classes for the updated RuleSet appear in the drop-down list in the Class Explorer:

However, at times the LookupList XML file may not be rebuilt with the latest information, for example if batch or non-integrated tools are used to load or change rules.  If this occurs, the drop-down list in the example above may not contain the new Classes.

 

Solution

To resolve this issue and refresh the LookupList, you must delete the LookupList cache as follows:

  1. Select Tools > System Management Application to access the System Management tool.
  2. Select the node for which you want to delete the LookupList cache; the following appears:

  1. Select Advanced > ETier Static Content Management; the following appears:

  1. Click Delete Lookup List Cache . You may need to repeat this process on each Process Commander node.
  2. Return to Process Commander and select the LookupList function you attempted earlier, to force the system to regenerate the cache.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us