Replacement caches
Introduction
Having chosen to configure cache replacements for a virtual environment, a new replacement rule is displayed, ready for you to configure:
Having defined the first rule, you can add more - you must create one replacement rule for every cache that you need to replace in every process flow that will run in this environment.
Need to know
Please consider the cache type used when replacing caches in master process flows.
Company
Yes
Yes
We recommend that you always replace company caches in virtual environments, unless you have a good reason for not doing so. This ensures that caches are unique for each environment.
Keep in mind that cache keys are NOT replaced. Provided that you replace the company cache in each virtual environment, this is not an issue - the cache in each environment will be unique.
If, for some reason, you do not take this approach, please ensure that the given cache key in your master process flow utilises variables to ensure that it's unique at runtime - otherwise, cached data from one environment may overwrite data from another.
Flow
Yes
Yes
We recommend that you always replace flow caches in virtual environments, unless you have a good reason for not doing so. This ensures that caches are unique for each environment.
Keep in mind that cache keys are NOT replaced. Provided that you replace the flow cache in each virtual environment, this is not an issue - the cache in each environment will be unique.
If, for some reason, you do not take this approach, please ensure that the given cache key in your master process flow utilises variables to ensure that it's unique at runtime - otherwise, cached data from one environment may overwrite data from another. Please see Referencing variables for unique cache keys for more information.
Flow run
No
Yes
Behind the scenes, each cache key for a flow run cache is appended with a unique flow run id - although you never see this in the dashboard, it does mean that these caches will never clash between virtual environments.
However, if required, you can reference an environment variable in the cache key name, so the cache key is immediately identifiable for each virtual environment. please see Referencing variables for unique cache keys for more information.
Defining replacement rules for a cache
Select the required ORIGINAL cache
Use the original dropdown list to select the first company cache in a 'master' process flow that must be replaced when this process flow runs in the given virtual environment - for example:
Select the required REPLACEMENT cache
Use the replacement dropdown list to select the replacement cache that must be used when this process flow runs in the given virtual environment - for example:
Confirm your selections
Click the create button (associated with this replacement rule) to confirm your selections:
The rule is added:
Add more replacement rules for caches
To add another replacement rule for a cache, click the top-right create button:
Update the new rule as required, then click the associated create button to confirm your selections:
Repeat as many times as needed to define all required cache replacements for all process flows that will be running in this virtual environment.
Last updated