Curam caches Code Table data on both the server and client applications. The row on this table holds the latest version number of the cached data to ensure that all client and server caches are kept in sync.

Example

User Ronan Rooney uses the administration screens to make changes to a Code Table. He clicks 'Save' and the Curam Server stores his changes on the Code Table Item table.

User Ronan Rooney then clicks the 'Publish' button and the Curam Server:

• retrieves the row on this table for the Code Table cache. The version number currently on the row is 3;
• increments the version number on this row to 4 and stores it on the database; and
• publishes a 'cache update' message (including the version number of 4).

Each running instance of the Curam client application and server application receives the 'cache update' message and clears its cache. Some of the client application instances receive the message before the servers do; when these clients request the codetable cache from a server, they pass the version number to ensure that they are not supplied with a stale copy of the cache.