BC DeleteRecord Event on Child BC Does Not Fire if User Navigates to Parent BC Applet Without Doing Save Record ( Crtl-S ) or Stepping Off Deleted Record to Next Child BC Record.
(Doc ID 2081389.1)
Last updated on FEBRUARY 08, 2019
Applies to:Siebel CRM - Version 18.104.22.168.17 [IP2013] and later
Information in this document applies to any platform.
On : 22.214.171.124.17 [IP2013] version, Configuration - General
We have existing eScript on the Revenue buscomp that adds numbers in 2 fields on all Line Items and updates 2 fields in the head Opportunity. In High Interactivity, when a Line Item is deleted, the script is successfully invoked once a record is deleted and the user moves to another Line Item or the header Opportunity. In OpenUI, the code is NOT successfully invoked when a Line Item is deleted and the user moves to the Opportunity header. It appears that moving to the Opportunity applet is not triggering any kind of commit or save that then invokes the actual Delete record event.
I will attach the SIF of the Revenue and Opportunity buscomps, a view and 2 applets in the view where the issue occurs. It may be easier if we can have an appshare so I can demonstrate the issue.
Server scripting on the Child BC in a Parent / Child view that works as expected in HI, does NOT work with Open UI.
The issue can be reproduced at will with the following steps:
1. Use out of the box Opportunity / Revenue view.
2. Add server script in the Child Revenue BC's DeleteRecord even to update the ActiveBusObject's Parent BC field.
3. Test the child Revenue BC Delete Record script config in HI client, where the parent BC field is updated in the view..
and compare to the child Revenue BC Delete Record script that fires in the Open UI client, but it does NOT show the new value in the parent BC applet.
If the end user does a Commit / Save Record in the Child BC BEFORE navigating to the parent Opportunity BC.. the parent BC field DOES show the new value and that new VALUE is SAVED.
If the end user does NOT do a Commit / Save Record or a NEXT Record (Something to "step off" that record that was deleted in the child applet,,,Then the Delete Record script fires, but the field change DOES NOT get shown in the top parent applet.
The user can o a F5 to reload the web page and then it is shown..
But if they don't do that, they don't see the change AND if they happen to update the parent, then that update done in the scripting is LOST.
Existing HI view with Server Scripting does not work the same.
Incorrect BusCompDelete_Record behavior only happens with Open UI.
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