My Oracle Support Banner

The Modified Browser Script Does Not Work On The Target Environment After Migration (Doc ID 2978380.1)

Last updated on OCTOBER 07, 2023

Applies to:

Siebel CRM - Version 23.3 and later
Information in this document applies to any platform.

Symptoms

A browser script was changed in DEV environment. Then the change was migrated via Full Runtime Repository Migration. When the browser script is invoked in the target environment, it run the old browser script in browser cache instead of the new browser script.

1. Create a browser script in Development environment and run Full Runtime Repository Migration so the browser script is copied to the target environment.

2. Login to Siebel client connecting the target environment and call the browser script.

3. Modify the browser script and run Full Runtime Repository Migration again so the modified browser script overrides the old browser script in the target environment.

4. Login to Siebel client connecting the target environment and call the browser script.

5. The old browser script in the browser cache is run instead of using the new browser script in the AI server.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


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