Siebel 18.104.22.168 - Object Tagging related Questions
(Doc ID 1638923.1)
Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 22.214.171.124 [IP2013] and later
Information in this document applies to any platform.
We are trying to upgrade to 126.96.36.199 from 188.8.131.52.
1. 2 Developers modifying the same BS function / BS event (for example PreInvoke) with 2 different tags. If the SDF generated second time doesn't include changes done with first tag, then when second SDF is imported after importing first SDF, first tag changes are getting lost.
2. 2 Developers modifying the same BC field (for example one is setting Force Active and another is making the field Required) with 2 different tags. If the SDF generated second time doesn't include changes done with first tag, then when second SDF is imported after importing first SDF, first tag changes are getting lost.
This basically seems the issue when two different tag changes are done on a component for which one XML tag is generated in SDF. Request you to confirm if this is known issue and if any fix is available for the same. In Reference to the first point, it becomes critical when multiple developers are working on same BC like "Service Request", which is base component of Services module.
Are there any other such limitations with object tagging feature of 184.108.40.206 version?
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.|