Custom Extension Data Different When Task Rejected via the CORAB API rejectTask_v2 Versus the MetaSolv GUI
Last updated on SEPTEMBER 26, 2017
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
***Checked for relevance on 26-Sep-2017***
When the task been rejected through MetaSolv Solution (MSS) GUI level, the custom extension code gets data for rejected task as well as all the tasks which were re-opened because of this rejection process.
However, when the task is rejected through MSS CORBA API rejectTask_v2 the custom extension gets the data only for rejected task and there is no information passed regarding the task's which were re-opened (i.e. values in the NameValuePair differ between MSS GUI reject and API reject).
Same data needs to be passed for both GUI level and API level task rejects through Custom extensions (Entity / NameValuePair).
MSS GUI passing the rejected task id as well all task id's that are re-opened to the custom extension and the rejectTask_v2 API is only sending the task id of the rejected task.
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