Issue

In the Equipment Maintenance window’s Port Address tab, when users modify the override option twice, one of the equipment port gets deleted.

Resolution

Code has been modified and now when the override option is modified twice, the application will not delete any port.

Issue

In the Equipment Inventory window, when users Install an equipment using Equipment Specs View with a spec having additional rate codes, the application incorrectly adds the additional rate codes as actual ports to the installed equipment instead of displaying them as additional rate codes for the same port.

Resolution

Code has been modified and now when the Equipment Specs View is used to install an equipment, the application correctly installs the equipment with only the primary rate code for the actual ports.

In the Equipment spec view, the primary rate code displays within parenthesis first, followed by a space, and then followed by the additional rate codes in brackets separated by slash (/).

E.g. (DS3) [DS0/STS1].

Issue

In the Product Service Request window, when a user Supplement Cancels an order, clicks OK in Task Generation window and changes focus to another application using Alt+Tab before the progress window pops up, the application closes with the below error message:

Error Number 2.

Error text = Null object reference.

Window/Menu/Object = w_progress.

Error Object/Control = w_progress.

Script = open.

Line in Script = 37.

The supplement cancel process is not processed completely.

Resolution

Code has been modified and now the application will cancel the PSR order even if the user moves away to another application after clicking on OK in the Task Generation window.

Issue

When attempting to make an equipment assignment on some circuits, the Equipment Assignment window displays the Z location on the left and the A location on the right.

Resolution

Code has been modified and now the A and Z location will be displayed in the appropriate positions in the equipment assignment window.

Issue

In the Connection Design window, when changing the network location in the equipment inventory window to a location with the building location CLLI that is same as the circuit's A or Z 11 byte CLLI, the application maps the assignment to Other location instead of the A or Z location.

Resolution

Code has been modified and now the application maps the assignment to A or Z location as appropriate.

Issue

In an EWO order, when opening a virtual circuit where the service type code of the circuit is not defined in the Service Application window, the application terminates with the below error:

Error Number 39.

Error text = Error accessing external object property nst_cont_type.

Window/Menu/Object = n_cst_cd_dbcommon.

Error Object/Control = n_cst_cd_dbcommon.

Script = of_get_nst_con_type.

Line in Script = 3.

Resolution

Code has been modified and now the virtual circuit will open successfully even if the service type code is not defined in the Service Application window.

Issue

In the Equipment Inventory and Network Area window, users are able to use expired 11 byte network locations.

Resolution

Code has been modified and now users will not be able to add/copy to an equipment, if any equipment in its hierarchy has an expired location. Moving an equipment from a non-expired location to an expired location is not permitted. However, move of an equipment would be permitted if moving within the equipment's hierarchy under an expired location.

Also, users cannot associate expired network location (11 byte) to a Network area.

Issue

In the End user location window, the application accepts latitude and longitude values outside the permissible range of -90 to 90 and -180 to 180 respectively.

For longitude, the values entered outside the permissible range “rolls over” into the next hemisphere. For latitude, this “rolling over” was wrongly done using 180 degrees as a reference.

Resolution

Code has been modified and now the application will give the below error message when a value outside the permissible range of -90 to 90 and -180 to 180 for latitude and longitude respectively.

When entering in decimal format, the below errors are returned for invalid values:

Latitude

Specified argument was out of the range of valid values.

Please enter a value between -90.0 and 90.0.

Longitude

Specified argument was out of the range of valid values.

Please enter a value between -180.0 and 180.0.

When entering in DMS format, the below errors are returned for invalid values:

For latitude degrees

Specified degrees is out of range. Please enter a value between -90 and 90.

For longitude degrees

Specified degrees is out of range. Please enter a value between -180 and 180.

For latitude/longitude minutes

Specified minutes is out of range. Please enter a value between 0 and 60.

For latitude/longitude seconds

Specified seconds is out of range. Please enter a value between 0 and 60.

Issue

The Background Processor creates an overridden design issue on top of Pending design issue when two consecutive reconciliations triggered by editing the same equipment is sent to Background Processor in quick succession.

This prevents the user from performing any changes on the overridden design issue.

Resolution

Code has been modified in reconciliation process. Now the background processor will not create an overridden issue on top of pending issue when two reconciliation processes triggered by changing the same equipment are sent to background processor in quick succession.

Issue

In Network system, auto population of Facility designation field is not working for CLF circuit formats when creating a new group connection.

Resolution

Code has been modified and now Facility designation field will be auto populated for CLF circuit formats when creating a new group connection.

Issue

Executing getDLR Web Service does not bring all the fields.

ISS, OLDECCKT, EQPTYPE, FACDESG, RELAY RACK, FACTYPE, UNIT, CHANNEL fields are missing in the output. The ECIA field gives a boolean output instead of valid values of Y, X or blank.

Resolution

Code has been modified and the getDLR Web Service API brings all the missing fields and also shows the proper valid values for the ECIA field.

Issue

When we navigate to the Connection Hierarchy Search window from Bandwidth link of CLR/DLR Design in the Connection Design of a facility, the virtual check box is disabled and hence users are not able to retrieve virtual circuits.

Resolution

Code has been modified and now the virtual checkbox is enabled allowing users to search and retrieve virtual circuits. So a facility can be assigned on a virtual circuit and can be seen as a Bandwidth block in CLR/DLR Design window.

Issue

In Equipment Maintenance window's port address tab, when users edit the port address using the edit button option, application closes with the below error:

Error Number 2.

Error text = Null object reference at line 16 in itemchanged event of object dw_portaddresses of w_equipment_maint..

Window/Menu/Object = w_equipment_maint.

Error Object/Control = dw_portaddresses.

Script = itemchanged.

Line in Script = 16.

Resolution

Code has been modified and now users would be able to edit the port address using the edit button option.