Cumulative IR Tables for MetaSolv Solution LSR 6.x

This document contains the published IR tables from each Service Pack ReadMe in the LSR 6.x release stream. The tables are listed in ascending order, beginning with the first service pack and continuing to the most recent.

LSR 6.1

Product Description
IR: CR9255

Product Area:
 LSR

Product:
 LSR

PROBLEM
1. LRADMIN Screen displays the error tab without any error messages when the user clicks the validate button on the LRADMIN Screen.
2. When validating the Order in LR HUNT Group Form for a Port Service Order the order hangs. You have to close the Order and open it again to complete the order.

RESOLUTION
1. The error tab will not display erroneously.
2. The order will not hang when validating an order in LR HUNT Group Form for a Port Service Order.

IR: CR9401

Product Area:
 LSR

Product:
 LSR

PROBLEM
User experiences port validation problems.

RESOLUTION
BSPRAO Field population and validation takes place as desired.

IR: CR9563

Product Area:
 LSR

Product:
 LSR

PROBLEM
Centrex LNUM Renumbering and Debugger message problems.

RESOLUTION
LNUM is renumbered after deletion in Centrex Station Details List 
Form. When validating the Centrex Station Details Form the attached Debugger message is not displayed. And, when selecting the LOCNUM value in Centrex Station Details Form a Run Time Script Error does not occur.

IR: CR9636

Product Area:
 LSR

Product:
 LSR

PROBLEM
The application allowed the user to create received orders for all request types. It should only support received NP orders.

RESOLUTION
The application will now allow the user to create received orders for request type 'C' number portability.

IR: CR9672

Product Area:
 LSR

Product:
 LSR

PROBLEM
The Hunt Service is not populated with HTN and TLI values. Also, LOCNUM is not auto-populated in Centrex Station Details Form.

RESOLUTION
For a Centrex Order, the TLI and HTN field in Hunt Service Detail will be populated with the station details number. LOCNUM will be defaulted.

IR: CR9713

Product Area:
 LSR

Product:
 LSR

PROBLEM
The customer cannot import DSCN with Remarks field.

RESOLUTION
DSCN Remarks field value gets imported successfully.

IR: CR10531

Product Area:
 LSR

Product:
 LSR

PROBLEM
Oracle error when trying to assign PP for LSR

RESOLUTION
The LSR Tasks link will be disabled if there are validation errors and will only be enabled when the order is validated and there are no errors.

IR: CR1055

Product Area:
 LSR

Product:
 LSR

PROBLEM
When clicking on the Loop or Port Service Detail link from the Hunt Service Detail Form in a Combined LSPS Order ( ACT-M) a script error.

RESOLUTION
No script error would be thrown while navigating from Hunt Service Detail section to Loop and Port Service Detail section.

IR: CR11061

Product Area:
 LSR

Product:
 LSR

PROBLEM
TNS field value not displayed in PS Detail form of the Child Order

RESOLUTION
TNS field gets populated while mapping a PSR to a LSOG6 LSPS Order.

IR: CR13497

Product Area:
 LSR

Product:
 LSR

PROBLEM
Running the prodfix sql for LSR6 gives ORA errors.

RESOLUTION
SQL files modified to fix the ORA errors.

LSR 6.2

Product Description
IR: Internal CR# 9668

Product: LSR
 

PROBLEM
1. Valid Entries for the LVL field should be 0 - 7 as per the OBF .
2. Validation rules for the following fields need to be implemented.
a) PLTN
Optional when the LVL field is different than the DOI field and the PLS field is 'E', otherwise prohibited.
b) SO
Prohibited when the LVL field is '0', otherwise optional.

RESOLUTION
1. Valid entries for the LVL field have been changed to 0 - 7.
2. The validation rules for the PLTN and SO fields have been implemented as described above.

IR: Internal CR# 10246

Product: LSR
 

PROBLEM
Need to implement Filtering Ineligible characters in Express Entry.

RESOLUTION
Express Entry will now validate for the ineligible character(s) and give the validation error as "<field name> contains one or more of the following ineligible character(s) : <list of ineligibe characters>."

