Application Level Object Changes In Developer Workspace Retaining In Parent Workspace. (Doc ID 2798951.1)

Last updated on JUNE 10, 2022

Applies to:

Symptoms

Application level object changes in developer workspace retaining in parent workspace.

The environment is recently upgraded 21.6 from 20.6, and workspace is defaulted to MAIN.

When making changes to the application level object in a developer workspace (dws), the changes were being retained after inspecting the dws and logging out and back in to MAIN. 

There does not appear to be a way to get back to what should be in MAIN without the dws update.

The update made in the undelivered dws seems to be cached in memory, and opening MAIN workspace and logging in does not help. Only restarting the environment will get back to MAIN as it should be.

 This inspect behavior only occurs with Application level object and not with Applet or Buscomp.

 
The issue can be reproduced at will with the following steps:

1) In Tools, create new dev workspace.

2) Add below scripts to Siebel Universal Agent Application object > Application_Navigate function to raise an error when a certain view is navigate.

5) Log in to the Callcenter application.

6) Open the second dev workspace, Inspect it.

7) Go to "Opportunity Detail - Contacts View", note "test" error is displayed. The expected error is "test2" as the second dev workspace is loaded.

8) Logout and Log back into the application, go the Go to "Opportunity Detail - Contacts View", note "test2" error is displayed.  The expected error is "test1" as MAIN workspace is loaded.

Changes

 The environment is upgraded 21.6 from 20.6.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.