As well as providing the ability to manage the catalog manually, RPI also automatically catalogs values for any newly-created attributes. This is carried out by the Attribute Value Catalog system task.
Following an attribute’s initial cataloging, the frequency at which it is refreshed is controlled by system configuration setting AttributeRefreshInterval, which controls the number of days between refreshes. Every [n] (where [n] = AttributeRefreshInterval) days since an attribute’s last refresh, attribute counts are refreshed automatically.
These features ensure that any disruption experienced while building selection rules due to having to wait while attribute values are cataloged is kept to a minimum.
Note that auto-cataloged attribute counts are only available once you log off and back into RPI.
An external third party can invoke a refresh of the values of all attributes that share a given target table by inserting the name of the table into data warehouse table RPI_AttributeUpdateRequests. The refresh occurs on execution of the Attribute value catalog system task. Afterwards, the row is removed from RPI_AttributeUpdateRequests. Any refreshed attribute values are available when the client application is restarted.