My Oracle Support Banner

Multiple Names Under Atomic Action Label Separated By Commas After Upgrade (Doc ID 2364688.1)

Last updated on MARCH 14, 2019

Applies to:

Oracle Communications Design Studio - Version 7.3.5.0.0 and later
Information in this document applies to any platform.

Goal

On : 7.3.5.0.0 version, Activation Services

This is with regards to upgrade project from ASAP 7.0.2 to ASAP 7.3.0.

We imported an ASAP cartridge to DS 7.3.5 B9. On auto-upgrade of the cartridge, a discrepancy noted was multiple atomic action parameter names (in atomic action label) mapped to single parameter, separated by commas. 

For example, when 2 atomic action parameters have the same parameterValueMap value in the original cartridge, the upgraded cartridge will merge the 2 parameters into one, separated by ','.

For example, in original cartridge, SERVICE_TYPE and SDM_SERVICE_TYPE share the same parameterValueMap value:

     <act:parameter>
       <act:simpleParameter name="SERVICE_TYPE">
         <act:description></act:description>
         <act:constraint>Enter relevant data restrictions here.  For example:  min value, max value, valid values, etc</act:constraint>
         <act:required>false</act:required>
         <act:default></act:default>
         <act:parameterValueMap></act:parameterValueMap>
       </act:simpleParameter>
     </act:parameter>
     <act:parameter>

     <act:parameter>
       <act:simpleParameter name="SDM_SERVICE_TYPE">
         <act:description></act:description>
         <act:constraint>Enter relevant data restrictions here.  For example:  min value, max value, valid values, etc</act:constraint>
         <act:required>false</act:required>
         <act:default></act:default>
         <act:parameterValueMap>SERVICE_TYPE</act:parameterValueMap>
       </act:simpleParameter>
     </act:parameter>

Then in the upgraded cartridge, SERVICE_TYPE and SDM_SERVICE_TYPE is merged into single parameter:

<data:dataElementDetails xsi:type="networkActionParameterDetailsType">
   <com:id><ID></com:id>
   <com:elementType>com.mslv.studio.activation.entities.networkaction.ParameterDetailsModelElement</com:elementType>
   <data:dataElementId><ID></data:dataElementId>
   <constraint>Enter relevant data restrictions here.  For example:  min value, max value, valid values, etc</constraint>
   <indexed>false</indexed>
   <indexPosition>Last</indexPosition>
   <serviceLabel></serviceLabel>
   <atomicLabel>SERVICE_TYPE,SDM_SERVICE_TYPE</atomicLabel>
   <runtimeType>SCALAR</runtimeType>
 </data:dataElementDetails>


This issue is with hundreds of ASDLs.

The previous design studio version in which initial solution was built had the provision to map single service action parameter to multiple atomic action parameters. 'original_cart' folder may be referred (uploaded). Basically, how to achieve same in current studio?

We already referred to Doc ID 2218215.1, but this doesn’t seem to cover our above mentioned issue.
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.