Note:Please do not use double quote("), as a filtering character. TBS utility warns when using this as an ineligible character but gets associated.

IR: Internal CR# 13594

Product: LSR
 

PROBLEM
Express entry is currently not working for LSR 5. If you create a new PSR order and map a LSR order and then click on the Express Entry link you receive an error stating the URL can not be found. 

RESOLUTION
Express entry will now work for LSOG5. Users must ensure they associate the SC with the valid values on the forms contained on the Express Entry SF.

IR: Internal CR# 13620

Product: LSR
 

PROBLEM
The Reqtyp field disappears when a DL order is reopened.

RESOLUTION
The Reqtyp field will appear when a DL order is reopened.

IR: Internal CR# 13919

Product: LSR
 

PROBLEM
Some of the LSOG fields that were present in LSOG 4 & 5 are not supported by MLSR6 Express Entry.

RESOLUTION
Users can now map LSR from PSR using LSOG 4 & 5 templates in MLSR6.

IR: Internal CR# 14018

Product: LSR
 

PROBLEM
PON hyperlink for mapped LSOG4 and LSOG5 orders on the summary page should be disabled.

RESOLUTION
PON hyperlink on the mapping summary page for LSOG4 and LSOG5 child orders will be disabled. The PON hyperlink will be available for LSOG 6.

IR: Internal CR# 14486

Product: LSR
 

PROBLEM
1. In Centrex Resale LSR -> End User Bill, the following message occurs "BILLCON is required when the FBI field is populated", but there is no entry in the FBI field. This occurs only when a new record is populated in the Location & Access detail form and the functionality works correctly when an existing service address is selected in the Name field.
2. When a location service address record is deleted from the list, the Location & Access Details entries are deleted, except the field entries in End User form are retained.

RESOLUTION
1. "BILLCON is required when the FBI field is populated", validation error message will function as desired.
2. When a location service address record is deleted from the list, the Location & Access Details entries as well as the associated information would also be deleted. EU Bill information would not be retained.

LSR 6.3

Component Issue ID Problem Resolution
LSR 43499 The field length for the LNUM field in the Service Detail section of LS, LSNP, PS, RS, CRS, LS/PS, DL need to be lengthened to 5 bytes on the windows. The OBF field is 5 characters in length, the database shows the REFERENCE_ NUMBER on the LSR_SRSI table to be VARCHAR2 (5). The windows need to accommodate the correct field length. The LNUM field width is increased to accommodate 5 characters in LS,LSNP,PS,RS,LS/PS service forms
LSR 69009 Add a Refresh button to the Ticket Maintenance window in Trouble.

If the user clicks the Refresh button and changes are pending, prompt the user to see if they want to save their changes.
The code that validates the ACT type for Importing and for Express Entry is modified for accepting the user defined ACT types 'P' and 'Q'.
LSR 69113 The LOCNUM field does not populate. The LOCNUM field will be populated correctly.
LSR 69162 TIME_TYPE_FIELDs display the default 1970*01*01 as the value in Express Entry. All the TIME_TYPE fields will now give the times (for example, 1010AM) in Express Entry.
LSR 69163 The user was able to type small case letters in PON input box, but could not query for the small case letters in the Search Window. Changed the property of PON input box in to accept only uppercase letters.
LSR 69534 Customer cannot create a new child LSR. Customers can now create child LSRs from SR Hierarchy window and see the relationship with the parent PSR.
LSR 69793 When creating an LSOG 6 DSR order, the REQTYPs G and J are not available. Customer can now create LSOG 6 DL orders with REQTYPs G, H and J.
The REQTYPs can be accessed via the pop-up window for a Standalone DSR but the recommended method would be to select New LSR and select "G", "H" or "J" from the REQTYP dropdown on the LSR Admin window.
Since the DSR Form was deleted with LSOG 6 the Directory Listing(s) are treated the same as a service specific form and can be selected just like any other service (for example, REQTYP C, F, E etc.)
LSR 70041 Cannot update supplemented orders after the "Sent" box is selected. Steps: 1.Created an LSR order 2.Entered a value in all required fields. 3.Saved and validated order. 4.Reopened order and selected the "Sent" box. 5.Hit the icon and then I closed the order. 6.Supp the same order and all the fields are grayed out. Supplemented orders can be updated after the "Sent" box is selected.
LSR 70043 When you execute a gateway event, you receive an error, "CKR field value 920-884-8594 conflicts with order value 920-884-8594 for PON 1071830 LOCNUM 1, LNUM 0001". This gateway event is invoking the importLR5 API method. The value on the order is trimmed for trailing spaces before comparing it with the imported value in the parameter file
LSR 70046/70080 Users cannot inactivate values in the ACT field for LSOG 6.
Made all the Static Dropdowns on the LSR to SQL dropdowns. All the SQL SELECT will retrieve only the Active valid values for the components on the LSOG.LSOG_VALUES structure format. All the CHECKBOX components will remain as is.
TC OPT fields on End User, Loop Service, Number Portability, Loop Service with Number Portability Resale Port Service forms will remain as a text box to accept three alphanumeric characters.
LSR 70049 Export of LSOG 5 (and below) order fails when the LSR6_jbroker_stubs.jar is placed infront of the LSR_jbroker_stubs.jar in the AGCLASSPATH. The LSR6 project was changed to remove an IDL file that was only intended for LSR5. That IDL file was causing java classes to get constructed with the incorrect path "Metasolv.Corba.WDILSR" and those were being included in the lsr6_jbroker_stubs.jar.
LSR 70057 On LSOG 6 port orders, the TNS range is not exported. Only the beginning number of the range is exported. Both start and end range values for the TNS field gets exported.
LSR 70096 We found that in the LSOG6 request, the UDFs are being exported only for the LSR form. For other forms, like EU, LS, NP, the UDFs are not being exported.
Also the UDFs added in the EU Bill section are added in EU Inside Wire section. While UDFs added in EU Inside Wire section are shown in EU Bill section.
The user defined values for LSR, EU, LS, NP, LSNP, PS, RS, CRS and DL forms will be exported.
LSR Internal CR22205 The IWJQ and IWJK fields in the LSR service details form should have the following number of occurrences:
Loop, LSPS, LSNP - 3
Port, Resale, ISDN, Centrex - 1

But the application shows 4 occurrences and the validation is also for all 4 occurrences.
Number of occurrences of IWJK and IWJQ are corrected to follow OBF.  LS, LSPS, LSNP will have 3 occurrences RS, CRS will have 1 occurrence
LSR Internal CR26677 EUMI is displaying as a checkbox and not a dropdown on the End User Location and Access detail window. EUMI is now changed to a dropdown showing the valid values. New validation rules are called from both LSNP and NP forms(NPT)
LSR Internal CR26688 User receives an Advertising Error on a Residential Listing. EA field is validated against TOA if TOA is "B" then EA is populated, otherwise Optional.
LSR Internal CR26710 In LSOG version 6 REQTYPs G and J for Directory listings do not validate and do not allow the user to generate tasks. Customer can now validate and generate tasks for REQTYP G or J. Tasks hyperlink will be enabled after validation is completed successfully for REQTYP G or J.
LSR Internal CR26727 Receiving an error for the CHAN PAIR field that states this optional field is required when the customer has assignment control in a collocation arrangement, otherwise optional. The usage for the CHAN PAIR is optional. The error message belongs to the UNIT field that should not be edited because you do not know when the customer has assignment control unless they populate the fields that carry those notes. Validation is Removed for UNIT field.
Whenever there is an OBF validation indicating that "the field is required when customer has assignment control..." there should not be  this validation because our application has no way of knowing whether this agreement exists or not.
LSR Internal CR27271 When we could add values to PIC, LPIC and IPIC fields (which provide Values in the drop down list) using the Structured Formats * Best Practices guidelines, we could not see these values in the application. PIC/LPIC/IPICs are generated from Infrastrucutre and not Structured Formats. This data is provided via Access Customer information in Infrastructure. All three indicators display all pre-subscription Indicators created in Access Customer.
LSR Internal CR29251 The JK POS and IWJQ on the LS service detail screen are zero filled.

On the print preview, the D/TSENT field is not displaying correctly and several fields are being populated with "Ns". Please Note the Ns are being transmitted via the LSR API.
Quantity fields will not show up zeros in the application by default. Checkbox fields will not show 'N's in the export and in the print form.
D/TSENT field will be correctly formatted in the print form.
LSR Internal CR 29252 When creating a standalone Number Portablity LSR ( REQTYPE = C), the NP form validation requires the LRN field to be filled out. This is no longer a valid rule. The field is an optional field and the validation rule should be removed. LRN field validation is removed for REQTYP=C and it is optional.
LSR Internal CR 29439 Unable to export REQTYP G or J across the LSR API. Now ReqType G & J orders are exported for Directory Listing.
LSR Internal CR29511 Receiving a validation error for the Hunting Form at the Service Detail level. Edit is being generated too early. Validation error will not be thrown when validating the service details. Validation error will be thrown only when HuntGroup occurs and it does not match HTQTY
LSR Internal CR29573 The AUTHNM and ACTL fields don't save when you supplement as LSR6 with a supplement type of 3 - Other. All fields on the Administrative section will get saved on supplementing with a supplement type of 3-other.
LSR Internal CR29579 Unable to import an NP request, receiving validation errors when they do not apply. Validation error will not be thrown, if TNP field is not populated. Now LSR 6.3 to import successfully only if the AN or ATN is populated or if both AN and ATN are populated.
LSR Internal CR29581 The 1st position of the LTOS fields on the Port Service has incorrect values in the dropdown, LNA needs to be sorted. LTOS first position is changed as per the OBF guidelines.
LSR Internal CR29827 The TNS field is on the PS, RS, CRS and LR Forms - Allow the user to enter Alphas if needed in this field. The TNS field is on the RS and LR Forms will Allow the user to enter Alphabets.
LSR Internal CR29855 Unable to enter "N" in the SMDRAC field. SMDRAC field can now accept an 'N'.
LSR Internal CR29901 PORTTYP field is defaulted when REQTYP is "F" or "M", and this is correct. However, this field is not permitted when the 2nd position of the TOS or LTOS field is "M" or "N".

If the 2nd position of the TOS or LTOS field is "M" or "N" the field is not required. Either the system removes the defaulted value and leaves the field blank or enable the field and allow the user to remove the defaulted value of L = Line port.
The system removes the defaulted value and leaves the PORTTYP field blank and validation against the TOS or LTOS field has been removed.

LSR 6.4

Component Issue ID Problem Resolution
LSR 43499 The field length for the LNUM field in the Service Detail section of the supported services LS, LSNP, PS, RS, CRS, LS/PS, DL needs to be lengthened to 5 bytes. The OBF field is 5 characters in length, the database shows the REFERENCE_NUMBER on the LSR_SRSI table to be VARCHAR2 (5). The GUI needs to accommodate the correct field length. The LNUM field width was increased to accommodate five characters on the LS, LSNP, PS, RS, LS/PS service forms.
LSR 69162 Remarks field for Admin, EU, LS, NP, LSNP, and PS was not saved through Express Entry. Remarks field for Admin,EU,LS,NP,LSNP and PS will save through Express Entry.
LSR 70041 You cannot update supplemented orders after the "Sent" box is selected. Supplemented orders can be updated after the "Sent" box is selected.
LSR 70057 On LSOG 6 DL orders, the Remarks field is not getting exported. Directory Listing Remarks field will be exported on LSOG 6 orders.
LSR 70423 The RT and RTR field valid values are hard coded and need to be changed to allow the user to add new valid values.

The API edits need to be relaxed to allow the new valid values to be passed across the interface and into MSS.

No validation for new values added in SF and received across APIs.
The user can now enter user-defined values in the RT field as well all other fields listed in the LSOG.LSOG_VALUES structured format. Duplicate valid values can be entered as long as they have a unique value name and do not exist on an ADDRESS structured format. The validation for the RT field has been removed so that a Local Response can be imported with a user-defined value in the RT field.
LSR 70584 LPIC is not appearing in the Express Entry window. LPIC will be available for editing in Express Entry window as a dropdown field with valid pic codes.
LSR 71142 LNUM is starting with 0000(x), but not everywhere within LSR. LNUM will be 0000(x) for the LSRs mapped from PSR.
LSR 71380 ECKKT is not updating to the LR Details List. The ECCKT field will be imported to the LRServiceDetail.
LSR 71546 You cannot change the SC field on an LSOG 6 form. The SC field in the LSR Admin page is kept enabled for editing. The SC field in the LSR Admin page will always be populated with the LSOG 6 Service Centers.
LSR 71595 The City, State, and Zip fields disappear on the Location and Access window when you change the address information by selecting a different name from the NAME dropdown.

APP Time and DFDT are not saved on the Admin form of LSR when you go to another form and click back to Admin. This is for both express entry and manual entry when using PSR to LSR mappin

The City, State, and Zip fields will not disappear on the Location and Access window when you change the address information by selecting a different name from the NAME dropdown.

DATETIME fields will be saved while navigating to some other 

LSR 71689 Execute importLR and you receive the following error message "Code: 29001 Message: SQL Exception thrown. Error ORA-02291: integrity constraint (ASAP.REF_372) violated - parent key not found Severity: 4 From Class:com.mslv.core.api. internal.LSR6.entity.helper. LrAdminEntityHelper Debug Code: 2" All issues with importing Local Response (LR) have now been resolved and no errors will occur when the user imports a LR with a new billing account number (BAN), a different BAN or no BAN at all.
LSR 71711 The TDT field on the Number Portability and the NRI field on the Billing page, incorrectly defaults to "N" on printed forms. TDT field on the Number Portability and NRI field on the Billing page will not display "N" on printed forms.
LSR 71757 Users are unable to change the Name Field on the End User form when using the PSR/LSR mapping or using the lookup function. Users can now change the EUNAME field on the End User form in MLSR6 Thin client.
LSR 71950 DFDT and APPTIME fields will not stay populated when a supplement is applied to an order. DATETIME type fields will get saved when a supplement is applied to an order.
LSR 71906 Create a PSR order and use PSR/LSR mapping to create the LSR order. Provision and work the order. Receive the importLR, open the DLRD task and click on Circuit Xref and the ecckt /ckr data xref data form the importLR does not appear in the dialog box. You must manually enter. When importing LR circuit_xref is populated with the ECCKT value.

LSR 6.5

Component

Issue ID

Problem

Resolution

LSR

71689

When you execute importLR you receive the following error message "Code: 29001 Message: SQL Exception thrown. Error ORA-02291: integrity constraint (ASAP.REF_372) violated - parent key not found Severity: 4 From Class:com.mslv.core.api. internal. LSR6. entity. helper. LrAdminEntityHelper Debug Code: 2"

All issues with importing Local Response (LR) have now been resolved and no errors will occur when you import an LR with a new billing account number (BAN), a different BAN, or no BAN at all.

LSR

71719

Unable to view Feature Details in LSOG 6 Loop and Port order.

Feature Details will be displayed for Loop and Port Service.

LSR

71757

You cannot change the Name field on the End User form when using the PSR/LSR mapping or using the lookup function.

You can now change the EUNAME field on the End User form in MLSR6 Thin client.

LSR

71906

Create a PSR order and use PSR/LSR mapping to create the LSR order. Provision and work the order. Receive the importLR, open the DLRD task, and click on Circuit Xref. The ECCKT /CKR data reef data form the importLR does not appear in the dialog box. You must manually enter this information.

When importing LR, the circuit reef will be populated with the ECCKT value.

LSR

71949

The ported number is deleted from LSR when you make a change to the LR Service Details form, and you cannot reenter it.

Changing something on the LR Service Details form will not delete the ported number. The ported number will no longer be removed from the response form when other data elements are added to LR Form.

LSR

71950

DFDT and APPTIME fields will not stay populated when a supplement is applied to an order.

DATETIME type fields are saved correctly when a supplement is applied to an order.

LSR

72133

You have to bounce the application server if you change any of the LSR guideline rules.

There is no need to bounce the application server when changing any of the LSR guideline rules.

LSR

72137

When you select a line to delete in the Service Details section, and delete a line, all lines disappear from the order.

The user now can delete Lines/LNUMs from the Service Detail List window without all lines being deleted from the request.  NOTE: Lines/LNUMs can be deleted from the request and they will be renumbered as long as the request hasnít been sent to the provider.  Once the request has been sent to the provider the Lines/LNUMs must remain the same as when sent for the life of the order.

LSR

72199

You cannot select specific pages to print of the LSR.

There are two ways you can preview/print a service request. One way is to preview/print the service request from within the order while it is open. If the service request is preview/printed this way, then you will get a response window before the service request is preview/printed, which asks you which part of the order do you want to print and whether or not you want to include additional data as well. You can choose to print the Order forms (LSR, EU, Service detail forms) or the Response forms (LR, LSRCM) and choose whether to include additional data for the part of the order you are preview/printing. 

Another way the service request can be printed is from the Service Request Query window on the Results tab by clicking the Preview button or selecting Preview from the right click menu. If either of these actions are performed, the preview/printing acts a little differently than in the first scenario in that you will not be prompted with a response window to choose what part of the order to print, but instead the Order forms (LSR, EU, Service detail forms) will be printed automatically with any additional data included in the preview/print. The only way you can control what you want to preview/print is by performing the preview/print from within an open order.

LSR

72248

The validation error message on the Centrex Common Block page doesn't make sense.

Validation error messages are corrected to display the correct values.

LSR

72297

When multiple End User Disconnect sections are entered, the data from the first one seems to be repeated in all the other DNUMs.

End User Disconnect Details will be exported correctly, when it contains multiple Disconnect Details.

LSR

72397

There are 3 field entries for IWJK and IWJQ fields on Loop Service Detail page in LSR. This was recently changed - previously IWJK and IWJQ had 4 fields each. Change was made on the GUI, however the validation still expects 4 entries

The user will no longer be required to enter data in all appearances of the IWJQ and IWJK code fields.   When Multiple lines are terminating in one multiline jack, the IWJK and IWJQ fields should only be populated for the first line.  Jacks may be ordered on a line-by-line basis. 

LSR

72443

The LCON is not passing over from Express Entry.

LCON will pass the values from Express Entry to full mode LSR.

LSR

72565

Changes to an LSR are affecting the parent PSR.

When the end user location is changed on a mapped LSR, the service location on the parent PSR will not change.

LSR

72581

The application is pre-populating the EU Bill: City, State and Zip Code.

Mapped LSR orders will not get defaulted with EU Bill City, State and Zip Code.

LSR

72625

When the LSLoopConInfo fields are populated in the GUI, the fields are not exporting through the LSR6 ExportLSR method.

When the user populates data in the LSLoopConInfo section of the LS Form, the data will be displayed on both the print form and in the export file. For Example: If the CABLE ID and CHAN/PAIR are selected and data is entered in those fields all data entered will be displayed on the GUI, Print Form and Export File.

 

LSR

72771

EU Bill city is being exported even though it has been deleted from the LSR.

When EU Bill city is exported, if it is deleted from the LSR, it will not be exported.

LSR 72792 Additional data is not specific to each LNUM in LSOG 6 orders. The additional data values will be specific to the individual LNUM.

LSR

Internal CR# 33566

Delimiters are not available in the LSR6 Print form to separate the Field Values.

Delimiters will be printed in the LSR6 Print form to separate the Field Values.

LSR

Internal CR# 33953

User could not get the ACNA address if he changes from the default.

ACNA address can now be changed to different one from the default.
SR_PARTY_ROLE_ADDRESS table updated correctly with the PARTY_ROLE_SEQ and PARTY_ROLE_ADDRESS_SEQ when the address is changed.

It will not throw constraint error when ACNA preference is set to 'none'.

LSR

Internal CR# 34465

Before the Location and Access page is rendered we need to make sure that the party_id is not used on a different order. A variable should be passed into the opening of the page denoting whether or not a row was returned when this sql was run so that if the user does type over the name we will already have the info we need in this variable to determine if we need to open the "end user changed" window that asks the user if they want to update this End User or create a new End User.

The Address Change window will display only if the End User Location is being used elsewhere in the application.

LSR

Internal CR# 35466

Users would like the ability to enter directory information once on the PSR and have that information mapped over to a DSR.

You can map Directory Listings from the PSR to the LSR using both DIRREQ item type at the Global level and the LINEDIR mappable item at the Service Location Line level for LSOG 5 and 6 orders.

LSR

Internal CR# 37636

Feature Details displayed on Port Service Details window of Loop and Port are not the correct length. It is only 25 characters in length and it should be 200 alphanumeric characters in length.

Feature Details are displayed on the Service Details window of Loop and Port, Port Service and Resale Service windows and will accept up to 200 characters.

LSR 6.6

Component

Issue ID

Problem

Resolution

LSR 72397 There are 3 field entries for IWJK and IWJQ fields on Loop Service Detail page in LSR. This was recently changed - previously IWJK and IWJQ had 4 fields each. Change was made on the GUI, however the validation still expects 4 entries. The window has been updated to correctly reflect three appearances of the IWJK and IWJQ fields. The user will no longer be required to populate all three occurrences of the IWJK and IWJQ fields when the JR field is populated.
LSR 72721 The NNSP field is not populating with the correct data. NNSP will be populated correctly from Infrastructure based on what is entered in the NPAC SPID field of the CC.
LSR 72771 The EU bill city is being exported even though it has been deleted from the LSR. The EU bill city won't be exported when it is deleted from the LSR. Also, if the validation for these fields are turned off they are not populated on the mapped LSR.
LSR 72792 Add data is not specific to each LNUM in LSOG 6 orders. The additional data values will be specific to the individual LNUM.
LSR 72960 LSR fails and displays an ambiguous error message. The error message has been changed to make it more clear.
LSR 73101 When you make a change to the existing end user address on the LSR 6 form, a pop up window displays. The text in this window is not consistent. The test asks if you want to insert a record. This is confusing, because there isn't an Insert button. Also, SOFTWARE is spelled SOFWARE. The proper message is given when the window is displayed. Also, "software" is spelled correctly.
LSR 73361 You can't sort the feature details of a req type E order. You can now sort features on the Feature Detail window by Feature Activity, Feature or Feature Detail. You can also sort Additional Data values by clicking on the following headers: ON, MAX, Value Label, or Assigned Values.
LSR 73404 You are unable to populate the UDF for multiple end user location access sections. All sections show the same UDF values once populated. Additional Data can be added differently for different End User Location Access sections.
LSR 73460 You are unable to deactivate the LSR guideline rules for the TELNO and IWCON fields. The validation for EU Inside Wire is changed similar to other pages so that the validation rule can be deactivated and activated.
LSR 73462 You are unable to delete IWBAN of EU Inside Wire, EBD of LSR Bill, IBT of EU Location Access, and TCPER fo EU Disconnect. After deleting these fields, the fields still show up in the user interface when the sections are reopened. IWBAN of EU Inside Wire, EBD of LSR Bill, IBT of EU Location Access, and TCPER fo EU Disconnect can be deleted from user interface.
LSR Internal CR# 37859 Feature Details displayed on Port Service Details window of Loop and Port is not the correct length. It is only 25 characters in length and it should be 200 alphanumeric characters in length Feature Details displayed on Port Service Details window of Loop and Port will accept 200 characters.

The interface now accommodates 200 bytes in the Feature Details field. The Print Preview, Printed Form and Export file all display the 200 bytes for the selected feature.

LSR  Internal CR# 38039 The HT Form is provided on LS/PS request when it's not selected. HT form will not be displayed on the print preview form by default for request types E,F,M and P.
LSR Internal CR# 129694 Additional data not showing correctly in LSR6 Print Preview. Additional Data specific to each LNUM will be displayed correctly on the Print/Preview form.
LSR Internal CR# 129695 Default values for additional data cannot be deleted. Default additional data can now be deleted.
LSR Internal CR# 129697 Number Portability Detail displays incorrectly after adding additional data. Detail pages will be displayed correctly for individual LNUM after adding additional data.

LSR 6.7

Component

Issue ID

Problem

Resolution

LSR 72950 the LSR Bill SBILLNM drop-down does not show the ACNA address if it is invalid on infrastructure/Access Customer. If the Access Customer billing address is incomplete in the infrastructure, a non-obf error message will be displayed for the STATE, CITY and ZIP code fields on the billing form. The user may have to go and correct the Access Customer billing address in infrastructure/Access Customer.
LSR 73051 LSR PON is changing mid-stream when the SC field changes the LSR version. The parent PSR document number will be used to generate the PON when the user preference "Use the Parent Level Document Number" = Y.
LSR 73259 User cannot access a page in the Feature Details of an LSR order. They check off the available FA box, then click OK, but nothing happens even though the application server appears to be attempting to open a page at this link:

http://appservername/backoffice/lsr6/ fdsection.do

The user will once again be able to select the Feature from the Feature Detail window and the selection will be saved without an error message being generated. Once the Feature and Feature Activity is selected click on "OK" to have the feature saved, click OK again and you will be returned to the previous window.
LSR 73404 Unable to populate UDF for multiple End User Location Access sections. All sections show the same UDF values when populated. A User with a request that has multiple End User Locations can now select different UDF values for each EU Location Access section. 
LSR 73471 ONSP and NNSP fields are dependent on the CC field in the user interface. So, when the CC field is deleted without first deleting ONSP and NNSP, the ONSP and NNSP fields disappears from the user interface, but are exported in IDL. When the CC field is deleted or removed from the request. its corresponding NNSP and ONSP will also be removed from the request.  None of the removed fields will be displayed on print form and the CC, NNSP and ONSP fields will export a null value.
LSR 73517 On the LSNP/NP form, the LRN*CLLI field can not be populated. When the LRN CLLI is populated and the  LSNP/NP service detail section is reopened, the value for the field disappears. The change that allowed the LRN CLLI field to be populated after it has been saved / reopened has been rolled back in order to further look at the implications of this change.
LSR 74186 When the LRLoopConInfo fields are imported through the importLR operation, they do not show up in the user interface. The LRLoopConInfo fields can be imported through the importLR operation, and can be verified in the user interface.
LSR 74310 Customer wants to populate NNSP field with different OCN than what they have in CC field, but are not able to do this. You can now populate the NNSP field with a different OCN (NPAC SPID) than what you have in the CC field.
LSR 74473 You cannot import LSRCM because of ATN. LSRCM will be imported successfully without getting any error after changing the ATN value as alphanumeric.

LSR 6.8

Component

Issue ID

Problem

Resolution

LSR 74331 The DSGCON should not populate from the INIT field. The ALTIMPCON should not populate from the IMPCOM field The DSG information will not be populated from the INIT information. The ALTIMP fields will not be populated from the IMP fields
LSR 74921 The SATH value does not display on the End User form for an LSOG 6 order. SATH, SASS, and SASD values will be displayed in the EU form for LSOG6. Also SATH, SASS, and SASD values will be displayed in the EU form while navigating to some other form and come back to the EU form.
LSR 74854 When the LSR prints, there is roughly 2 inches at the left margin and 1+ inches at the right margin of blank space, with the print of the actual LSR being much smaller. This is not visible in the screen shot, only on the actual print out. At the bottom of the page, the paper size is showing 11 x 10.5, instead of 11 x 8.5. When the LSR displays it shows 11 x 8.5 and it prints fine. The Bottom of PrintPage size will be changed to 11 x 8.5 from 11 x 10.5.

 

LSR 74928 The Additonal Date link is disabled on the Local Resonse - Adminstration Section. The Additional Data link will be enabled when the LSR order is opened via Work Mgmt\Queue Mgr.
LSR 74884 Mapping LSR produced two identical PONs for LSOG 6. Identical PONs cannot be produced for LSOG6.
LSR 74946 User received an error message when they used PSR/LSR mapping, populated the NC_SERVICE_CD field with option "AH", and did not populate any other fields including NC_OPTION_CD and NCI SECNCI. The message states: "ExpertOrder undefined NULL Value required". An NC Field validation error message will be displayed, if NC_OPTION_CD is not selected after selecting NC_SERVICE_CD.
LSR 75122 The field remains functional, but now the user can only put in three characters of the 11 character ACTL. They then need to use the drop-down list to filter through every ACTL in the database that begins with those three characters. User should be able to input more then three characters. User will be able to enter the maximum characters allowed for the smart drop-down components as described in structure format. The user will also be able to manually enter the 11 character CLLI without having to use the drop-down.
LSR 75349 The application does not accept double digits in the DQTY field. DQTY field on the EuLocAccess Form will accept double digits and it will not throw an error message ("DQTY is not formatted correctly according to OBF standards"). The EUDisconnect form will not allow duplicate Disconnected Telephone Numbers (DiscNbr).
LSR 75378 An Internet Explorer script error is displayed in LSR for the 'Additional Data' form. Additional Data will accept special characters.

LSR 6.9

Component

Issue ID

Problem

Resolution

LSR Internal CR# 177551 The system requires the user to populate the NNSP field when it is different than the CC code. You cannot tell it is different until the user enters the value in the field. The system will not throw an NNSP validation error if the NNSP field is different than the CC code.
LSR 72318 The user receives an error on the LR Admin Form stating the NPORD is required. Edit is turned off in Guideline Rules. Also, the NPORD field is grayed out in LR Details. You are unable to add order numbers to the field manually. This prevents the LR from loading with an FOC. When the LSR Guideline Rule for NPORD is turned off, the system will no longer generate an error message requiring the NPORD to be populated. The Local Response will be imported with no problems and the user will be able to complete their request.
LSR 74445 User errors errors/problems while installing LSR for Solaris 6.0.2. Installer has been modified to ask for the start script directory (typically the Domain directory) and then will modify both the startMSLVmanaged.sh and startMSLVsingle.sh scripts indicated at that directory location.
LSR 75328 Manually entering an invalid ACTL does not return an error message and the REQTYP field entry was stripped out of the field. The user will receive a validation error message if they enter an invalid ACTL value. The REQTYP field will be stripped and the user will have to re-enter a valid ACTL and REQTYP for this request.

It will not insert a row in the 'ASAP.SERV_REQ' table if any LogFatalError is thrown.

LSR 75867 You are unable to populate the AFO field on a mapped LSR. The AFO field will be enabled for mapped orders.
LSR 76146 LSR is not showing as a NameService for API's. The java classes that handle creation of the HTTP name services were changed to account for the "web-app repackaging" done for the M6 environment and BEA 8.1.

Note: MSS version must be at 6.0.4.0, 6.0.5 or higher.

LSR 76258 LSR validation errors out on city, state, and zip code even though the LSR guideline rules have been marked inactive. LSR will not throw a validation error message for the NPDI field when LSR guidelines rules for EU Bill city, state and zip codes are set to inactive.
LSR 76284 You receive gateway errors when you attempt to export standalone directory listing requests. Standalone LSR and directory listing requests, and LSR/DLR combination orders, can be exported without error.
LSR 76471 Open JDSCStatementManagers create maximum open cursors, which cause an out of memory error. JDSCStatementManagers are closed after their usage which will avoid the problem of open cursors.
LSR 76640 java.lang.NullPointerException errors appear in the appconsole.log after LSR6.6 implementation. java.lang.NullPointerException errors will not appear in the appconsole.log after implementation.
LSR 76699 Address components that are mapped over from PSR to LSR are too large to be exported. The logic has been changed so that now when an LV address value is mapped over from PSR that is too large based on OBF standards, the value will be truncated to the appropriate length before being exported.
LSR 76774 The feature details do not save on an LSR with a  request type of M. LSR feature details will be saved correctly.
LSR 76776 You are unable to begin LSR remarks with a semicolon. The Remarks data will not save when a semicolon precedes all other data. Remarks data will be saved and loaded even if there is a semicolon character at the beginning.
LSR 76778 You cannot populate the NPORD field if you open the order via the RCONF task. The NPORD field will not be grayed out while opening an order via the RCONF task. The NPORD will be available for editing.
LSR 76814 When you create a new LSR from the service request hierarchy, the application is not attaching the LSR to the parent PSR. The LSR will now be associated to the parent PSR if it is created from the service request hierarchy of the PSR.
LSR 76828 The LSR FOC ECCKT field won't validate or save. The LSR FOC ECCKT field will be saved and validated on the LR form.
LSR 76855 The LSR/DSR LTXNUM, LTXTY, and LTEXT fields are not printing. The LTXNUM, LTXTY and LTEXT fields will be printed in the print preview for LSR/ DSR orders.
LSR 77075 You cannot add user defined values to the Blocking Components. The tab is grayed out. Added user-defined values for Blocking Components in the StructuredFormat(LSOG.LSOG_VALUES) which will be displayed in the full mode user interface.
LSR 77220 While running iterative LSR Print previews with multiple concurrent users, an application server "out of memory" error occurs. This occurs only on a UNIX platform. The XML/XSL to formatted output (FOP) to PDF generation in LSR was altered to combine some parts of the transformation process to be more efficient. Also some errant exception handling code was corrected. Corrected LSR "action" class so that use of variables is thread-safe.
LSR 77353 The LSR API is sending out feature details on the Port Service form when they are not selected on the order. The LSR API will not send the unselected feature details through the gateway.
LSR 77530 Customer reports that the sorting of feature details on an LSR removes details that have been entered. Sorting of feature details on an LSR will not remove selected features.

LSR 6.10

Component

Fixed Issue

Description

Issue ID: 78000

Internal CR#: 200700

Problem: LSR*DSR - You receive an error when changing the LVL field.
Resolution:
LSR*DSR will not throw an error while changing LVL field value.

Issue ID: 77253

Internal CR#: 184210

Problem: Valid values with hyphens are being cut off when added to the additional data for an LSR order.
Resolution:
Hyphened characters (which are populated in the ProductSpec/Catalog) will be displayed in the LSR AdditionalData.

Issue ID: 77075

Internal CR#: 185136

Problem: You are unable to add user defined values to the Blocking Components. The tab is grayed out.
Resolution:
Added UserDefined values for Blocking Components in the StructuredFormat(LSOG.LSOG_VALUES). These will be displayed in the full-mode GUI. User defined data will not be available in express entry at this time.

Issue ID: 75328

Internal CR#: 189236

Problem: Manually entering an invalid ACTL did not return an error message and the REQTYP field entry was being stripped out of the field.
Resolution:
Users will receive a validation error message if they enter an invalid ACTL value. The REQTYP field will be stripped and the user will have to re-enter a valid ACTL and REQTYP for this request.

Issue ID: 76146

Internal CR#: 184949

Problem: LSR is not showing as a NameService for API's.
Resolution:
The java classes that handle creation of the HTTP name services were changed to account for the "web-app repackaging" done for the M6 environment and BEA 8.1. MSS must be at 6.0.4.0, 6.0.5 or higher

Issue ID: 77220

Internal CR#: 184472

Problem: While running iterative LSR Print previews with multiple concurrent users, an application server "out of memory" error occurs. This occurs only on a UNIX platform.
Resolution:
The XML/XSL to formatted output (FOP) to PDF generation in LSR was altered to combine some parts of the transformation process to be more efficient. Also some errant exception handling code was corrected. Corrected LSR "action" class so that use of variables is thread-safe.

Issue ID: 77530

Internal CR#: 187228

Problem: Customer reports that the sorting of Feature Details on an LSR removes details that have been entered.
Resolution:
Sorting of Feature Details in LSR will not remove selected features.

Issue ID: 77522

Internal CR#: 188106

Problem: Customer reports an IE error when they attempt to add a call block ID to a new LSR.
Resolution:
You can add and remove a call block ID to a new LSR without getting a IE error.

Issue ID: 203929

Internal CR#: 204157

Problem: User is not being able to remove information from the LSR once it's saved.
Resolution:
User can remove data from the LSR EuBill Section.

Issue ID: 76947

Internal CR#: 185166

Problem: User receives a warning message about the structured format not being correct. All structured formats have been entered correctly and the user still gets the warning.
R
esolution: Warning message will not be displayed when block and feature detail components are added to the structure format.

Issue ID:

Internal CR#: 206020

Problem: When doing an exportLSR, the LSLoopConInfos structure is populated with blank values when all four parts are not populated for CTI, CABLE ID, CBCID and CHAN/PAIR. The customer wants the structure to be exported only when the fields are populated.
Resolution:
When doing an exportLSR, the LSLoopConInfos structure will not be populated with blank values when not all four parts are populated for CTI, CABLE ID, CBCID and CHAN/PAIR when creating the LSR. Only those structures that are populated will be exported.

Issue ID:

Internal CR#: 206030

Problem: Change build scripts to fix lsr_integration.ear and LSR6.ear problems. 1) The lsr_integration.ear file had two listing for the LSR6.ear. One at root and another one. The root one needs to be deleted. 2) The LSR6.ear file is not showing up in the LSR_EJB.jar.
Resolution:
Changed the build scripts to fix lsr_integration.ear and LSR6.ear to alleviate these problems.

