When you set up the Health Verification package, we create a platform cache org
partition with 3 MB called HealthVerification in the safetycloud namespace. The Health
Verification package uses the cache to improve the performance of status look-ups. Depending on
your data volume, usage patterns, and performance requirements, you can allocate more space to
the cache org partition.
Required Editions
Available in: Enterprise and Unlimited Editions
User Permissions
Needed
Allocate Space to Cache Org Partition
API Enabled
Modify Metadata Through Metadata API Functions
Determine how much space your cache org partition needs
Each Health Verification record in the cache consumes approximately 750 bytes of space. So,
depending on how many records you want to store in the cache for effective look-up, you can
allocate the appropriate amount of space. For example, If you expect to have 20,000 Health
Verification records in the cache (at 750 bytes each), you need 20,000 x 750 bytes =
15,000,000 bytes, or 15 MB,
Note If the cache capacity doesn’t meet your needs, you can
request additional platform cache. For more information, see Request Additional Platform
Cache.
Change the space allocated to the cache org partition
Use the Platform Cache Partition tool in Setup to increase the partition size.
From Setup, navigate to Custom Code | Platform Cache.
In the bottom panel, click Edit.
Change the value for Org Cache Allocation, and click Save.
Determine how much of the platform cache is being used
To determine how much of the platform cache is being used, check the Platform
Cache Diagnostics page.
From the User Detail page, make sure Cache Diagnostics is
enabled for the user.
From the Platform Cache Partition page, select the partition name.
Click the link to the Diagnostics page for the partition.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.