ISR Should Support End User Locations For Circuit Identification for A And Z Locations

Last updated on DECEMBER 16, 2017

Applies to:

Symptoms

REQUIREMENT

ISR should support End User Locations for Circuit Identification A and Z locations

When we enter an ISR, we are unable to select an End User location for a virtual connection.
The management of Virtual Connections go from an End User to a PE Router, so we need this capability.

The spyglass is available under Location A and Location Z, but clicking on it does not do anything.

We are able to use the spyglass when filling out the A and Z locations using End User Locations for ASRs and EWOs.

EXPECTED BEHAVIOR

User should be able to enter VC requests using End User Location

STEPS

The issue can be reproduced with the following steps:

1. Create an ISR for Broadband request with at least one Virtual Circuit
2. In Virtual Connections tab: enter qualifying information for the Virtual Connection
3. Go to the Virtual Circuits tab and add a new VC

4. Add a Circuit Format and choose a proper Sve Type Category and Code: CLS - CLCI-SS Intralata - HC
5. Choose a Connection Type if needed
6a. Click the Spyglass for either A or Z location

          »» nothing happens

6b. MSS issues a Warning if the Connection Type is needed and not provided.

         No Connection Types Found and the spyglass for both A and Z location freeze
         A Service Application must be set up and associated to a Service Type Category,
         Service Type Code and Connection Type for values to appear here.
         Service Applications are set up through the Inventory Management Setup.

7. Click the Spyglass for either A or Z location

         »» nothing happens

BUSINESS JUSTIFICATION

Users need the ability to assign End User Locations to Virtual Circuits per internal process.
We are able to use the spyglass when filling out the A and Z locations using End User Locations for ASRs and EWOs.

Changes

Cause