Actions in ITSM applications that trigger caching
In large BMC Remedy AR System applications such as those in the BMC Remedy IT Service Management Suite (BMC Remedy ITSM Suite), some actions performed through the BMC Remedy AR System Administration Console might trigger a client cache load or an admin copy cache. The following table lists ITSM actions that can trigger a client re-cache or an admin copy cache event.
|Action||Client cache load||Admin copy cache|
|Creating, modifying, or deleting a non-support user||NO||NO|
|Creating, modifying, or deleting an organization||NO||NO|
|Creating, modifying, or deleting a company||NO||YES 1|
Creating, modifying, or deleting an association between a company and one of these items:
|Creating, modifying, or deleting a resolution category||NO||NO|
|Adding a company to a support user's access restriction list||NO||NO|
|Deleting a company from a support user's access restriction list||NO||NO|
|Adding a support group to a support user's profile||NO 2||NO|
|Deleting a support group from a support user's profile||NO||NO|
|Adding an application permission to a support user's profile||NO||NO|
|Deleting an application permission from a support user's profile||NO||NO|
|Creating a service target||NO||YES|
|Deleting a service target||NO||YES|
|Adding or removing attributes in the BMC Atrium CMDB||YES 3||YES|
1. Removes the group record associated with the company.
2. Support groups are not used as permission groups in structures. This action does not trigger a client cache load.
3. The form must be open.