SRF Compile with the Same Repository in Different Environments like Dev or Prod, Generates a SRF with Different Behavior for a Complex Configuration.
Last updated on MARCH 02, 2017
Applies to:Siebel Tools - Version 126.96.36.199 SIA  and later
Information in this document applies to any platform.
On : 188.8.131.52 SIA  version, Configuration - Dev Env
Compiling the same repository in Development and Productions creates a SRF with a predefault field configuration that works in one environment but not in another.
There is an expectation that the same repository in different Siebel environments like the same 8.1.1 in development, test, stage and production will always generate a srf file that behaves the same in every environment. This expectation is mostly true for the vast majority of cases, but there is a small percentage of cases where this is not true.
The difference in the behavior is caused by the different Siebel environments having different row_ids for the repository objects and this can affect the order that repository objects are viewed when a srf is being compiled.
While this behavior is more commonly seen for tools objects that don't have a sequence number property like Field Pick Maps, and Applet Web Template Items, this behavior can be fixed by adding a sequence number for these properties.
In this situation, the complex configuration was for a field's predefault expression that referenced three other calculated fields.
The issue can be reproduced at will with the customer's Siebel Tools developers database with a complex configuration involving a predefault expression that looks at 3 other calculated fields.
As long as the field with the complex predefault expression has a row_id that is higher than the other fields used in the predefault expression, the srf will have the expected behavior.
It is always recommended to only do the full SRF compile in the development environment and then move that SRF file and the repository to the other environments like test, stage or production as a best practice. This practice will avoid this situation. Since this behavior can be confusing and not obvious to the Siebel Developer a bug has been raised for this test case where the row_id of a field affects the SRF behavior.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms