DD SYSTEM TASK completed in background processor does not fire custom extension code

(Doc ID 1053520.1)

Last updated on JULY 09, 2013

Applies to:

Oracle Communications MetaSolv Solution - Version 6.0.15 to 6.0.16 [Release 6.0.15 to 6.0.16]
Information in this document applies to any platform.
*** Reviewed for currency on July 9th, 2013 ***


Through the GUI, it is possible to send a DD task completion through the Background Processor, and that task completion will execute the Complete Task Custom Extension.

If you put the DD task in the SYSTEM queue and it gets picked up by the Background Processor, the Complete Task Custom Extension is not executed.

Our expectation is that the Complete Task Custom Extension would be executed for all tasks that are completed via the Background Processor.

-- Steps To Reproduce:

1. Create PSR Order
2. Provision with a plan that has a DD task that is put in the SYSTEM queue
3. Make sure the System Task Server and Background Processor are running
4. After DD task completes review the appserverlog.xml file and see that the ProcessPoint / ActionType and BuildingBlock are not logged because the custom extension was not invoked

-- Business Impact:
The custom extension logic execution should be consistent for Complete Task via the GUI and System Task Server, this causes the custom extension logic to not be run for all cases of completing the DD 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