Different Behavior When Handling Compound Parameters In ASAP V5.2 Versus ASAP V7.3 (Doc ID 2128458.1)

Last updated on JULY 25, 2017

Applies to:

Oracle Communications ASAP - Version 7.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

There is a different behavior when handling compound parameters in ASAP v5.2 versus ASAP v7.3

In customer's ASAP v7.3 environment, all work orders generated via OCA Client, which contain 'optional compound parameters' currently fail with below error message

"E X C E P T I O N --> java.lang.NullPointerException."

The execution fails on the handling of compound parameters. Customer sees different behavior in ASAP v5.2 versus ASAP v7.3.

workorderparameters passed in ASAP v5.2:

...
PRODUCTID1 = 1001
PRODUCTID2 = 486
PRODUCTID3 = 56941
PROVISIONINGSYSTEM = TLNNAGRA
...

 

workorderparameters passed in ASAP v7.3:

...
PRODUCTID.1 = 1001
PRODUCTID.2 = 486
PRODUCTID.3 = 56941
PROVISIONINGSYSTEM = TLNNAGRA
...


One can see between the parametername and index a dot ('.') exists. Customer thinks this might cause the issue..

Changes

 

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