So I found that if you change the value of an Action that has already been processed and cached on a client, that cached action doesn't get updated.
I think there needs to be some form of Versioning set on the action, so that if you open and edit the action it increments the number so that when the cache loads and sees the version is behind it updates that cache. This will prevent us from having to remove cached action at logoff as we do now to get changes.
I did a write-up on the issue and our workaround here -
Question
Jeff Riechers
So I found that if you change the value of an Action that has already been processed and cached on a client, that cached action doesn't get updated.
I think there needs to be some form of Versioning set on the action, so that if you open and edit the action it increments the number so that when the cache loads and sees the version is behind it updates that cache. This will prevent us from having to remove cached action at logoff as we do now to get changes.
I did a write-up on the issue and our workaround here -
https://www.jeffriechers.com/wiki/wemchanging-actions-not-caching/
Link to comment
6 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now