Cards Caching (Managed Package)

For the managed package runtime, cards, card layouts, templates, custom labels, and profile data load from the VlocityMetadata partition of the Platform Cache when the card is active and viewed from a record page or a community page. You can clear, enable, or disable the user session cache and specific types of data from the Platform Cache.

Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

To confirm your org has enough space allocated to the VlocityMetadata partition or to allocate more space, see Allocating Space in the Platform Cache Partitions.

Clearing Caches

Remove stored data by clearing specific types of data from the platform and user session caches to get the latest available data from the database. See Clear Platform and User Session Caches (Managed Package).

Enabling and Disabling Caches

Enable and disable specific caches.

Cache Type

Description

User Session Cache

Disable user information caching in the session cache. See Disable User Information Caching (Managed Package).

Future Method Calls on the Platform Cache

Enable async calls on the Vlocity platform cache. See Enable Async Caching on the Vlocity Card Framework (Managed Package).

Platform Cache

Disable caching across the Vlocity Cards Framework to get the latest available data directly from the database. See Disable Platform Cache (Managed Package).

  • Clear Platform and User Session Caches (Managed Package)
    For the managed package runtime, remove temporarily stored data by clearing the platform and user session caches to get the latest available data. Cards, card layouts, templates, custom labels, and profile data load from the VlocityMetadata partition of the Platform Cache when the card is active and viewed from a record page or a community page.
  • Disable Platform Cache (Managed Package)
    For the managed package runtime, disable caching across the Vlocity Cards Framework to get the latest available data directly from the database. Cards, card layouts, templates,custom labels, and profile data load from the VlocityMetadata partition of the Platform Cache when the card is active and viewed from a record page or a community page by the end-user.
  • Disable User Information Caching (Managed Package)
    For the managed package runtime, disable user information caching in the session cache. The Vlocity Cards Framework keeps stored user profile data on the VlocityMetadata partition of the Platform Cache. The Cards.UserTrigger caches the user after user information updates, and removes the cached user after the user is disabled or deleted.
  • Enable Async Caching on the Vlocity Card Framework (Managed Package)
    For the managed package runtime, use the Future Method to enable card caching to run in sync with the Vlocity Card Framework. Future method calls are async calls made by an Apex class.