Oracle® Communications MetaSolv Solution ASR

3629

Valid Entry “X” has been removed from GBTN field on MSL form.

3630

Replaced AFG field with GOV field on ASR form.

3633

Modified the usage rules for the UREF field on the EVC form.

3634

PNUM field has been newly added on CN (Confirmation Notice) form.

3635

TLE field has been renamed to TLR field on ASR form.

Modified the usage rules for RORD field to replace TLE with TLR field on NOTE2.

3637

Modified usage note validation for DIVPON field on Transport, ACI, SES, EUSA, PIP, and DIS forms.

3638

Modified usage note validation for DIVCKT field on ACI form.

30461919

Issue

The lengths of the lata field in the asr schema and ckr1 in the cn schema of the WebService xsd files differs from the GUI lengths.

Resolution

Code has been modified and now the LATA and CKR1 length has been modified to 5(from4) and 40(from 53) respectively.

30461885

Issue

When importing CR through the importCR WebService API, the application allows up to 225 characters to be entered for the Remarks fields, but editing the field in GUI reduces the length to 124 characters.

Resolution

Code has been modified and now the application will no longer reduce the remarks length to 124 characters.

30405298

Issue

When importing an Access Service Request order via WS API, the API returns the error “The value 'x' of element 'y' is not valid” for the below list of fields:

• SALI form icol when length = 8
• Trunking form apc when length = 9
• Trunking form tsc2 when length = 8
• Trunking form tsc3 when length = 8
• Trunking form tsc4 when length = 8
• Trunking form pcu when length = 8
• Trunking form ssn when length = 3
• Trunking form ttn when length = 3
• Trunking form pcna when length = 3
• CR form remarks when length is between 124 and 225
• CN form dtn when length = 10
• CN form vci when length = 5
• TQ from lrng when length = 10
• TQ form lrn when length = 10

Resolution

The code has been modified and the Access Service Request API will now import the order successfully for the above listed scenarios.

30359967

Issue

When importing a disconnect SES Access Service Request order via API, if the <sbdw> field is not populated within the <asr:aSESSeq> structure, the API responds with a java.lang.NullPointerException.

Resolution

The code has been modified and the disconnect SES Access Service Request API will now import the order even if the <sbdw/> tag is not provided in the <asr:aSESSeq> structure.

30359955

Issue

When importing a disconnect Trunking Access Service Request order via API, if the <qaci> field is not populated with 0 within the <asr:aTrunking> structure, the API responds with a java.lang.NullPointerException.

Resolution

The code has been modified and the disconnect Trunking Access Service Request API will now import the order even if the <qaci> field is not provided in the <asr:aTrunking> structure.

30359920

Issue

When importing an EVC Access Service Request order via API, if the <aEVCUNIMappingDetailSeq> structure does not have the <svlan> and <svact> fields, the application logs the below error in the <servername>.mss.log file, but the order gets created successfully.

<Sep 26, 2019, 10:16:59,138 AM PDT><Notice> <StdErr> <BEA-000000><java.lang.NullPointerException>

Resolution

The code has been modified and now when importing an EVC Access Service Request order via API, no errors would be logged even if the <aEVCUNIMappingDetailSeq> structure does not have the <svlan> and <svact> fields.

30312764

Issue

When importing a Trunking ASR order using the ImportTRUNKING Web Service API with PCNA value having 3 characters, the application gives the error "cvc-type.3.1.3: The value'XXX' of element 'pcna' is not valid."

Resolution

Code has been modified and now the application will allow the import of an order with 3 character PCNA values.

30301369

Issue

When importing an Access Service Request order via API, the API returns the following error when the LONG field on the SALI form contains a valid value as follows: -nn.nnnnnnn

FORM : SALI | Reference Number: 0001 Valid entries for LONG field is -NN.NNN to -NNN.NNNNNN where N must contain a value of 0-9.

Resolution

The code has been modified and now the Access Service Request API will import the order successfully when the LONG field contains all valid values including -nn.nnnnnnn.

30146134

Issue

Users are able to execute the import order API on an ASR order which is already cancelled and change the supp type to a different value. This is contradicting the GUI behaviour where the order becomes read only when the order is marked as cancel.

Resolution

Code has been modified and now the application will not allow an import ASR WS API to be executed on an ASR order that is already cancelled and instead will return the below error:

"Cannot Import Cancelled Order"

29354233

Issue

In an ASR order's remarks field, if the user enters certain ASCII characters, print preview of the ASR gives the following error:

javax.xml.transform.TransformerException:

javax.xml.transform.TransformerException:

com.sun.org.apache.xml.internals.utils.WrappedRuntimeException: Premature end of file.

Resolution

Code has been modified and now when users enter any characters apart from the below white list, the application will filter it and not save it. Hence, print preview of an ASR will no longer give an error.

1. a to z
2. A to Z
3. 0 to 9
4. Special characters`~!@#$%^&*()_-+={}|\][:";'?><,./
5. Carriage returns, tabs, and spaces