Issue ID:

Internal CR#: 182571

Problem: Invalid error for LSR on REMARK being required.
Resolution:
LogFatal Error will not be displayed in the application server  log for the REMARK field.

Issue ID: 77353

Internal CR#: 186181

Problem: The LSR API is sending out feature details on the Port Service form when they are not selected on the order.
Resolution:
API will not send the unselected Feature details through Gateway.

Issue ID: 72318

Internal CR#: 187185

Problem: Error on LR Admin stating NP ORD is required. Edit is turned off in Guideline Rules. Also NPORD field is grayed out in LR Details. Unable to add Order numbers to field manually. This prevents the LR from loading with an FOC in TBS.
Resolution:
When the LSR Guideline Rule for NPORD is turned off, the system will no longer generate an error message requiring the NPORD to be populated. The Local Response will be imported with no problems and the user will be able to complete their request. The user can also manually add an NPORD number to the LR Service Detail window and it will be stored in the LSC_DETAIL table in the NP_ORD_NBR on the database.

Issue ID: 207727

Internal CR#: 208105

Problem: Unable to populate the DIRQTY field with numeric.
Resolution:
Pattern introduced to accept only numeric values for the DIRQTY field.

Issue ID:

Internal CR#: 208228

Problem: You cannot export orders that have feature details associated to them.
Resolution:
LSOG defines the Feature Code as 6 character length and therefore the Feature code is trimmed for 6 characters while exporting the LSR order that is associated with Feature Details.

