Cumulative Fixed Issues for MetaSolv Solution LSR 9.x

This document contains the published fixed issues from each service pack's release notes in the LSR 9.x release stream. The tables are listed in ascending order, beginning with the first service pack and continuing to the most recent.

LSR 9.1

Component

Fixed Issue

Description

LSR
Issue  ID: 
207727
Internal CR#:
208025
 
Problem: You are unable to populate the DIRQTY field with a numeric value
Resolution: You can now populate the DIRQTY field with a numeric value.
LSR
Issue  ID: 
232772
Internal CR#:
232940
 
Problem: The master sql file is looking for but not finding the following files:
CR141020.sql
CR138595.sql
Resolution: The entries for the files in the master sql file have been removed because
the contents of the files have been moved into the LSR 9 base data files.
LSR
Issue  ID: 
Internal CR#: 
234051
Problem: The DLQTY should control the number of caption listings that can be entered, 
and the LVL field should save the value entered by a user.
Resolution: These problems have been corrected. The system now allows you to have the number
 of listings reflected in the DLQTY field, and the LVL field works as it should per the OBF.
LSR
Issue  ID: 
Internal CR#: 
233225
Problem: The LNA field does not default.
Resolution: The N value now populates automatically based upon the ACT field on the LSR ADMIN.

LSR 9.2

Component

Fixed Issue

Description

LSR
Issue  ID: 
207661
Internal CR#:
233226
 
Problem: The LNA field no longer defaults in LSR 6.
Resolution: The LNA field will now be auto populated with the value 'N'.
LSR
Issue  ID: 
207727
Internal CR#:
233357
 
Problem: The DIRQTY field is unable to be populated with numeric data.

Resolution: A new pattern was introduced to accept only numeric data for the DIRQTY field.

LSR
Issue  ID: 
232772
Internal CR#:
233453
Problem: Unable to install LSR 9 missing files. The install sql master file is looking for two specific files, but they do not exist.

Resolution: The entries for the two specified files were removed from the sql master file because the contents of these files were moved into the LSR9 base data files.

LSR
Issue  ID: 
231814
Internal CR#:
234483

 

Problem: When coming from the RCONF task, an LSR can be edited and saved without SUPPING the order. This should not be allowed to happen because the user preference 'LSR View Only After Tasks Generated' is set to 'Y'.

Resolution: When coming from the RCONF task, LSR forms will be 'View Only' when the user preference 'LSR Viewonly after Tasks Generated' is set to 'Y'.

LSR
Issue  ID: 
202406
Internal CR#:
235983

 

Problem: Following an LSR location/address change, the user is allowed to update that address for all locations using it. This could cause a problem. Users need a preference so that a new location/address is always created.

Resolution: A preference will be added for LSR to "Always create new location/address." The default will be "N" (no or unchecked; allow update of the address). When set to "Y" (or checked), the user will not be able to choose the "update" option on the confirmation dialog following the location address change on the LSR.

LSR
Issue  ID: 
235950
Internal CR#:
236940

 

Problem: On the Location and Access Detail page, changes to the ACC field do not get saved.

Resolution: The code was fixed such that changes to ACC field on the Location and Access Detail page will now be saved.

LSR
Issue  ID: 
234404
Internal CR#:
238610

 

Problem: PSR Mapping functionality does not work with existing phone lines.

Resolution: PSR to LSR Mapping functionality can now be performed on the existing phone lines. This enhancement covered following scenarios:

1. MAPLSRPORT child item can be added to an existing phone line.

2. MAPLINEDIR child item can be added to an existing phone line.

3. MAPLSRPORT and MAPLINEDIR can be added to an existing phone line.

4. MAPLINEDIR can be added to an existing phone line that has already the MAPLSRPORT as a child.

LSR
Issue  ID: 
208162
Internal CR#:
239691

 

Problem: In LSR 6, Loop Service Detail, CCEA field, when ALPHA characters are re-entered after initial entry the cursor jumps to the end.

Resolution: The code was modified such that the cursor will not move to the end, which allows the user to enter alpha numeric characters at the required position in the CCEA field.

LSR
Issue  ID: 
241005
Internal CR#:
246063

 

Problem: The error message 'Value specified is larger than column width' is being displayed, but the column identification is missing.

Resolution: The field causing the problem is DLQTYR. It's precision is 3 and it is crossing that threshold when importing an LR. The Error message for the column was implemented for DLQTYR field.

 

LSR 9.3

Component

Fixed Issue

Description

LSR
Issue  ID: 
249153
Problem: On an LSR Order under Location Service Request>Location and Access 
Detail, when the user deletes the values in the LD1, LD2, LV1 and LV2 fields, the form 
does not get saved and continues to display the previous values.
Resolution: The code was modified and now when the user deletes the values in the 
LD1, LD2, LV1 and LV2 fields, the form will get saved.

LSR

Issue  ID:
250579
Internal CR#:
207401
 

Problem: When the user validates a PSR Order having a PSR/LSR Task, and double
clicks the PSR/LSR Task on the Work Queue Manager to map the PSR order to an LSR order, the Next button on the PSR to LSR Mapping window is missing.

Resolution: The code was modified and now when the user double clicks on the PSR/LSR
Task on the Work Queue Manager, the Next button on the PSR to LSR Mapping window
will be available.

LSR
Issue  ID: 
249120
Internal CR#:
242945

Problem: When the user imports an LSR Order, the PORTED NBR field on the LSNP Service Detail window is still enabled.

Resolution: The code was modified and now when the user imports an LSR Order, the
PORTED NBR field will be disabled.

LSR

Issue  ID:
252229
Internal CR#:
249473

 

Problem: The user validates a PSR Order having a PSR/LSR Task and maps the order to an
LSR Order. When viewing the details on the Location and Access Detail form, the LCON field is blank.

Resolution: The code was modified and now when the user views the details on the Location
and Access Detail form, the LCON field will display the correct value.

LSR

Issue  ID:
252671

 

Problem: In Local Service Request>Administrative Section, when the user clicks the double
arrows near the NNSP and ONSP fields, the expanded alpha numeric description of the OCN
does not get displayed
in the fields.

Resolution: The code was modified and now the expanded alpha numeric description of
the OCN will get displayed in the NNSP and ONSP fields, when the user clicks the double arrows near the fields.

LSR

Issue  ID:
259344
Internal CR#:
258813

 

Problem: On an LSR Order under End User>Location and Access Detail, when the user
modifies the values in all fields except NAME, STATE, CITY, SASN and ZIP CODE, the new
values are not saved, instead the fields are blank.

Resolution: The code was modified and now when the user modifies the values in all
fields except NAME, STATE, CITY, SASN and ZIP CODE, the new values get saved on the
Location and Access Detail form.

LSR

Issue  ID:
253958
Internal CR#:
251681

 

Problem: The user validates a PSR Order having a PSR/LSR Task, maps the order to an LSR Order, and arranges the telephone numbers in a particular LNUM sequence on the
PSR to LSR Mapping window. However, this LNUM sequence is not displayed
on the Port Service Detail List window.

Resolution: The code was modified and now the correct LNUM sequence will be displayed on the Port Service Detail List window.

LSR

Issue  ID:
253482
Internal CR#:
249063

 

Problem: On the Location and Access Detail window of a child order, when the user
modifies the value in the NAME field and saves, the change is not reflected
on the parent order.

Resolution: The code was modified and now when the user modifies the value in the
NAME field and saves the child order, the change gets updated on the parent order.

LSR

Issue  ID: 
257580
Internal CR#:
256762

 

Problem: On an LSR Order under the Hunt Group Form, when the user enters values in any field, the following error occurs in the Appserver logs:"StringIndexOutOfBoundsException from MSS.log".

Resolution: The code was modified and now values can be entered in any field on the
Hunt Group Form without an error.

LSR

Issue  ID: 
261503
Internal CR#:
259763

Problem: On an LSR Order under End User>Inside Wire, when the user enters a value
on a blank IWBAN field, the following error occurs: "Please enter at least one non-whitespace character to limit results".

Resolution: The code was modified and now the user can enter a value on a blank
IWBAN field without an error.

LSR

Issue  ID:
253452
Internal CR#:
251795

Problem: For any section on an LSR Order, on the Remarks pop up window, when the user
enters a character string value that includes "ex" and saves, an exclamation mark ("!") is
displayed on the Remarks window.

Resolution: The code was modified and now a character string value that includes "ex" will
be correctly displayed on the Remarks window.

LSR

Issue  ID: 
251427
Internal CR#:
251316

Problem: In the Local Response section of an LSR Supplement Order, the Details List link is
not available even after version upgrade.

Resolution: The code was modified and now the Details List link under the Local
Response section will be available.

LSR

Issue  ID: 
255958

Problem: On an LSR Order under End User>Location And Access Detail, when the user
deletes or modifies the values in both the SATH drop down and ACC field and saves,
the changes do not get updated.

Resolution: The code was modified and now when the user deletes or modifies
the values in both the SATH drop down and ACC field and saves, the changes get updated.

LSR

Issue ID:
256119

Problem: When the user validates a PSR Order having a PSR/LSR Task and maps the order
to an LSR Order, the Express Entry link is not available on the PSR to LSR Mapping window.

Resolution: The code was modified and now when the user maps the PSR Order to the LSR
Order, the Express Entry link will be available on the PSR to LSR Mapping window.


Copyright 2007 MetaSolv Software, Inc. All rights reserved. MetaSolv Software, the MetaSolv logo, Telecom Business Solution, TBS, MetaSolv Solution, Framework for Success, MetaSolv QuickStart, MetaSolv eService, MetaSolv Field Operations Portal, and Rapid Results are trademarks of MetaSolv Software, Inc. MetaSolv is a trademark registered in the United States of America by MetaSolv Software, Inc.