The RejectTask_v2 Corba API Call Sends Interchanged Values for Document Number and Task ID to the Custom Extension Code via the NameValuePair
Last updated on JULY 10, 2014
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
MetaSolv Solution Software (MSS) custom extension sends incorrect data in the NameValuePair when the RejectTask_v2 Corba API invokes the custom extension. The NameValuePair interchanged the values for document number and task number; however, this is working appropriately when reject the task through MSS GUI and the custom extension invoked.
Using the RejectTask_v2 CORBA API populate the following fields:
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