Issue ID: 77292

Internal CR#: 185026

Problem: Unable to add additional data to HGI form.
Resolution:
Additional data will display on the HGI form after adding it in the Product Spec and Product Catalog.

Issue ID: 74609

Internal CR#: 185468

Problem: LSRCM encounters error during import and fails. The error states the following: The server encountered the following Exception: Code: 20042 Message: LSRCM notice found for Document Number 443920, only 1 allowed Severity: 4 From Class: Debug Code: 0.
Resolution:
LSRCM will import successfully after the LR is received and imported. If the LSRCM is received and imported before the receipt of the LR, when the LR is trying to import into the system you will receive the following error message; LSRCM notice found for Document Number XXXXXX, may not import LR after LSRCM has been received.

When  the LSRCM has been received, the order is considered complete and you cannot import or receive a Local Response (LR). The LSRCM will be inserted to the CONF_NOTICE.FORM_ID as 'LSRCM' and not 'LSC'. Also, a SQL script (CR182480.sql) will be supplied to clean bad data.

Issue ID: 77379

Internal CR#: 189129

Problem: TNs entered on the LR form are not showing up in the LSR GUI.
Resolution:
The entered TNs value in the imporLR will be imported and it will be displayed in the GUI (LRServiceDetailForm).

Issue ID: 76790

