A New Full Compile SRF has a Different Behaviour when Compiled In Dev versus Prod Database for the Same Repository. Why?
(Doc ID 1362039.1)
Last updated on FEBRUARY 03, 2019
Applies to:Siebel Tools - Version 126.96.36.199 SIA to 188.8.131.52  [Release V8]
Information in this document applies to any platform.
Reviewed for relevance "16-DEC-2016".
On : 184.108.40.206 SIA version, Configuration - General
We have the Account Contact List Applet, which is having a different Look and Feel in the Test and the Production environment. Note that after the repository is migrated to each environment, a new FULL Compile SRF is generated in the new environment.
We are having an issue with the Account Contact List Applet. This applet uses 5 different applet web template modes.
For the New mode, the applet has two web templates with same default sequence number, 0. They are named New and New-Bad.
When we compile the srf in production, the SRF is using the New-Bad web template instead of New web template.
When we checked the event log we found that it is pointing to correct CCAppletForm4Col_E_N_Expanded.swt template in SWE, but it is rendering CCAppletList_E_N_Q.swt which is of New-Bad.
We would like to know how the html rendering happen when there are two web templates with same sequence number for a given mode?"
Snippet of SWE log
processRequest ProcessRequestDetail 4 0000004a4e6e107a:0 2011-09-12 11:23:32 SWE View - GetObjInfo: view=Account Detail - Contacts View
ProcessRequest ProcessRequestWarning 2 0000004a4e6e107a:0 2011-09-12 11:23:32 The control BlankLabel1 is mapped to more than once in the applet of Account Contact List Applet
ProcessRequest ProcessRequestDetail 4 0000004a4e6e107a:0 2011-09-12 11:23:32 SWE SWX Manager - GetAppletSWX: Applet=Account Contact List Applet; Template=CCAppletForm4Col_E_N_Expanded.swt; Container=; mode=2; sequence=0
It is expected that a srf compiled from the same repository but in different environments will always have the same behavior.
The issue can be reproduced at will with the following steps:
In Tools for an existing list applet, set up 2 New Mode applet web templates with different names and the same default sequence of 0.
Compile and test the srf.
Migrate the repository and compile a new srf.
The new srf will use whatever New Mode applet web template is returned by the query first when the SRF is being compiled.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|