Default Values Are Not Sent From Task Data Node Through Activation Task (Doc ID 2123478.1)

Last updated on APRIL 11, 2016

Applies to:

Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.

Symptoms

OSM 7.2.4.1.9  with O2A version 2.0.1.3.0

Create a Data Element in Task Data of an Automated Task and set default value to it.
When next task was edited the value for that element was empty string. Default value assigned to a Data Element is not sent through Activation Task.

STEPS TO REPLICATE:
1. Create a Data Element in Task Data of an Automated Task and set default value to it.
2. Fire orders and noticed the Request and Response messages in the Automated task.
3. Noticed that the default values are populated properly in Automated task. No issue with Automated task.
4. The issue is that the default values are not sent through Activation Task from Task Data Node default value.
An empty string is found instead of the default value in createOrderbyValueRequest section.
Example: parameter called RETRY_PARAM has a empty value in createOrderbyValueRequest.
The :value/>" section is empty which is wrong, while "type" or "name" section are populated.

Cause

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