Internal CR#: 200494

Problem: Customer reports that address changes are not saving correctly when using the New From to create a new LSR.
Resolution:
Address changes will be saved properly when using New From to create a new LSR.

LSR 6.11

Component

Fixed Issue

Description

Issue ID: 78000

Internal CR#: 200700

Problem: LSR*DSR - You receive an error when changing the LVL field.
Resolution:
LSR*DSR will not throw an error while changing LVL field value.

Issue ID: 77253

Internal CR#: 184210

Problem: Valid values with hyphens are being cut off when added to the additional data for an LSR order.
Resolution:
Hyphened characters (which are populated in the ProductSpec/Catalog) will be displayed in the LSR AdditionalData.

Issue ID: 77075

Internal CR#: 185136

Problem: You are unable to add user defined values to the Blocking Components. The tab is grayed out.
Resolution:
Added UserDefined values for Blocking Components in the StructuredFormat(LSOG.LSOG_VALUES). These will be displayed in the full-mode GUI. User defined data will not be available in express entry at this time.

Issue ID: 75328

Internal CR#: 189236

Problem: Manually entering an invalid ACTL did not return an error message and the REQTYP field entry was being stripped out of the field.
Resolution:
Users will receive a validation error message if they enter an invalid ACTL value. The REQTYP field will be stripped and the user will have to re-enter a valid ACTL and REQTYP for this request.

Issue ID: 76146

Internal CR#: 184949

Problem: LSR is not showing as a NameService for API's.
Resolution:
The java classes that handle creation of the HTTP name services were changed to account for the "web-app repackaging" done for the M6 environment and BEA 8.1. MSS must be at 6.0.4.0, 6.0.5 or higher

Issue ID: 77220

Internal CR#: 184472

Problem: While running iterative LSR Print previews with multiple concurrent users, an application server "out of memory" error occurs. This occurs only on a UNIX platform.
Resolution:
The XML/XSL to formatted output (FOP) to PDF generation in LSR was altered to combine some parts of the transformation process to be more efficient. Also some errant exception handling code was corrected. Corrected LSR "action" class so that use of variables is thread-safe.

Issue ID: 77530

Internal CR#: 187228

Problem: Customer reports that the sorting of Feature Details on an LSR removes details that have been entered.
Resolution:
Sorting of Feature Details in LSR will not remove selected features.

Issue ID: 77522

Internal CR#: 188106

Problem: Customer reports an IE error when they attempt to add a call block ID to a new LSR.
Resolution:
You can add and remove a call block ID to a new LSR without getting a IE error.

Issue ID: 203929

Internal CR#: 204157

Problem: User is not being able to remove information from the LSR once it's saved.
Resolution:
User can remove data from the LSR EuBill Section.

