Custom Extension Data Different When Task Rejected via the CORAB API rejectTask_v2 Versus the MetaSolv GUI
(Doc ID 1682939.1)
Last updated on MARCH 13, 2019
Applies to:
Oracle Communications MetaSolv Solution - Version 6.2.1 and laterInformation in this document applies to any platform.
***Checked for relevance on 26-Sep-2017***
Symptoms
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.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |