Sharma asked 2 years ago
Title : Siebel Open UI Blank Screen or Aurora Side Menu Not Visible in Environment Upgraded to Innovation Pack 2014. Can you help.

Question :

Siebel Open UI Blank Screen or Aurora Side Menu Not Visible in Environment Upgraded to Innovation Pack 2014. Can you help.

1 Answers
Kumar HarshKumar Harsh Staff answered 2 years ago

GO through this: 
 
SYMPTOMS
 
ACTUAL BEHAVIORS 
—————
After upgrading from 8.1.1.11 (IP 2013) to 8.1.1.14 (IP 2014) it has been noticed that the Aurora side menu bar is not visible.
 
However, in a newly installed 8.1.1.14 (IP 2014) environment the side menu IS visible. Additionally, when using the Aurora Tree or Aurora Tab themes the user interface is correct. An additional symptom is an incompletely rendered Open UI screen for mobile clients, for example:

EXPECTED BEHAVIORS
———————–
The expectation is that the side menu is visible in an upgraded Siebel environment similar to a standard installation environment.
 
ERROR
———————–
The following error may also be seen in the browser console:
Uncaught Type Error : B.ShowUI is not a function
 
STEPS
———————–
The issue can be reproduced at will with the following steps:
1. Install 8.1.1.11
2. Upgrade environment to 8.1.1.14
3. Log in to application using Open UI mode.
NOTE: Please note that if you see a crash when navigating to User Preferences > Behavior, please see:
Doc ID 1963207.1 – Object Manager Crash Access The User Preference Settings In Open UI After IP 2014
 
CAUSE
The cause of the issue is the sequence of the relevant Javascript files in Administration – Application > Manifest Administration.

In the standard application we see:

Administration – Application > Manifest Administration

For:
UI Object
Type: Navigation
Usage Type: Physical Renderer
Name: NAVIGATION_SIDE

Files:

Inactive

Sequence 

Name

N

1

siebel/hamburgernav.js

N  

2

siebel/accnavigationphyrender.js

In the upgraded environment the following is seen:
Files:

Inactive

Sequence

Name

N

 

siebel/accnavigationphyrender.js

N

 

siebel/hamburgernav.js

 
This causes the siebel/accnavigationphyrender.js file to be loaded first and the siebel/hamburgernav.js second as can be seen in the log:
Upgraded SERVER database:
GenericLog GenericInfo 3 0000000254bb0ee8:0 2015-01-18 17:43:13 ***MANIFEST_LOG*** Adding File: siebel/accnavigationphyrender.js
GenericLog GenericInfo 3 0000000254bb0ee8:0 2015-01-18 17:43:13 ***MANIFEST_LOG*** Adding File: siebel/hamburgernav.js
Newly installed SAMPLE database:
GenericLog GenericInfo 3 0000000254bb0e2c:0 2015-01-18 17:50:29 ***MANIFEST_LOG*** Adding File: siebel/hamburgernav.js
GenericLog GenericInfo 3 0000000254bb0e2c:0 2015-01-18 17:50:29 ***MANIFEST_LOG*** Adding File: siebel/accnavigationphyrender.js
Newly installed SERVER database:
GenericLog GenericInfo 3 0000000254be07fc:0 2015-01-20 07:38:21 ***MANIFEST_LOG*** Adding File: siebel/hamburgernav.js
GenericLog GenericInfo 3 0000000254be07fc:0 2015-01-20 07:38:21 ***MANIFEST_LOG*** Adding File: siebel/accnavigationphyrender.js
The following bug was logged to look into this further:
Bug#20847685 – MANIFEST FILES FOR NAVIGATION_SIDE ARE NOT SET IN SEQUENCE
 
SOLUTION
Please note that the bug has not yet been fixed, however, the below workaround is available:
Please note that the standard Manifest records cannot be updated and as direct SQL is not supported the following solution can be used to resolve this issue:
1. Lock BC ‘UI Object Expression’
2. Inactivate the following BC user property:
Aspect Child BC ReadOnly: ReadOnly
3. Query for BC ‘UI Files UI’
4. Inactivate the following BC user property:
Name: BC Read Only Field
5. Compile BCs into SRF.
6. Login to Siebel using new SRF
7. Go to Administration – Application > Manifest Administration.
8. Query for Name = NAVIGATION_SIDE
9. In the Files applet (UI Object Expression Files List Applet) change:

FROM:

Inactive

Sequence 

Name

N

 

siebel/accnavigationphyrender.js

N  

 

siebel/hamburgernav.js

 
TO:

Inactive

Sequence 

Name

N

2

siebel/accnavigationphyrender.js

N  

siebel/hamburgernav.js

 
e.g. ensure that the sequence number for siebel/hamburgernav.js is BEFORE siebel/accnavigationphyrender.js
10. Re-test issue and confirm that side menu is now visible. 
11. Once confirmed fixed, go back to Siebel Tools and reactivate the user properties that you inactivated in step 2 and 4.
12. Re-compile the BCs into the SRF.

Cubastion is among a very small number of specialized Siebel CRM Oracle Gold Partners in SME.