Issue ID: 76947

Internal CR#: 185166

Problem: User receives a warning message about the structured format not being correct. All structured formats have been entered correctly and the user still gets the warning.
R
esolution: Warning message will not be displayed when block and feature detail components are added to the structure format.

Issue ID:

Internal CR#: 206020

Problem: When doing an exportLSR, the LSLoopConInfos structure is populated with blank values when all four parts are not populated for CTI, CABLE ID, CBCID and CHAN/PAIR. The customer wants the structure to be exported only when the fields are populated.
Resolution:
When doing an exportLSR, the LSLoopConInfos structure will not be populated with blank values when not all four parts are populated for CTI, CABLE ID, CBCID and CHAN/PAIR when creating the LSR. Only those structures that are populated will be exported.

Issue ID:

Internal CR#: 206030

Problem: Change build scripts to fix lsr_integration.ear and LSR6.ear problems. 1) The lsr_integration.ear file had two listing for the LSR6.ear. One at root and another one. The root one needs to be deleted. 2) The LSR6.ear file is not showing up in the LSR_EJB.jar.
Resolution:
Changed the build scripts to fix lsr_integration.ear and LSR6.ear to alleviate these problems.

Issue ID:

Internal CR#: 182571

Problem: Invalid error for LSR on REMARK being required.
Resolution:
LogFatal Error will not be displayed in the application server  log for the REMARK field.

Issue ID: 77353

Internal CR#: 186181

Problem: The LSR API is sending out feature details on the Port Service form when they are not selected on the order.
Resolution:
API will not send the unselected Feature details through Gateway.

Issue ID: 72318

Internal CR#: 187185

Problem: Error on LR Admin stating NP ORD is required. Edit is turned off in Guideline Rules. Also NPORD field is grayed out in LR Details. Unable to add Order numbers to field manually. This prevents the LR from loading with an FOC in TBS.
Resolution:
When the LSR Guideline Rule for NPORD is turned off, the system will no longer generate an error message requiring the NPORD to be populated. The Local Response will be imported with no problems and the user will be able to complete their request. The user can also manually add an NPORD number to the LR Service Detail window and it will be stored in the LSC_DETAIL table in the NP_ORD_NBR on the database.

Issue ID: 207727

Internal CR#: 208105

Problem: Unable to populate the DIRQTY field with numeric.
Resolution:
Pattern introduced to accept only numeric values for the DIRQTY field.

Issue ID:

Internal CR#: 208228

Problem: You cannot export orders that have feature details associated to them.
Resolution:
LSOG defines the Feature Code as 6 character length and therefore the Feature code is trimmed for 6 characters while exporting the LSR order that is associated with Feature Details.

Issue ID: 77292

Internal CR#: 185026

Problem: Unable to add additional data to HGI form.
Resolution:
Additional data will display on the HGI form after adding it in the Product Spec and Product Catalog.

Issue ID: 74609

Internal CR#: 185468

Problem: LSRCM encounters error during import and fails. The error states the following: The server encountered the following Exception: Code: 20042 Message: LSRCM notice found for Document Number 443920, only 1 allowed Severity: 4 From Class: Debug Code: 0.
Resolution:
LSRCM will import successfully after the LR is received and imported. If the LSRCM is received and imported before the receipt of the LR, when the LR is trying to import into the system you will receive the following error message; LSRCM notice found for Document Number XXXXXX, may not import LR after LSRCM has been received.

When  the LSRCM has been received, the order is considered complete and you cannot import or receive a Local Response (LR). The LSRCM will be inserted to the CONF_NOTICE.FORM_ID as 'LSRCM' and not 'LSC'. Also, a SQL script (CR182480.sql) will be supplied to clean bad data.

Issue ID: 77379

Internal CR#: 189129

Problem: TNs entered on the LR form are not showing up in the LSR GUI.
Resolution:
The entered TNs value in the imporLR will be imported and it will be displayed in the GUI (LRServiceDetailForm).

Issue ID: 76790

Internal CR#: 200494

Problem: Customer reports that address changes are not saving correctly when using the New From to create a new LSR.
Resolution:
Address changes will be saved properly when using New From to create a new LSR.

 


Copyright © 1994-2004, 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.