Skip Navigation
Expand
Changes in workspace are not taking effect when loading workspace
Answer ID 9275   |   Last Review Date 12/24/2018

Why when I make changes to a workspace and save does it not take effect when I load the workspace with an agent's profile who has that workspace?

Environment:

Workspace Elements, Staff Accounts
Oracle Service Cloud, All versions

Resolution:

When testing, you would like to see the changes you just made.  In order to do this, it may be necessary to close the workspace and re-open it. This will pull the optl cache update and you will be able to see the new modifications you have made. You can also choose to use the Preview button within the workspace editor; it may be found on the Home Ribbon option and you can choose between New Record and Opening a Record.

Cause:

After making a modification to the workspace you still have a cached copy residing on your computer for the agent account you are logged into. If you move a tab around, update a workspace rule, or even hide a tab these changes will not take effect immediately when you load this workspace using an agents account.

The application cache is used to reduce the number of persistent connections to the database and houses intermediary data for transactions that occur often such as Menu Control Drop-downs or Workspaces.

Available Languages for this Answer:

Notify Me
The page will refresh upon submission. Any pending input will be lost.