Last updated on JULY 09, 2017
Applies to:Siebel CRM Desktop - Version 22.214.171.124.17 [IP2013] and later
Information in this document applies to any platform.
Customer observed the following: the integration object used to synchronize activities is called "CRMDesktopActionIO". This IO contains the component "Action". This component has a integration component key called "Secondary Key" configured in vanilla. The key consists of the fields Description, Planned and Primary Owned By. We want to adjust this IO component key in order to fulfill a demand of our Siebel users. The question now is: can this key be changed or is it vital to the functionality of CRM Desktop?
It seems that Siebel vanilla does not use this kind of key for the internal handling of actions (i.e. table S_EVT_ACT does not have this kind of key in Siebel vanilla). It seems, that the key in the IO has been added solely for CRM Desktop purposes, hence the question if we can change it.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms