Terminating Location and Element are not Being Auto Populated for EVC.
(Doc ID 2285588.1)
Last updated on MARCH 26, 2019
Applies to:
Oracle Communications MetaSolv Solution Module - ASR - Version 45.0.0 and laterInformation in this document applies to any platform.
Symptoms
MSS 6.0.16 Connection Design
The following issues were reported regarding the Selection Of Terminating Element in the Connection Design screen :
ISSUE 1:
Once the connection spec is selected for a circuit on the Connection design screen, the originating component is automatically selecting based on the originating location. The terminating component ,however ,was not automatically selected, even though there is only one CUST_SITE component matching the terminating location.
Expectation :THE TERMINATING END SHOULD BE AUTOMATICALLY PICKED WHEN THE TERMINATING COMPONENT IS A NETWORK EXTENSION.
ISSUE 2:
Now ,once the terminating network is selected, the user has to click the 'None' hyperlink to manually pick the terminating element.
The window provided for picking the terminating element has a number of problems as described below:
1) No scroll bar on the right side of the window so one can only move down the list using arrow keys.
2) No sort ability on any column so one cannot sort the results. The default sort is based on the NS_COMP_ID value which is not visible to the user. The user should be able to sort by any column to make finding the selection easier
3) No search/filter ability in the window. It is possible that this network could have hundreds or thousands of customer site components. It is unreasonable to have the user manually scroll through a large list to find the row they need.
4) No address details displayed. When an end user location is used as the customer site, only the name is displayed. If there are multiple EULs with the same name but different addresses, it is impossible to differentiate between the locations in this window without address details. The Element Type and Network Name columns are useless in this window and could be removed since all elements will be of the same type (based on connection spec) and in the same network (which was picked one step earlier).
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |