Bandwidth Assignment for TDM Circuits Should Allow Users to Override the Included Connection Types to Minimize Search Results

(Doc ID 2040022.1)

Last updated on FEBRUARY 22, 2017

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.

Goal

PROBLEM STATEMENT

Bandwidth assignment for TDM circuits should allow users to override Included Connection Types

When making a Bandwidth assignment to TDM circuits to create a Circuit Emulation, the Connection Hierarchy Search window that pops up has multiple “Included” circuit types checked in,
from the User's Preferences in Inv Mgmt - Conn Hierarchy (Bandwidth, Facility, Special, Trunk), but the user is not allowed to uncheck any of these types at the time of search.
As a result, the search may return too many circuits of incorrect type (i.e. not Bandwidth), which can make it difficult to select the circuit you want.

Window: Connection Hierarchy for Connection Design
   w_channelhier_query

Requested Change:
  a. Change the default behavior to only Include Bandwidth types; and/or
  b. Allow Users to override the default choices and select the desired circuit type (s), in the same way MSS does when assigning a Facility circuit.

STEPS

1. Open a TDM circuit in Connection Design in the CLR/DLR page
2. Click on Bandwidth choice under Actions menu
    » The Connection Hierarchy Search window displays the ' Include ' choices from the User's Preferences in Inv Mgmt - Connection Hierarchy » Query Defaults

       BW (Bandwidth) choice is added to the window if user has not checked it in his/her preferences.

The picture below provides a visual cue to the request:

 

BUSINESS JUSTIFICATION

    • Not being able to uncheck items that should not be there, brings incorrect circuit types, making it difficult to select the proper one.
    • Making changes in the Preferences is not the best choice as Conn Hierarchy is regularly used by the engineers besides provisioning.

COMMENTS

The same behavior can be found in 6.0.15 , 6.0.16 , 6.2.0 & 6.2.1 releases.

 

Solution

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