Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 220.127.116.11.17 [IP2013] and later
Information in this document applies to any platform.
On : 18.104.22.168.17 [IP2013] version, Client Functionality
Two Read Audit records created for a drill down on a View.read audit trial captured in source view even though the field not displayed in UI and no Lin specification and force active for the same field
The source and the destination BC here is the same. After the Drill down event, it is inserting two read audit records.
Single record need to create in audit trail BC
The issue can be reproduced at will with the following steps:
1) For the 'Service Request List Applet':
For the Drilldown object named 'Original': Set the Source Field and Destination Field as 'Id'.
2) For the 'Service Request Detail Applet':
Create a new control : 'Provider Id' and map the field 'Provider Id' of the Service Request BC to the same.
Map the new control the web layout of the Applet.
3) Navigate to Administration-->Audit Trail screen in the Application
Create a new record in the Audit Trail with the BC as 'Service Request'
And set the read field as 'Provider Id'. Click the 'Update Audit Cache' button.
Navigate to Service Request View and drill down on SR# from Service Request List Applet.
Navigate to Read Audit Items view to check the read audits created for the record on which the drilldown was performed.
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