Cumulative IR Tables for 6.0.1 - 6.0.12

This document contains the published Fixed Issue tables from the Release Notes for the 6.0.1 through 6.0.12 service packs. The tables are listed in ascending order, beginning with the first service pack and continuing to the most recent.

MSS 6.0.1

Component Issue ID Problem Resolution
ASR 50745 You are unable to add trunk range of 0 * 0 (per the ASOG). Altered the trunk number range window so that a range of 0 to 0 is allowed.
ASR 69068 On BHMS order, you are unable to select EOD button on Non-company owned ASR. The trunk circuit identification window was being improperly closed following cancel of the query. The circuit ID page is now available following the query cancel. The EOD button and window can then be accessed for the BHMS change order.
ASR 69782 Not all of the Billing Information is being carried over to the Billing Window in CABS Bill Prep from the Access Customer Table. A view, v_acna_addr, was inappropriately changed with an earlier CR. The view is used in the retrieval of the billing address information in CABS bill prep. The view has been altered to correct the problem.
ASR 71096 CFA validation is not working as expected. CFA is being padded with spaces when the Pad Spaces preference is turned off and the CFA is also being truncated when its length exceeds 42 characters. An error message should be sent back instead of putting incorrect data into the database. CFA will not get Truncated. The error message will be logged when the CFA length exceeds the limit.

CFA will not be padded with spaces when the Pad Spaces preference is turned off.
Engineering 41526 The disconnected lines for a Disconnected order that was Due Date completed would be automatically removed at DD completion if the preference was set to automatically remove.  Disconnected orders should always keep the disconnected lines since it is a disconnected order. Therefore, if the preference is set to 'Remove', when Due Date completing a Disconnect order, the disconnected lines will not be automatically removed. The preference will not take into account Disconnect orders.
Engineering 68553 1. The SECNCI field on an ASR order of request type E, S, V, W, X or R is not transferred to the Design tab in Circuit Design.
2. When the value of SECNCI is changed after supplementing an ASR order, the changes are not reflected on the Design tab.
3. The NC and NCI fields on an ASR order of request type R are not transfered to the Design tab.
1. The SECNCI field on an ASR order of request type E, S, V, W, X or R will be transferred to the Design tab.
2. When the value of SECNCI is changed after supplementing an ASR order, the changes will be reflected on the Design tab.
3. The NC and NCI fields on an ASR order of request type R will be transferred to the Design tab.
Engineering 69256 An error is received when trying to access the CLR for a circuit in customer profile. If a circuit has been deleted and its CLR is trying to be accessed from customer profile, a message will be displayed stating that the necessary information no longer exists.
Engineering 69938 When supplement canceling a change order that has an equipment block that has been manually disconnected and the equipment has been cross-connected, the supplement cancel process is halted. When supplement canceling a change order that has an equipment block that has been manually disconnected and the equipment has been cross-connected, the supplement cancel process will complete successfully.
Engineering 70238 Reconciliation and Mass Reconciliation are not bringing FTPC parameters. Added support to the reconcile process to also copy the Flow Through Provisioning Data when reconciling an Equipment or EPA block.
Engineering 70484 When there are multiple circuits present on a D order, the CLR preview and print show the correct order number for the first circuit. The remainder of the circuits show some other order number on the print and preview.  Before tasks are created, the ISR order will be automatically saved in order to capture any modifications made to the order number. The CLR will display the modified order number without having to save for each disconnected circuit on the order.
Engineering 70647 Response time on Eng*Conn Design when searching by TGN is too long. Querying for a trunk group by the TGN performance is tuned.
Engineering 70682 Group Assign is assigning equipment that is disconnected. If the block is disconnected on the base circuit, it should not be copied to other circuits.
Engineering 70982 An oracle error, "ORA-02292:integrity constraint (ASAP.FK_DE_NS_ RE_CA_VA _NS_CO_RE_CA) violated -child record found ", occurs when trying to delete a physical connection through PSR. The reason for the error occurring is because there are virtual connections still associated to the physical connection. For this reason, the error message is correct in popping up, but the message isn't really helpful to the user. Now, a new error message box will appear which will inform the user that there are still virtual connections associated to the physical connection, and the user will be given a list of the virtual connections.
Engineering 70997 The exception report generated when the Mass Reconcile is initiated at the spec level includes disconnected circuits. Disconnected circuits will not be included in the Mass DLR Reconcile process. Therefore, when initiating the reconcile process at the spec level, disconnected circuits will not be included and therefore will not display on the Exception Report.
Engineering 71164 The Rate Code field on bandwidth circuits is too small to display more than 6 character rate codes. Rate codes of up to 10 characters are allowed. Rate Code Field width has been increased to display 10 character rate codes.
Engineering 71302 If a PSR order has a PON greater than 16 characters, the PON was being truncated to 16 characters in the Circuit Design window on the Admin tab. Also, the PON displayed in the CLR and DLR was being truncated to 16 characters. Since the PON is now on the ISI-DLR tab on the connection summary, the PON for a PSR will still display as only 16 characters since that is the OBF industry standard for regulated ordering. The PSR PON will only display more than 16 characters in the CLR.
Engineering 71437 When the Cross Connect Report is saved, the html is wrapping the text in the report. When the customer imports the report into Excel, they have to do a lot of copy/paste to get it back to the way it was in the application.
The Cross Connect Report save functionality was modified to save the report as displayed rather than saving the printable version. The displayed report that is saved will open in Excel and look much the way it did in the application. Additionally, the save file type now defaults to HTML with a default file name of CCReport.html.
Engineering 71450 For previous designs of circuits, the software does not allow navigation to all of the necessary Inventory fields (Ownership/Assignment Control/Circuit Reference Association/Leased Circuit Information). For previous designs of circuits, the Ownership tab and assignment control tabs have been modified to allow users to choose selected rows. Modification is still not allowed. In addition, the User Data section on the Leased Circuit Information tab is now scrollable when it is disabled.
Engineering 71494 When a circuit has a coded location for either the Priloc or Secloc, the location is not displaying in the CLR preview. When a circuit has a coded location for either the Priloc or Secloc, the location will display in the CLR preview.
Engineering 71497 Circuits created in PSR using the 'Generate Circuit IDs' appear in the Service Request Connections window with an 'In Progress' status. They should be 'Pending' as their designs have not yet been worked. Circuits created in PSR using the 'Generate Circuit IDs' will appear in the Service Request Connections window as 'Pending' when no design work has been done.
Engineering 71909 The year is not visible on the connection Notes window. The column is now wide enough to display the entire date.
Engineering 71919 The Misc. Info section of a circuit design is cut off. To see the entire design, the user must Hide the Navbar, then reduce the size of the tool area using the bar. If the tool area were made smaller but still readable, the user would not have to move this bar. Several columns with two line column headings were wider than they needed to be. The size of these columns was reduced to be the correct size and the additional space allows all columns to be displayed, especially when the Navbar is hidden.
Engineering 71920 The grey blocks on the DLR for a Faciity only include the LOCN, EQPT TYPE, RELAY RACK, and UNIT columns. Now the grey blocks in design extended across the page.
Engineering 71925 When you assign or remove an equipment block from a facility, you are not always asked if you would like to reconcile the child circuits. When you assign or remove a equipment block from a facility, you will be asked if they would like to reconcile the child circuits.
Engineering 71962 If you are sitting in the middle of a block on the design and adds Foreign Info, the line is inserted in the middle of the block, if you do the same for Misc Info, it is inserted below the line group. The foreign info block is now added below the selected block. You still have the ability to move the block inside of another block and embed it.
Engineering 72035 When you search on the Connection Design Window for a specific end user location, the search returns more circuits than the location selected. The new changes will retrieve correctly in the Connection Design Window for a specific end user location.
Engineering 72063 On the Connection Design Query window, if you search for an element name it works the first time. If you do not close the window and modify the search to search for a different element name, you get a No Rows Returned message when there are rows that should be displayed. Now the Connection Design Query by Element Name is working properly.
Equipment 71653 When the node address is changed at the spec level, equipment install is updated, but no reconcile prompt window is received and the impacted drop ports are not reconciled. The problem when a user changes the node address of the physical port (the top level) was fixed. It reconciles the assignments.

When a user changes the node address of the enabled port address, it needs to reconcile the mappings. Modified code to look for mappings when equipment spec has been modified.
Equipment 71985 A oracle error occurs when trying to: A) add a card on a relay rack outside of a shelf B) move a shelf to another location or C) add a new shelf inside a relay rack. It appears that after hitting okay, the equpment is installed/moved correctly, but it's unknown what underlying problems might occur because of the error. Corrected code that was causing the error. The error involved SQL that verifies that there is enough room for the equipment being added or moved. Validation now occurs without error.
ISR 71020 Fields dropped from circuit window when it is reopened. When initially introduced, the fields in question were only supposed to be used by CLS or OTS type circuits. Therefore, when the window opened it was hiding the fields if the user was on a CLF type circuit. This restriction has been removed and the fields now can be used for any type of circuit. Therefore they will always be visible.
ISR 71023 New From does not populate Framing, Line Coding, Framing ANSI, Customer Circuit Reference, and Circuit Description. Fixed so that on New From, values are defaulted for Framing, Line Coding, Framing ANSI, Customer Circuit Reference, and Circuit Description.
ISR 71062 Framing and Line Coding fields need a "None" option like the Framing ANSI field "None" option added for Framing and Line Coding fields like the Framing ANSI field
PSR 63821 When querying for numbers to assign to a ported out product in PSR, the system should not bring back anything that is not local company-owned. Added validation that will stop the assignment of a TN for Porting Out if not Company Owned or Foreign.
PSR 64300 Connection IDs are not consistently appearing. There are in-service serv_items that are not showing an ecckt. Circuits can be deleted. There is not a matching circuit record nor a serv_item description. To resolve this issue, the code that shows circuits, was changed so that if there is not a circuit in the circuit table to match the in-service serv_item, then the verbiage shows 'Unknown' rather than 'In-service'.
PSR 70031 I created a new PSR order and put a line product with one line on it. I assigned the TN. I finished the order and assigned tasks. I opened the E911 smart task and highlighted the row and clicked send. The extract data was created. I then went and supp cancelled the PSR order. The extract data is still out there. It should be deleted.
I never ran the extract method.
Also, if you supp cancel an order before creating the extract row, if the user opens the E911 smart task and try to create the extract on a supp cancelled order, then it should stop them.
Supp-Cancel processing is now supported for E911. Regarding the problem description, if extract data has been generated before the order is cancelled, the row is deleted if it has not be sent. If it HAS been sent, it is marked for a resend as a delete.

If you cancel an order BEFORE creating the extract row, the extract row cannot be created. The line will not even appear on the extract window. In this scenario, only rows that have been created prior to the supp cancel will appear on the window, typically marked for a resend as a change or delete.

Processing has also been added so deal with a cancelled move scenario, as well as to reset service item level usage information if it was changed on the cancelled order. (i.e., if an inservice line is copied to the order, and usage info is changed, and then the order is cancelled, the extract reverts to the previous usage information).
PSR 70280 When you  attempt to Supp Cancel a PSR with a completed DLRD task,  reopen the DLRD task and click Canc Chg for the circuit in question, the related cable pair still shows as In Service and cannot be reused. This is a Prod Fix SQL that Cancels circuits where the service item has been canceled. The code in PSR Due Date has already been fixed. 
PSR 70354 The time stamp on the customer notes is not accurate when imported via the PSR API. The Date Entered field on the customer notes is supposed to be stored in GMT time zone and converted when it is displayed to the user's local time zone. The date was not being stored in GMT, but it was being converted to local time as if it was. The API was modified to store the date in GMT, so new notes entered will now display correctly in the user's local time zone.
PSR 70469 When searching for a specific facility using the copy from feature, it returns an error stating that "The Search Criteria did not Produce any Matches" even though there are matching values depending of if you put a space between the 'LIKE' and '%'. In oracle version 9.2.0.3.11 or higher, an oracle error (ORA - 24347) also occurs saying that null cannot be entered into the aggregate function. The criteria for LIKE clauses was being calculated incorrectly. This has been corrected.
PSR 70678 There is no way to uncheck the E911 extract indicator. A menu option was added to the E911 Smart Task window that will now allow the user to select one or more rows that have the e911 extract indicator set to 'Y' and update the extract_ind to 'N' for those rows. The sub menu option is called "Uncheck Extract Ind." and is located under the Options menu list and in the right click pop up menu.
PSR 70851 Initiate a Send Bill Ord (SBO) gateway event and receive the following error message "Gateway server errored: Trunk Product Billing Service Instance with Usage Guide Key of Telephone Number has no number associated with it, when one is required.". This same product configured the same way in the 4.5.7.14 Product Catalog did not cause this error when the SBO gateway event initiates.
The placement of the code that calls BTN was incorrect. The problem has been corrected.
PSR 71112 Customer needs the Customer Class to be either ISP or non*ISP to Validate orders with IP Addresses (IPADDR type products). They do not need the Cust Class to validate order with IP Addresses. The validation error message "The Customer Class is null for an order with an IPADDR item, and customer's primary billing address country is in North America, South America, Central America, or the Caribbean." will no longer be received if an IPADDR item is on a PSR and the Customer Class for the customer account is set to 'None'. The user will now be able to validate and finish any orders they were previously receiving this validation error message on successfully.
PSR 71160 Default date entered for User Data fields are not appearing in the PSR Order. The Default date set up for the user data field in Infrastructure will now display when entering the user data for a PSR.
PSR 71453 Customer reports getting the following error upon DD completion for a disconnect PSR. " Error in PSR Due Date. Please contact your system administrator.
of_get_current_or_parent_loc: 10:ORA-01422: exact fetch
returns more than requested number of rows"
An error in the SQL in the PSR due date logic has been corrected.
PSR 71504 Customer reports that some TNs are cut off in Print Preview. The column was widened.
PSR 71510 The reservation number field in Telephone Numbers window can support only 6 digits. The criteria input field for Reservation Number on the Telephone Numbers query window was expanded to support 9 digits. This window may be accessed from a PSR order or from Infrastructure (List => Number Inventory => Telephone Number Inventory...).
PSR 71598 Execute importPSR for a product that has a value/label that has a default value of space " ". In the api importPSR call, try to delete the default value/label for the space and add a new value/label but receive the following error message:
[0] Field: code = 30782
[0] Field: reason = This order has labels with null values, null values are not allowed.
[1] Field: code = 39990
[1] Field: reason = Miscellaneous Error: This order has labels with null values, null values are not allowed..
[2] Field: code = 30766
[2] Field: reason = Unable to process item B COMM SWITCHED 1+ (specId 3336, product group 1) due to errors listed.
The importPSR API was returning an error if the input value/label being deleted was spaces or null. This validation was modified to check only for a null value if the value is being deleted. Note that the input value to be deleted must exactly match what is in the database, including the case where the value is spaces. For example, if the value in the database is five spaces, the value input to the importAPI must also be five spaces.
PSR 71698 Item Info tab is not displaying the Hunt Groups in line number order. Changed order history to display hunt groups in line number order on Product History tab of Customer Account window and on Item Info tab of PSR Order window.
PSR 71704 Customer reports the following error when attempting to add a value to a label in Product Catalog:
Please add an Upstream bit rate on the Default Values tab.
(This value is required when the Transport Type label is populated.)
Corrected validation so error message no longer displays when values exist.
PSR 71808 When the user Supp Cancels an Order that is in a MPO scenario, and other orders are stacked up after it, the user does not receive a warning message telling them there are other open orders.
Modified application so Supp Cancel Alert window displays when Supp Cancel is performed on order with items that exist on another open order. The alert window displays each item on another order along with the other order number(s) and their activity code and due date. After alert window displays, the user has the option to cancel or continue with the Supp Cancel.
PSR 71811 Execute importPSR API operation and enter PSROrderNotes, view the PSR order in the GUI and the Created By date is 6 hours off. The API is not storing the time in GMT and the GUI is converting the time so it is off by 6 hours. If you create a PSR order note via the MetaSolv Solution, the time is correct. Changed importPSR to store Notes date_entered value in GMT time zone.
PSR 71823 Customer reports that TN status is not updating from Unassigned to Reserved status when adding to a new reservation group. The logic has been corrected so that numbers do change to Reserved status when the reservation is saved. Numbers should appear on the reservation list as Unassigned when they are first queried for, and then will change to Reserved when the reservation is actually saved.
PSR 71899 Your not able to double click to select the customer from the customer account search screen for a new PSR. Double clicking one of the results rows will select that customer account and return with it.
PSR 71907 Customer reports that the PSR Supp New Due Date function is not updating properly. Updated changes are not reflected on the Order Info tab. Modified the logic to retrieve the Order Info after the processing of the supp due date.
Technical Framework 71828 Null Object Reference error message encountered upon clicking tbs.exe after install. Error message is ambiguous. Need to get a specific error message in order to determine root cause of issue. An appropriate and specific error message is displayed telling the user to at least install IE 6.0 SP1.
Technical Framework 72044 When you add a custom link to a group when customizing the Nav bar to open a file that needs another program, the Nav bar went away completely and when they try to add a group to try to correct it, a java exception occurs. If you add a custom link to the Nav bar that contains one or more double quotes, the Nav bar will not disappear.
Technical Framework 72088 If you set your pc to use large fonts, you are not able to see all of the necessary information within the application. Also, customer reports that when using "Large Fonts" the Nav Bar text is cut off.
This is a partial fix. A change in the framework was made to better accommodate the "Large Fonts" display setting. However, because many of the descendent windows override the framework behavior, users will still see problems when they use large fonts. Some windows can be fixed manually. Also, as the Nav Bar is not resizable, the user should be able to see the entire text by hovering their cursor over the link in question.
Work Management 63724 Not all tasks for an order go to Jeopardy Status when you select "Apply to all tasks for an order". Now the Jeopardy status was copied to all the task when "Apply to all tasks for an order" check box was selected
Work Management 70327 Dates for tasks on a provisioning plan are automatically defaulting to non-work days by not adjusting the task dates to leave out these days. The "Allow user to schedule tasks on non-workdays" preference has been fixed to not ignore workdays when tasks are being scheduled. Before the fix, when the preference was turned on tasks were scheduled 7 days a week regardless of the organization calendar having non-workdays defined. Now, the non-workdays will be used when the provisioning plan is selected. The user will have the ability to schedule tasks to complete on a non-workday on a task by task basis.

 

MSS 6.0.2

Component Issue ID Problem Resolution
ASR 69370 ISR does not allow reuse of existing Trunk Group circuit or Two Six Code to add new trunks.

ASR creates a New Trunk Group in the database when trunks are added to an existing Trunk Group. It should reuse the existing data within the database, not create new rows.
The issue of reuse of the two-six code was corrected in an earlier service pack. It is entirely accurate to create a new trunk_group_design_id for the new trunk that is reusing the ECCKT from a previously disconnected trunk group. However, the code needed to be corrected so that that ECCKT is removed from the old TRUNK_GROUP table entry.
ASR 70522 If a user has the USOC entered but accidentally deletes the quantity, the validation does not catch the missing value. Added validation to check that the USOC quantity and amount are both greater than 0 if added for the circuit and location in ASR CABS Bill prep.
ASR 71933 Users are unable to create ASRs using the New/From functionality Corrected the stored procedure used in the "new-from" action so that when the CCNA data is retrieved it looks for only the "active" entry that matches the customer name abbreviation supplied. Also added code to properly set the "sent_recv_cd" of the new order based on the new combination of CCNA and ICSC.
ASR 72016 Problems with CFA on ASR coming forward to Bill Prep. Altered the CABS prep process so that if an ACI is associated to the facility circuit, the CFA info for CABS will be retrieved from the ACI data on the order.
Engineering 34428 The Misc. Info section of a circuit design is cut off. To see the entire design, the user must Hide the Navbar, then reduce the size of the tool area using the bar. If the tool area were made smaller but still readable, the user would not have to move this bar. The width of multi-line column headings were appropriately reduced, providing a more appropriate layout that now shows almost all of the information in all of the columns. When necessary the navigation bar can be closed and all the data in all the columns will be displayed.
Engineering 46998 Need separate security functionality for Cascading Reconciliation. Currently it uses the same security permissions and users as Mass Equipment Edit/Move Reconcile. Separate security functionality exists for Cascading Reconciliation.
Engineering 65304 User may be unable to Due Date complete an order for a Virtual Connection as a result of an Oracle Fetch error. User will be able to successfully Due Date complete an order for a Virtual Connection.
Engineering 65486 The DD task on Supp-Cancel cannot be completed. This particular issue only occurs if there is a DESIGN task that follows the DD task. The validation has been altered for a Supp Cancel process to complete a DD task even if there is an additional design task that follows the DD task. Additionally, the design task that follows the DD task will only open up in Read-Only mode.
Engineering 65672 Not all information is contained from ISR on the Tech Translations sheet. Tech Translation Sheet issues are corrected.
Engineering 69042 When a user assigns a circuit to a Sonet route that is Path Switched without TSI and the circuit's rate code exists at multiple levels in the Sonet hierarchy, the circuit does not always get assigned all the way around the ring on the same position. This is a problem during Auto-Assign and manual assign. This makes for an invalid Sonet system. Now when a user assigns a circuit to a Path Switched Sonet without TSI and the circuit's rate code exists at multiple levels in the Sonet hierarchy, both the auto and manual assignment process will verify that the same channel is being selected all the way around the ring.
Engineering 69310 Cross connect has been removed but the mapping did not release the position The code to find the original assignment indicator does not loop all the way to the top level. Because of this problem the mappings did not get removed, so this port could not be reused.
Engineering 69551 When you perform a product transfer, Cascading Reconcile is triggered. You get the error message "Unsuccessful retrieval of circuit product data for Administration section of DLR ..." for each child circuit that the system is attempting to reconcile. When Due Date completing a Transfer order, Cascading Reconcile will not be initiated. The Due Date task will complete successfully.
Engineering 69971 When some background processor reconcile jobs are restarted, their status is left in Executing even though the worker has completed. The background processor reconcile jobs that are restarted will finish with a status of Completed.
Engineering 69987 Some orders have been sup-cancelled and any engineering work reversed, but the service_request_status.circuit_status was not correctly updated. This prevents the order, or other orders containing the affected circuits, to be completed. The script cr26224.sql will update the status with order field on the circuit design window for circuits that have been through the sup-cancel process but are not in a Cancelled or Inservice status. The open orders these circuits are on should then be able to complete successfully. If there are any lingering circuit status or issue status problems due to the circuit not finishing the sup-cancel process, the connections.sql script should correct them.
Engineering 70000 The application is allowing the user to DD complete an order that has a physical circuit associated to a network element, even though the network is not yet In Service and it's not on the current order. Added a validation for physical connections on Due date completion logic.
Engineering 70484 When there are multiple circuits present on a D order, the CLR preview and print show the correct order number for the first circuit. The remainder of the circuits show some other order number on the print and preview.
Before tasks are created, the ISR order will be automatically saved in order to capture any modifications made to the order number. The CLR will display the modified Order number without having to save for each disconnected circuit on the order.
Engineering 70508 When viewing the details for a PSR order using the CLR or the Prod Cat Details tab in connections design, there is no way to determine the type of activity for a data label and value. When viewing the details for a PSR order using the CLR or the Prod Cat Details tab in connections design, the activity column was added to determine the type of activity for a data label and value.
Engineering 70541 There are circuits that have been on a order to create them, but no issue was ever created for that circuit with the order. This means there are missing issues for the circuit and a problem can arise if another order is entered against the circuit and the order is sup-cancelled since often there is no current issue for the circuit. Running CR33106.sql creates an issue for the circuit to match the order that created the circuit. If any issues currently exist for orders after the new activity, they will be bumped up by one issue. Any corresponding information, such as notes, will be bumped up as well.
Engineering 70631 TID is being placed at the Bay level Now, the TID will appear at the correct location on the design lines.
Engineering 70634, 70927 After some orders are cancelled, the circuit activity (seen on the service request connections window when a dlrd or rid type task is opened) for the circuits on the order gets set to "A". If the Cancel Change button is used, the activity gets correctly updated to "K" for cancelled, but the circuit status with order gets set to null. This prevents the order from being completed. This script will fix the bad data and will allow the user to successfully complete the supp canceled orders. Following the successful completion of this script, for further data integrity, it is suggested to also run the connections.sql script available to customers on the portal.
Engineering 70647 The response time on Eng*Conn Design when searching by TGN is taking too long. Improved performance of TGN search in connection design.
Engineering 70805 When performing Auto Provision for a virtual connection, an Exception: java.lang.NullPointerException error is returned. Added logic to check for null objects within the initialization class when performing Auto-provisioning.
Engineering 70928, 64941, 68481 If a virtual circuit once rode a bandwidth circuit, but has since been redesigned to ride a different one, when a disconnect order is put in for the original bandwidth circuit, the previous assignment is still seen by the validation and the order cannot complete. The validation has been changed so that only bandwidth circuits pending and current issues are looked at when verifying all assignments have removed. Any assignments from previous or overridden issues will no longer be taken into account. This will allow a bandwidth circuit to be disconnected after it's virtual circuits have been moved to another circuit.
Engineering 71388 On a Transfer order, the IC field of the CLR (for CLS ckts) is being correctly updated with the new Customer Account name after a successful Transfer order, but the IC/Cust field in the CLR Print Preview does NOT get updated.
When the new issue is created on Due Date, also update the customer information for the new order.
Engineering 71660 The copy design functionality does not make facility or equipment assignments for disconnected connections, even though the blocks appear on the design lines tab.
The copy design functionality is not allowed if the destination connection is disconnected. This is because disconnected connections cannot have active assignments; therefore, nothing but the blocks would be copied. Using the copy design functionality while the source connection is still in pending disconnect will copy its assignments.
Engineering 71783 In Connection Hierarchy, when querying for a Facility circuit that has a Physical Connection assigned to it, you will not be able to drill down into the Physical Connection to see any Virtual Connections allocated to the Physical Connection. You will now be able to drive down into a Physical Connection to see any Virtual Connections allocated to it.
Engineering 71846 User is unable to disassociate bandwidths from the network design. All of the virtuals riding the bandwidth have been redesigned and no longer appear in connection hierarchy. But when they try to unassociate in the network, they get a message saying that the circuit has been provisioned to. Since this is not an extension, they cannot manually delete the network association in the BW design. When validating whether the bandwidth has been provisioned check the design with issue status "Current" or "Pending" only and exclude disconnected and canceled circuits
Engineering 71909 Customer reports that the year is not visible on the connection Notes window. The column is now wide enough to display the entire date.
Engineering 71919 The Misc. Info section of a circuit design is cut off. To see the entire design, the user must Hide the Navbar, then reduce the size of the tool area using the bar. If the tool area were made smaller but still readable, the user would not have to move this bar. The width of multi-line column headings were appropriately reduced, providing a more appropriate layout that now shows almost all of the information in all of the columns. When necessary the navigation bar can be closed and all the data in all the columns will be displayed.
Engineering 71925 When you assign or remove a equipment block from a facility, the user is not always asked if they would like to reconcile the child circuits. When you assign or remove an equipment block from a facility, the user will be asked if they would like to reconcile the child circuits.
Engineering 71962 If a user is sitting in the middle of a block on the design and adds Foreign Info, the line is inserted in the middle of the block, if they do the same for Misc Info, it is inserted below the line group. The foreign info block is now added below the selected block. The user still has the ability to move the block inside of another block and embed it.
Engineering 71971 Customer getting booted from system during CANCEL CHANGE process under RID task. Fixed the SQL that caused the error. User needs to Cancel Change again, so that the activity indicator will be set to 'Cancel', circuit status kept in service. Now the task can be completed.
Engineering 71980 DLCI information does not appear for all circuits on the Connection Hierarchy window. Corrected the SQL that builds the allocations. The allocations now display correctly in the Connection Hierarchy treeview.
Engineering 71986 Cascading reconcile job cannot get to the background processor Error was being encountered when the "Default Background Server" preference was set to "FIRST AVAILABLE" and the "Suppress Confirm Background Server Window" preference was set to 'Y'. Modified Background Processor logic to correctly handle this preference combination.
Engineering 71992 When dragging and dropping an available position in the Group Assignment window and the available position is dropped in the circuit list window area with no row, Error Number 6 message will display then application terminates. When dragging and dropping an available position in the Group Assignment window and the available position is dropped in the circuit list window area with no row, error message will not display.
Engineering 72035 When you perform a search on the Connection Design window for a specific end user location the search returns more circuits than the location selected. The new changes will retrieve correctly in the Connection Design window for a specific end user location.
Engineering 72063 On the Connection Design Query window if you search for an element name it works the first time. If you do not close the window and modify the search to search for a different element name you get a No Rows Returned message when there are rows that should be displayed. Now the Connection Design Query by Element Name is working properly.
Engineering 72181 An Oracle error was received while doing a Group Assign on 5 facility circuits when the rate code of the equipment is N/A. The problem occurred because the next port available for group assign was cross-connected to an empty placeholder. The cross-connect logic in the stored procedure has been changed to account for an empty placeholder in the cross-connect chain. The user will now be able to group assign this particular scenario without getting an error. The other solution is for the user to install an appropriate card in the placeholder's mounting position.
Engineering 72361 When a query is done from the Connection References Search window and a like is used, the records returned are not being limited to the search criteria. Also, items in the Type drop-down on the search window do not match items in the drop down when creating a cross reference, Now the search results are limited by the search criteria and the items in the Type drop- down match the items in the drop down when creating a cross reference.
Engineering 72363 When one connection reference is deleted from the design, all connection references are being removed. The problem was that, when the customer responded that he/she wanted to delete the underlying connection reference, the software was deleting all the connection references for the circuit rather than just the one on the design. Now, the software will delete only the connection reference that is highlighted on the design.
Engineering 72430 Some connection IDs are not showing for in service connections on the customer profile. There were some facility circuits which were showing blank IDs in the customer profile. Changed sql to use the connection id from the circuit table if the serv_item_desc is blank.
Engineering 72484 Issue updating information on the Circuit table, but not updating the LAST_MODIFIED_DATE. The last_modified_userid and last_ modified_ date will be updated when updating the circuit status.
Engineering 72487 Oracle Error whenever we use the Connection Hierarchy query window. We're trying to query for a Vendor Circuit ID, but when we enter the value and click 'OK', we receive the error below. The user will now be able to query for and retrieve Leased Circuits from the Connection Hierarchy query window for Leased Circuits without receiving a database error message. The Leased Circuits will be retrieved successfully.
Engineering 72502 Received a prompt that a cascade reconcile would occur after disconnecting an equipment block from the DLR. The reconcile does not occur though when the design is saved. Cascade reconcile was not getting kicked off on a save if the circuit only had one issue. Added code to handle the case where only one issue exists for the given circuit. As a result, cascade reconcile will be initiated when the design is saved.
Engineering 72600 If a change order for a NGN circuit is entered, the DLRD task cannot be completed if the circuit status with order is DLR issued. The DLRD task for a NGN circuit change order can be completed if the circuit status is set to DLR Issued.
Engineering Internal CR# 32184 After making a change that results in a mass reconciliation and choosing to run the reconciliation in the background, the user is presented with the Design Print Specifications window. This window displays the printer where reports will be sent, and defaults to the user's default printer The 'Printer...' button on this window presents a list of printers set up on the user's PC and the user should be able to select a printer other than their default printer to send any reports to. When a different printer is selected, the background printer is not changing on the Design Print Specifications window. Made Changes, similar to that was handled in the connection design print. Now the user can select his desirable printer.
Engineering Internal CR# 32983 There is a known issue that when a new node is inserted into a Unidirectional Path Switched Ring without TSI and that ring contains child circuits, the child circuits are reconciled but the CLR does not update correctly. Generally, when assigning to a UPSR without TSI enabled, assignments are made to the two drop nodes in both directions so that two card or enabled port assignments display for each node. When the new node is inserted and the child circuits are reconciled, one of the enabled port assignments is removed from each direction and will not be displayed on the CLR; however, the enabled port assignments are being updated in the database. Made a code change in the reconcile code to detect the affected child circuits when a non-TSI path-switched ring is involved. In the screenshots there is a question about whether or not the pass thru nodes should appear on the design lines. The answer is no. For path-switched non-TSI rings the software only places the drop nodes on the design and displays the channel. The reason is because the circuit is riding the same channel on each segment and therefore only one is needed for display on the the design. This applies to the schematic view also as it is derived directly from the design lines.
Engineering Internal CR# 34755 Null pointer exception appears at the top of the Network Element Types search page when you first open it. You can still do the search. The null pointer exception will no longer show on the top of the page. Also, the list will no longer automatically retrieve when returning from the maintenance page. The search criteria for the last search so the user can hit the search button again if they want to re-retrieve.
Engineering Internal CR# 37736 Mass DLR Reconcile needs to be corrected to only exclude blocks whose underlying assignments have actually been disconnected or unassigned. This means that a pending disconnect block should still be reconciled. Mass DLR Reconcile will include all pending disconnected assignment blocks and exclude all disconnected assignment blocks.
Engineering Work Order Internal CR# 33181 When using the Engineering Work Order, rules and behavior for user data, and a default work plan, the rules does not get executed when the order is created. The reason is that the rule executes when the plan is created, but the user data can not be entered until after the initial save of the order. To get the rule to execute the user data needed to be input and the plan regenerated. This enhancement changes how user data works with EWO in the following way:

1. The user data is now entered, viewed and changed on the maintain engineering work order window. This window is presented when the user wants to create a new engineering work order, or when the user select edit from the engineering work order summary field. The maintain engineering work order window will enforce all the rules of user data including mandatory field checking, content checking, and valid values.
2. When a new engineering work order is saved by pressing save and close, the user data will be saved. If rules and behaviors are defined for an EWO, when the default plan is generated and the rule is true, the actions defined by the rule and behavior will occur.
2. The change engineering work order link has been removed from the engineering work order summary page. To change user data for an engineering work order use the edit option located by the Work Order information title on the EWO Summary page.
Equipment 71856 Position Mapping not being displayed when opening from the equipment install screen

Position Mapping information will be displayed when opening from the equipment install screen.
Equipment 71877 Circuits are showing on ports where they should have been disconnected. CR35050.sql cleans up bad data. When a circuit is disconnected, there should not be data in asap.port_address table with the circuit assigned to or mapped to a port address.
Equipment 71941 The customer has approximately 250 instances of a card part number which has incorrect port addresses within the concatenated node address. This cannot be alleviated by changing the card specs. This means the customer would have to manually modify each instance to affect the concatenated node address. It is not known where the STM16 card port address is coming from in the installed instance. The SQL that calculates the node address has been corrected by another CR. However if user noticed the node address are not updated correctly after they modified the equipment specification. Following steps can clean up the data:

1. Clean up the equipment which can build the node address longer than 30.
one example below
rack node address as: 008-001
shelf node address as: 007 slot LEA
card node address as: 001-002
the top node address TX
enabled port address and enabled port address
It can be 008-001-007-LEA-001-002-TX-16-63. This is more than 30.
2. Since some of the node address might have been built up wrong before they modified the node address, they need to clean up the equipment spec node address to null, EVERY LEVEL. This will clean up all the bad node addresses.
3. Add node address on the top level, add all the sequence as before for the enabled ports as before.
Equipment 71978 After making changes to an existing SPEC, the changes are saved and the cursor stays on the SPEC but the window jumps to the top. If you need to open the changed SPEC back up you have to scroll down to the SPEC again. You now do not need to scroll back down to the SPEC again after changing any row.
Equipment 71985 An Oracle error occurs when trying to: A) add a card on a relay rack outside of a shelf B) move a shelf to another location or C) add a new shelf inside a relay rack. It appears that after hitting okay, the equipment is installed/moved correctly, but it's unknown what underlying problems might occur because of the error. Corrected code that was causing the error. The error involved SQL that verifies that there is enough room for the equipment being added or moved. Validation now occurs without error.
Equipment 72161 The wrong information appears on the design lines after changes have been made to the ring the circuit rides. The correct information will appear on the design lines after changes have been made to the ring the circuit rides. For example, a circuit assigned to the A path and the B path of a Line-Switched ring, when inserting or deleting nodes on the network, the affected assignment block will be updated correctly to show the correct network information.
Equipment 72637 Execute the getHardwiredCrossConnects_v2 and/or getSoftwareCrossConnects_v2 API operations and the transaction objects are not getting destroyed thus leaving the database connections open.
Added the Destroy transaction call for following API operations.
getHardwiredCrossConnects_v2
getSoftwareCrossConnects_v2
getEquipInstallQueryValidValues_v2
getEquipSpecQueryValidValues_v2
ISR 72375 If an order is opened using the right-click Service Request wizard off the Queue Manager, and that order is later refreshed, a slew of orders are returned instead of just the retrieve order. Now the refresh will bring back one order.
ISR Internal CR# 34635 On a new ISR Trunk Change order, if a new trunk circuit is added, it cannot be deleted unless you exit the order and open it again. On attempting the delete, an error message appears indicating that the delete is not allowed because tasks have been generated, even though no tasks have been generated. Fixed code to not display the error message when attempting delete of trunk circuit on a new ISR change order.
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 a 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.
PSR 63712 User receives MPO Desired Due Date Alert when trying to Due Date complete several Supp Canceled MPO Change Orders. The MPO Desired Due Date Alert was generated by the application because these Supp Canceled MPO Change Orders had a Desired Due Date that was greater than the New MPO Order that these pending service items were copied from and also the New MPO orders was still in an Open status. To change this design logic the MPO code that triggers the MPO Desired Due Date Alert was modified to ignore Supp Canceled MPO orders in which a User is trying to complete the Due Date Task. Therefore, a User should be able to Due Date complete Supp Canceled MPO Change Orders that have service items that still exist with a New Activity or in a Pending status on other Open/Non Due Date completed Orders.
PSR 63821 When querying for numbers to assign to a ported out product in PSR, the system should not bring back anything that is not local company-owned. Changed logic on the Assign Telephone Numbers window so that if it is opened for a global, ported number product, then the user will only be able to assign a Locally Owned or Foreign number.
PSR 65929 Error Message received when trying to Disconnect Order with hunt groups when one of the numbers on the hunt group was already disconnected on a previous order (prior to the implementation of new validation logic). The validation was modified so it would not pick up a line that was already disconnected or cancelled when searching for lines that are not on the order but are part of a hunt group being disconnected.
PSR 70014 When a location has been modified and the location is selected to open in a PSR order , a null pointer exception will display. When a location has been modified and the location is selected to open in a PSR order , a null pointer exception will not display. The location information will display. Based on what information has been changed for the location, the application will create a new row for the location and set it as active. The primary indicator is not used anymore to get the current address but the logic was still using the primary indicator.
PSR 70280 Customer reports that when they attempted to Supp Cancel a PSR with a completed DLRD task, they reopened the DLRD task and clicked Canc Chg for the circuit in question, but the related cable pair still shows as In Service and cannot be reused. This is a Prod Fix SQL that Cancels circuits where the service item has been canceled. The code in PSR Due Date has already been fixed. This CR just cleans up some bad data.
PSR 70280 When trying to Due Date complete a supp canceled PSR order for a New physical connection, an oracle error occurs. The error is: ORA-02292: integrity constraint (ASAP.FK_DE_NS_RE_CA_VA__NS_ CO_RE_CA) violated - child record found The reason the errors occurs is because the New Physical Connection has been allocated to a Virtual Connection that is already In Service or on another order. In this case, we do not want to delete the Physical Connection at due date completion of its supp canceled order so that it will still appear on the GLR for history purposes.
PSR 70381 When updating the address for an End User Location, the user receives a database error telling them that duplicate rows exist on the eul_lso table. This error occurs when the end user location being updated has the data switch and the tn switch populated. The logic tried to update the data switch row with the tn switch data. This did not work because the tn switch data was already on a different row. This violated the database constraint of the primary key for the eul_lso table.
PSR 70476 User is unable to complete a Due Date Task for PSR order. Application generates a unique constraint database error in the of_jack_info function of PSR Due Date. This issue was corrected by a minor modification to a function in the PSR Due Date stored procedure that processes jack information. The modification involved updating a sequence that was referenced when the application attempted to insert a row into the ASAP.SI_JACK_INFO table.

With the correction to the sequence, this error should no longer occur and our client's users should be able to successfully Due Date complete their PSR orders without encountering the unique constraint database in the of_jack_info function.
PSR 70564 Set the "Require Billing Activation Date for PSR on DD" preference and the behavior for the creation of a PSR via GUI and API not consistent for the Bill Activation Date. The API has been corrected to be consistent with the GUI. If the preference is ON, the date is not auto-populated on the PSR. If the preference is OFF, the date is auto-populated to match the Desired Due Date.
PSR 71124 Unable to query orders based off of the last modified date from the Service Request Search window. You can now query orders off of the last modified date.
PSR 71364 Customer is seeing 'B' displayed in the Orders Pending Due Date Completion window. This is not very intuitive and the customer does not know what the B stands for. Changed the decode statement in the datawindow so that 'Restore' is displayed.
PSR 71428 When choosing Copy Attributes in the ordering dialog, one of the CA's is not saving correctly. Because the CA isn't saving, you get an error when you click the Finish button.
When Choosing Copy Attributes in the ordering dialogue the CA's will save correctly.
PSR 71467 Customer reports that the Services window in Customer Profile does not display the products in the correct numerical order. Products in the Customer Profile Services window will display products in correct numerical order.
PSR 71504 A space was missing between two pieces of data. Customer reports that some TNs are cut off in Print Preview. The missing space was added. The column was widened.
PSR 71524 User can create Duplicate short names for Network systems. Validation has been added that checks for Network System Short Name uniqueness when creating the Network System on a PSR order.
PSR 71548 When using a transfer order to transfer FRATM products, the CA's are not copying over to the design. They appear on the design initially during the GLR_DSGN task, but they disappear after DD of the transfer order. The Custom Attributes will now copy from the previous issue to the new issue generated by the transfer order. This fix only applies to physical connections.
PSR 71571 Error in PSR Due Date. Bandwidth Circuit not found. Due date proc was changed. The serv_item status was already disconnected and should not have been included in the items_cursor.
PSR 71594 YP Heading Verb and Code field sizes not correct. Changed the datawindow so that

YP Header Verb now allows 200 characters to be entered.

YP Header Code only allows 8 characters
PSR 71599 Execute importPSR api operation for a product and try to import the PSROrderItemPrice2 structure price information and receive the following error:
[0] Field: code = 39990 [0] Field: reason = Miscellaneous Error: SP_PSRAPI_UPDATE_PRICE: Not a Valid Price. [1] Field: code = 30766 [1] Field: reason = Unable to process item LD US TO INTERNATIONAL (specId 4409, product group 1) due to errors listed.
The error message is valid, but for customers that use Recurring and Non-Recurring prices. This customer only has Usage prices. The message is not applicable and the code is bypassed if the customer does not use Recurring or Non-Recurring prices.
PSR 71634 Errors received when disconnecting TN items. Previously disconnected items appearing on the PSR. Changed the sp_clec_so_del_item proc so that items that are already disconnected or canceled are not retrieved. Because these items are retrieved, they are getting reset.
PSR 71652 When you create a change PSR order to change an InService MPT telephone number to ALT and an ALT to MPTN, the activity code does not get updated to change correctly.
When the TN is changed from ALT to MPTN or MPTN to ALT and the TN is In Service, the activity code will be chnaged from 'I' to 'C'.
PSR 71652 When you create a change PSR order to change an InService MPT telephone number to ALT and an ALT to MPTN, the activity code does not get updated to change correctly.
When the TN is changed from ALT to MPTN or MPTN to ALT and the TN is In Service, the activity code will be chnaged from 'I' to 'C'.
PSR 71688 The Address Change Impact window does not make it clear which TNs are tied to which location being impacted, and the text of the window is a little confusing. Additionally, it would be helpful if the End User Location Maintenance window offered a way to tell which customer accounts the location has been use on, to help identify situations where a location has been tied to the wrong customer account. The Address Change Impact window has been modified in several ways:
1. The text of the window has been rewritten somewhat to make it clearer that the decision being made concerns the way in which address changes will be applied.
2. The address as it currently exists (prior to the changes you are about to make) is displayed on the window.
3. E911 impacts (telephone numbers) now include the telephone number suffix, the status, and the location name.

The End User Location Maintenance window was changed to include a new tab called "Customer Accounts". This tab will show each customer account the location has been used with on an order, the customer account number, and the status of the customer account.
PSR 71791 Add User Data capability to the customer account module. A new User Data toolbar option is now available while on the customer account window. In addition, a Customer Account User Data link appears on the Customer Profile window. Customer Account User Data fields can be defined via the User Data menu in Infrastructure the same way it is done for other modules. The new user data window can also be secured like other windows.

Note: Prodfix SQL CR33683.sql must be run to create the shell user data table before any of this will work.
PSR 71808 When the user Supp Cancels an Order that is in an MPO scenario, and other orders are stacked up after it, the user does not receive a warning message telling them there are other open orders.
Modified application so Supp Cancel Alert window displays when Supp Cancel is performed on order with items that exist on another open order. The alert window displays each item on another order along with the other order number(s) and their activity code and due date. After alert window displays, the user has the option to cancel or continue with the Supp Cancel.
PSR 71864 Addresses are not being updated with correct information. Changed the code so that the update to customer address occurs.
PSR 71899 User is not able to double click to select the customer from the customer account search screen for a new PSR. Double clicking one of the results rows will select that customer account and return with it.
PSR 71907 Customer reports that the PSR Supp New Due Date function is not updating properly. Updated changes are not reflected on the Order Info tab. Modified the logic to re-retrieve the Order Info after the processing of the supp due date.
PSR 71918 User is getting dropped from the system after attempting to recall an unavailable telephone number. This problem occurred when attempting to recall an international telephone number. Corrected logic error that was causing system to crash. If attempting to recall an UNAVAILABLE telephone number, user now receives error message "The number is not available for recall".
PSR 72003 In the Service Request Search window, users with a 'scroll' mouse can move the form underneath the 'Search By' dropdown on the 'Criteria' tab to an unreadable position. This happens for both forms (Service Request and Telephone Number). You can also click on the 'Status' icon and make it disappear by scrolling the mouse wheel. The datawindows had a lot of unnecessary space which caused the scrolling. The space was eliminated.
PSR 72134 The application will not allow you to add a new service location. Another code change somehow affected this functionality. The original code was restored and tweaked so that the problem is resolved.
PSR 72190 Customer reports that when they query for TNs they type in the NPA, but the NXX field remains grayed out until they click on the Line field. Now, the NXX field is activated immediately after they type in the
NPA.

PSR 72190 Customer reports that when they query for TNs they type in the NPA, but the NXX field remains grayed out until they click on the Line field. Now, the NXX field is activated immediately after they type in the
NPA.

PSR 72263 Customer reports that they are unable to use the Set Criteria functionality when searching for a PSR using the Telephone Number selection criteria. When they attempt to use Set Criteria for the Line field, the information is incorrectly populated in the Order Number field.

Customer reports that this works properly in 4.5.13.x, but does not work in 5.2.10 and above.
The fact that the Set Criteria option was enabled on TN criteria fields was actually an oversight. These fields are driven by structure formats, and only accept the values defined in the format. The criteria option has been disabled on these fields to be consistent with the rest of the application.
PSR 72463 In the M6 stream, account name was added to the header. When the order first goes to View Only, the words "View Only" appear after the account name. On long accounts, they are not visible. If the order is later retrieved, the words "View Only" are placed before the account name making them visible for all order types. Now the "View Only" text will appear before the account name immediately after assigning the provisioning plan.
PSR 72504 Once the Title of Lineage/Address 1 (Dr, Mr, Mrs, etc) column is populated, it cannot be removed. A 'None' option was added to the Lineage/Address column. Selecting it will remove the currently selected value.
PSR 72732 On a PSR order, after you assign an authorization code to Calling Card, it does not display on the service item for that calling card. Authorization Code will now be displayed in the service item description for the service item, so it will now display in the treeview next to the service item. If multiple authorization codes exist then it will display the first one off of the authorization tab and it will have a ",..." to signify that multiple authorization codes exist.
PSR Internal CR# 32748 When adding a telephone number to a LINE that has a child LINEDIR item, the Main and Listing TN for the LINEDIR are not defaulting. Now TN is defaulting to LINEDIR
Technical Framework 72044 When a user adds a custom link to a group when customizing their navbar to open a file that needs another program, the navbar went away completely and when they try to add a group to try to correct it, a java exception occurs. Now user can add the custom link with double quotes.
Technical Framework 72088 If the user sets their pc to use large fonts they are not able to see all of the necessary information within the application.
This is partially fixed. A random retest of windows indicates the large font (at 110%) allows the user to access the windows.
Technical Framework 72163 Customer reports the following error when attempting to change the user password through Preferences:

A database error has occurred. The error message is: ORA-01031: insufficient privileges.

The SQL statement that caused this error is: ALTER USER CRUTCHFJ IDENTIFIED BY FURN2SH

The user got out then got back in and successfully changed their password, but when accessing Preferences, they got the following error eight times before they were able to access preferences:

You have entered an invalid User ID and Password combination.

ORA-01017: invalid username/password; login denied.
Modified code to temporarily grant and then revoke the appropriate roles necessary for the user to change their password.
Technical Framework Internal CR# 36120 Needed an easy way to download the prodfixsql to a windows machine. Added a new link to the ZAC homepage that will let users download prodfixsql to their pc.
Technical Framework Internal CR# 36268 Certain roles were defaulted in the database that, under certain conditions, might produce security concerns. The default role was removed from the database and roles are explicitly granted at the time a connection is made. In this way, the admin_role is no longer assigned to every connection.
Trouble 71009 The active ticket queue takes too long to open. A join was removed from the Active Ticket Queue sql and was replaced by a stored function call. 

Also, a prod fix sql is being supplied with this CR. The prod fix sql will reset the version on the trouble views -- so when the user accesses the Active Ticket Queue, the views will be upgraded with the new SQL.
Trouble 71880 Notes on the parent event log of a child ticket report are not displayed chronologically. Notes now appear chronologically on the parent event log of a child ticket report.
Trouble 72225 Trouble description notes are being deleted Now the trouble description will not delete when closing the window by using 'X' button.
Trouble 72447 Notes not appearing in the log view Now copy and paste functionality works fine
Utilities 70988 The LERG utility is placing "+" in the NXX column on the NPA_NXX table thus causing downstream ORA-01722: invalid number errors. Fixed the import to the staging tables so that it will not load the invalid rows that contain a "+" for the NXX value.

Also provided a prodfixsql script to remove the "+" values from the database that already existed.
Utilities 72427 Customer reports the following error when loading LERG data for 4/2004:

Location and Routing Gateway error importing BRHMALOUDS0: No
Network Areas were found for Rate Center Abbrev GARDENDALE. Verify
that Network Areas were loaded correctly.

The LERG load stops at this point.
The rate center network area 'GARDENDALE - AL' existed in the database, but it did not have a rate center abbreviation populated in the database. When the import was adding the rate centers, it updated this row, but it did not contain the abbreviation in the update. This has been fixed to update the abbreviation as well. This column is needed when importing the 'BRHMALOUDS0' and 'ANTNAL070MD' locations, and because it was not populated, the error was logged. With the fix in place to populate the abbreviation if it did not previously exist, those locations will import properly.
Work Management 65323 The generateAndSaveTasks WM API method is allowing the provisioning plan to be assigned twice to a document number thus causing data corruption on the TASK table and the MetaSolv GUI to be unable to open the Tasks for that PSR order.
Modified the internal logic of the generateAndSaveTasks WM API method to lock the appropriate row (on serv_req) while performing the save tasks process. This prevents two concurrent requests for the same document number to duplicate the task data.
Work Management 70145 Performance of the Server Log List window in Work Management is slow. Many records in the log contain a 'Description' of 'Unable to obtain task with lock since task changed, task: documentNumber=XXXXXX,taskNumber= XXXXXXX'. User is unsure what this 'Description' message means. The system task server will not log the messages like

"Unable to obtain task with lock since task changed, task: documentNumber=XXXXXX,taskNumber= XXXXXXX".
and
"Transfering task to exception queue, task:XXXXXXXX"

This makes sure that there aren't any unnecessary rows in the server_log table.

Work Management 70145 The application hangs in the Server Log List window. When you highlight several records in the Server Log List window, the application hangs. This appears to happen only after you sort a column, scroll down the window and then highlight the records. When the application hangs, the tbs.exe process consumes all CPU resources as seen in the Windows Task Manager. Once this has happened, you must end the process.
When opening the window for the first time with a large number of data, it will be slow. The user can right-click and purge all the rows. This process should take 1-2 min.
From this point on, the window should perform well, since the unnecessary rows aren't written to the server_log table anymore which is fixed under a different IR.

The new functionality added to the right click menu option is 'Clear All', 'Purge All' and
'Restore All'

The datawindow control on the window couldn't handle large number of rows and so the shift click option is disabled. Instead the user can control click and select multiple rows.
Work Management 71135 When you execute the generateAndSaveTasks WM API method for a PSR order that does not have a DD, the API call hangs and does not return failed notification. Modified the internal logic of the generateAndSaveTasks WM API to return an exception if the Desired Due Date has not been set and the Provisioning Plan that is being used is not a Pre-Order Provisioning Plan.
Work Management 71247 DD task changed from Backward Dating Indicator to Forward Dating Indicator. The DD task Indicator will not change from Backward Dating Indicator to Forward Dating Indicator when a new task is added to the provisioning plan.
Work Management 71512 The value '?????????' appears in the Work Queue dropdown list of the task maintenance window. This behavior occurs when assigning work queues for tasks by clicking on the 'Queues' button of the task maintenance window. This happen when the size of the work queue is very large. Now the correct Work Queue value sets in the work queue field
Work Management 71858 Not able to complete disconnect order D36961 for 672 trunks Order N34569 that put the trunk back in service was not picked up in the query because it had never been supped. It was instead picking up order D28206 which disconnected the trunks which confused the DD validation. The SQL is now fixed so that it picks up the correct previous order.
Work Management 71973 The notes field on the Supp History tab in Work Queue Manager is used more often than the supp-reason field and will need to be looked at often. It has been requested that we try to modify that window to minimize the amount of scrolling necessary when text is entered in the notes section. The notes field in Supp History tab in Work Queue Manager is made visible completely.
Work Management 72479 Using Windows XP, the drop-down does not work correctly when trying to add a Why Miss code. Now the drop-down datawindows work fine in both windows 2000 and windows XP.
Work Management 72511 When you Supp cancel a PSR order that has been provisioned with tasks that have gateway events, there is no way to "Bypass" ("Not Require") the gateway event(s). This functionality exists at the time you provision the order by clicking on the Gateway Event tab and right mouse click on the gateway event to select "Not Require". This same functionality should exist when you Supp cancel the order. Also, if you have the gateway events set to AutoSignal set to "Ready", then as soon as the WM windows is displayed during the PSR Supp cancel dialog, all tasks go to "Ready" thus all gateway events go to "Sending" so this does not even allow for a manual solution to "Not Require" or "Bypass" the gateway event.
Two new preferences have been added for this CR and can be accessed from the Work Management -> Work Queue Management section:

1) Bypass Pending Gateway Events on a Process Supp Cancel - if this is set to 'Y', then when supp canceling an order, all of the Gateway Events in 'Pending' status will be updated to 'Bypassed'. This functionality will work for ISR and PSR.

2) Send System Tasks to the Exception Queue on a Process Supp Cancel - if this is set to 'Y', when supp canceling an order, all of the System Tasks will be transferred to the Exception work queue. This functionality will work for ISR and PSR.

Note that if the first task contains a gateway event, upon initial task generation, that task will go into a 'Ready' status, and its Gateway Event will go into a 'Sending' status. If this order is supp cancelled before that task is completed, then that Gateway Event will not be bypassed. Only Gateway Events with a status of 'Pending' will be bypassed.
Work Management 72541 Rules and Behaviors: User data selection list showing database values instead of dropdown values Now when you click the dropdown for the IXC_Carrier2 field, the dropdown lists all values that are set up in the User Data Categories window.
Work Management 9999 DD task completion validation is slow. The delay is between the time right-click the DD task in the queue manager and choose complete task to the time the task completion window opens.
Improved performance for completing DD tasks with large numbers of circuits.

 

MSS 6.0.3

Component Issue ID Problem Resolution
ASR 74064 Serv Req Detail for an ASR MSL order prompts for Location Type even though the information is on the order and the field is disabled. Now the SALI maintenance window is shown as view-only with all the information retrieved.
ASR 74453 User gets a validation error after adding USOCs to Bill because the USOC Amount field is set to .00. The validation error will not occur for the USOC Amount.
ASR 74456 Unable to delete and rebuild the Bill Prep record. Corrected the object that retrieves the billing circuit information for deletion of CABS bill prep data. The datawindow is not used for updates so the update specification was removed. Simplified the SQL statement used in that datawindow.
DB 73321 When creating a PSR, it takes 14 seconds after you click the Finish button to get the window that prompts you to click Yes or No to assign a provisioning plan.

When you click Yes to assign a provisioning plan, it takes 19 seconds to get to the Provisioning Plan Assignment window.
The code that creates the Provisioning Plan Assignment window has been modified. The SQL that is executed before this window appears has been tuned and the duplicate SQL has been removed. The window displays in less than five seconds.
DB 73322 When you click the Trunk Groups link, it takes at least 10 seconds to retrieve the Trunk Group Search window. The performance issues on the Trunk Group Search window are caused by the large amount of Trunk Group User Data columns setup. The User Data object that creates the User Data visual columns at run time has been optimized. All SQL needed to populate the User Data dropdowns will occur in a Bundle and duplicate pieces of SQL will only be executed once. The Trunk Group Search window will appear in under 5 seconds.
DB 73413 There is a performance issue in which it takes 11 minutes to complete a Supp Cancel for an In Progress PSR with the CKTID task completed. Optimized SQL was added to check if a Multiple Pending(MPO) situation exists on the Order. If there is no MPO then 2 complicated pieces of SQLwill not be run. These pieces of SQL are specific to the MPO situations. The time to finish the Supp Cancel process is reduced to under 10 seconds.
DB 73553 There is a performance issue in Equipment Assignment in Connection Design. The equipment window is taking 30-plus seconds to open. Performance when expanding a piece of equipment in Equipment Inventory via the Connection Summary is improved.
Engineering 68699 When a user goes into the cross connect report and clicks the magnifying glass for equipment type, it takes over 2 minutes to bring back any data. Also when the user clicks the magnifying glass for relay racks, it takes over 2 minutes to bring back any data The sql queries performing the above operations were tuned. An index hint is now used on the equipment table. The above operations are much faster now.
Engineering 70799 Available options, (for example, Reconcile, Pos Map, and so on), were visible no matter which tab you selected in previous versions. This has been resolved by adding the options as menu items under the 'Options' menu.
Engineering 70984 Customer is trying to reuse the TCIC that are on a Disconnect Order. They do not want to DD complete the disconnect order before the reuse the TCIC on the new add order. The application will not allow the reuse of TCIC's until the disconnect order is DD complete. A new preference has been added,"Method of TCIC validation". When PointCode is chosen, all TCIC validation is performed using only the point codes. The second option, PointCode/Validation, performs all TCIC validation based on the point codes as well as the A and Z location of the trunk group. If at least one location of the new trunk group is different from the locations on the pending disconnect trunk group, the TCICs can be reused.
Engineering 71778 Auto Building STS1 to DS3 to DS1 for SONET OC192 rings is taking a few hours in some rings. Also opening some networks takes a really long time. The performance when opening and autobuilding large networks has been improved.
Engineering 71925 When you assign or remove an equipment block from a facility, the user is not always prompted to reconcile the child circuits. When you assign or remove an equipment block from a facility, you will be prompted to reconcile the child circuits.
Engineering 71946 The location information on the printout of the Service Request Details for a circuit is blank. Now the location information for a facility circuit is displayed in the Circuits section of the Service Request Detail report.
Engineering 71953 It takes too long to delete and save a node in 6.0. Performance for deleting and saving a node has been improved.
Engineering 72038 The application allows printing of a BLANK PAGE when deselecting the defaulted checkmarks on the design lines and using PRINT CLR/DLR instead. Also, an error message appears when they preview the CLR. Error message when previewing a CLR was fixed in release 6.0.2. The user will get a message before proceeding to print if no printable lines were selected. You can see the basic circuit information as well if you deselect all the printable lines and preview with the option 'Printable Lines'.
Engineering 72062 Users are able to create two circuit IDs for the same circuit spot on an order in the database if two users open the same circuit at the same time.  You cannot create two circuit IDs for the same circuit using two sessions.
Engineering 72343 When adding a large number of trunks to a record activity order, the application takes approximately four times longer to process than it did in version 5.2. The reason for the decrease in performance is the introduction of the n-tier framework. When adding a large number of trunks to a record activity order, the application will have processing times closer to the 5.2 version. The reason for the decrease in performance is the introduction of the n-tier framework. The resolution required SQL bundling, and removing unnecessary database SQL calls.
Engineering 72364 There are some performance problems with the cross connect report.

1. If a 11-character CLLI is used, hitting the magnifying glass to pull up relay rack information takes a long time. If a 8-character CLLI is used, this search is much faster.

2. If the user selects multiple relay racks and then hits OK to see the report, if they try to save or print the report it takes a long time for the save or print window to open.
The first problem is fixed under Issue ID 68699. For the second problem, save or print the Cross Connect Report performance improved reasonably.
Engineering 73191 When searching by TGN in Connection Design search, user searches (select criteria) by TGN, and receives TGN result. User returns to the search window, clicks the Clear button, then selects a facility and a valid Network Location. Search does not return any records. Now the user can modify a search in Connection Design query when additional search fields have been used.
Engineering 73356 The status field on the Trunk Group Information window does not have a scrollbar in the drop-down. Users are unable to see a complete list of statuses. The status field on the Trunk Group Information window will now have a scrollbar and the user can view all the available statuses.
Engineering 73357 Create an order for a T3. Work the order through RID and completed RID, but not DD. Create an order to add 3 T1s to the T3. Assign the T1s to the T3, but leave them pending and do not complete RID. Supplement the T3 order to cancel and reopen RID. In RID, when you select to Cancel Change the T3, you receive a notice that there are underlying facilities riding the T3. The circuit cancellation process appears to continue and Cascading Reconcile is triggered. At this point there is an error and the T3 order is put in Problem status. In this scenario, processing will stop after the message stating that underlying riders exist. A second message will be displayed stating that the circuit will be put in a Problem status.
Engineering 73381 When running a group assign using the background processor, and the Service Request Connections window is not refreshed, when the background job ends, the circuit statuses will not get updated correctly when marking as RID or DLR issued from the Print window. When running a group assign using the background processor, and the Service Request Connections window is not refreshed when the background job ends, the circuit statuses will get updated correctly when marking as RID or DLR issued from the Print window.
Engineering 73389 When the user prints reservations, any data appearing on a line beyond a certain limit is truncated and not printed at all. When the user prints reservations, the data appearing up the right margin will be printed.
Engineering 73417 Queries on the Connection Reference window are returning records that do not match the query criteria. Already fixed with IR 72361in release 6.0.2 .
Engineering 73435 Original design contact information is being deleted and updated with the field techs design preference. If the Connection Design window is read-only, then the design contact information shows the original design contact information.
Engineering 73442 When performing the Group Print for 672 ordered trunks, the application appears to hang. You have to Ctrl-Alt-Del to get out of it. Combined code to loop all of the trunks, and also modified certain embedded SQLs to reduce the traffic to the server. Now, the Print window will display in 1-2 minutes after clicking Group Print.
Engineering 73647 When embedding a SONET network in a Network System using OPTICAL/TDM Network template, you receive the error, "Unable to Update Drawing with SONET/SDH Connections", then another error saying "Error retrieving SONET network system". The problem was caused because the SONET that the user was trying to embed had shared nodes. Previously, shared nodes were only allowed if the SONET network was a point-to-point or if it was a ring and was virtual, dual-homed, or subtended. The code that was causing the problem was only retrieving shared nodes in these cases and when it tried to update the canvas with the appropriate drawing, it couldn't find the shared nodes to do so. Now, any SONET type can have shared nodes and code in Network Systems was changed to handle this.
Engineering 73658 CKTID task has lost functionality to sequentially build connection IDs. In previous versions, users would generate the first connection ID using the CKTID task, then right-click and choose GENERATE IDs. That functionality is no longer there. It is still available in the PSR, just not on the CKTID task. The 'Generate Circuit Ids' in the 'Service Request Connections' window is working fine in R5.2 code stream. Code has been included in R6.0 code stream so that 'Generate Circuit Ids' will work in 'Service Request Connections' window as well.
Engineering 73688 When assigning TCICs sequentially on a Trunk Group that has 2016 trunk circuits, it takes more than three minutes to complete. When assigning TCICs sequentially on a Trunk Group that has 2016 trunk circuits, it will take a few seconds to complete.
Engineering 73688 When you click the Trunk Group Info button on the Circuit Identification window, it takes several minutes for the next window to be accessible. The window displays within a few seconds, but it takes a several minutes for the hour glass to go away in order to start entering data. When you click the Trunk Group Info button on the Circuit Identification window, the next window will be accessible within a few seconds. One of the windows displaying the trunk group information was retrieving all rows for the trunk group.
Engineering 73713 User tries to create a new Freeformat facility. User retrieves a coded Network Location to populate the first Network Location field. A Location Name longer than 11 characters cannot be selected. The following prompt displays, "A Network Location for CLF cannot be more than 11 characters." System does not allow the 12 character selection. Choosing Freeformat for the coded locations will allow up to 20 characters.
Engineering 73731 The trunk group information window becomes difficult to read after you clear the trunk group members.
The issue has been solved by introducing a horizontal scroll bar on the window.
Engineering 73894 When entering an order regarding an existing circuit and subsequently canceling the order before creating a provisioning plan, the system is indicating the incorrect number of orders opened against the particular circuit that was involved. The number of opened orders against the circuit is showing correctly in connection design.
Engineering 73951 User has a UPSR OC48 ring with 3 nodes, and the customer had enabled TSI on this network. The channelization for the 3 OC48 segments are done differently - they want to assign different speed circuits on different timeslots around the ring. When the customer puts ring IN SERVICE, the application validates that all the OC48 segments should be channelized identically, and will not let the user save the ring. Per request, if the network is TSI Enabled, then hierarchy equivalency validation will not occur. This will allow the ring to be placed In Service when the network channels are not exact matches around the ring.
Engineering 73987 When querying by Designation on the Connection Design Query, the result set includes connections which do not belong to the queried designation. Also, incorrect facility designations are being stored on design lines. The wrong facility designation is being stored in the transmission_facility_circuit (TFC) table. The script will get the designation off of the ECCKT in the circuit table and compare it to what's stored in the TFC table. If they are different, then the TFC table will be updated to match the designation on the circuit table. Also, if the circuit is showing up with the wrong designation on a child circuit's design lines, the designation will be corrected in that situation as well.
Engineering 74022 User cannot open a circuit because of the following error: " No Circuit Layout Report found for circuit design id xxxxx issue #xx". There were missing circuit layout report entries in the database for corresponding design layout report entries. Script CR139906.sql will insert these missing circuit layout report entries, therefore allowing the user to successfully open up a circuit without error.
Engineering 74029 When setting up capacity management for the GR-303 Group, the application is giving a database error. The user tries to save the Range From and Range To port ranges and encounters the database error. You can now successfully set up and save the capacity management for the GR-303 group.
Engineering 74177 Customer reports the following errors when attempting to search for Connections using Connection Design:

A database error has occurred. The error message is: ORA-00907: missing right parenthesis

A database error has occurred. The error message is: ORA-00933: SQL command not properly ended:

This only affects two specific user IDs.
The DB error that occurred due SQL parsing while retrieving Connections has been rectified and users can view results with out any interruption.
Engineering 74237 When creating an EWO, the Service Type Category field doesn't default to "CLFI" when CLF Format (Structured) is selected in the Connection Format field. When creating an EWO, the Service Type Category field is now defaulted to "CLFI" when CLF Format (Structured) is selected in the Connection Format field.
Engineering 74238 Unable to remove circuits from an ISR after the Connection Design window has been opened for any of the circuits.
If a circuit is opened and just closed, the status of the circuits will be updated as 'In Progress'. So, its not possible to delete circuits which are in 'In Progress' status. The new changes will allow the user to delete circuits which had not opened.
Engineering 74268 Orders that contain circuits in a Problem status can have their tasks completed without actually fixing the associated problem or by only fixing part of the root problem.  The DLRD/RID task validation will now prevent the completion of these tasks if the circuit is in a "Problem" status and the issue which caused the circuit to be in a Problem status has not been resolved and the cancel processing has not been rerun.
Engineering 74484 In the circuit design area where the circuit list is present, the status is not displaying. This appears to be the case only for change orders. The new changes will update the circuit status properly.
Engineering 74839 A SONET node shared with another SONET node, can not be also shared between TWO optical networks This is illustrated when the user embeds a SONET network with a shared node into an optical network, then attempts to share that same node with the second optical network. The original design of the software was not intended to allow Optical Components to be shared with a SONET node. Code changes have been made to support this. When a SONET node is shared with an Optical Component, any changes made in the Managing an Element window to either the Name or the Network Element ID will be kept in sync with the Name and Target Identifier fields found on the Node Properties window which is accessed from SONET and vise versa.

In the Managing an Element window, the Status field will not be editable if the component is shared with a SONET node. A warning message will appear if the user tries to edit the field.

Furthermore, validation in SONET will prevent a node from being deleted (or removed if the SONET network shares the node) if it is shared with an Optical component and connections in the Optical network terminate at the node.
Engineering 75102 Getting "Database Error" when attempting DLC Group Assign. The DLC Group Assign now processes without any errors after syncing the window column sizes to the table column sizes.
Equipment 72643 In a multiple pending order scenario, if there is a pending disconnect assignment for order B under order A and order B is sup-cancelled, the cancel change process does not remove the pending disconnect assignment for order B. Changes needed to be modified. Pending disconnect port assignments will now be removed when the user processes a supp canceled order.
Equipment 73530 Window refreshes and does not return to the same spot on the Cross Connect window. After the Cross Connect window refreshes, it will not scroll to the first row. It will stay where it is.
Equipment 74499 When user tries to assign any T3 to a specific type of equipment, system locks up. Assigning to any other piece of equipment takes only a few seconds. Modified code to handle mapping mixed rate code of N/A and matching rate code, so that it did not stop fetching the next port address or next circuit position.
ISR 72375 If an order is opened using the right-click Service Request Wizard off of the Queue Manger, and that order is later refreshed, a number of orders are returned instead of just the retrieve order. Now the refresh will bring back one order.
ISR 72909 Trunks are getting deleted out of the trunk number range. It is not possible to delete a circuit in 'in-service' from ISR for record activity type.
ISR 72937 When a ISR is supplemented with a new due date, but the new due date window is cancelled, the order goes to view-only, but the process supplement option is still available even though choosing it again causes an error.
Now the ISR does not go to view-only, while processing a supplement on the order.
ISR 73694 The Responsible Party field for the Order Query window for ASRs and ISRs is limited to 8 characters, but not for PSRs. The change will not limit the user to 8 characters for ASR, ISR and USO datawindows. Changes made to the following query criteria screens:

1. ASR - Service Request
2. ASR - CCNA
3. ASR - Circuit
4. ISR - Service Request
5. ISR - Circuit
6. USO - Circuit
7. USO - Service Request
8. USO - CCNA
ISR 73695 Trunks are not sequentially numbered from the right-click action. There are 3 problems that have been fixed:

1. Nothing happens when choosing "Member (A or Z) Number Sequentially ".
--The application does not populate the Member (Aor Z) number sequentially, if already there is a member number entered. So, choosing the menu option does not have any impact on the member number columns. This has been solved by populating with the Member (A or Z) number eventhough there is a number already entered. This Sequential number is based on the newly entered value in the column.

2. Trunk number gets off in the top section, no scroll bar to help correct this.
--This problem has already been solved by introducing scroll bar.

3. There is a scrolling problem where things move back to the top when they should not.
--This is because a filter is being applied on the window and this forces the window to changes its focus. Now this has been corrected to set the focus to the original row and column.
ISR 73704 When disconnecting trunk ranges in an ISR order, the TRUNK NUMBER TO field of 5th line of ranges displays behind the New Entry button obstructing the view of the last entry. The New button doesn't hide any information, and the scroll bar is used to view the Trunk Number Ranges.
ISR 74120 When querying by ISR>Location, results took five minutes to appear. ISR - location search performance has been improved.
ISR 74378 When Refresh is done after supp to cancel, the order is not showing as cancelled. When Refresh is done after supp to cancel, the order is refreshed.
ISR 74527 Getting TGN / Location error on ISR for DID trunks. After making the changes to the code, the window displays without any error and the "Unassigned Trunk Circuits" section in the "TGN and Member number assignment" tab also populated with the list of circuits.
PSR 72685 When you use the Copy Attributes function to update a circuits A location from a coded location to a CLLI. Right-click on a circuit and select Open Circuit, you receive the error message "No rows found matching search criteria for Network Location Search". The circuit still opens but the A location is deleted except for the first letter of the location. You can now use the Copy Attributes functionality to update a coded location with a CLLI without receiving an error message.
PSR 72731 Customer reports that they cannot query by authorization code when copying existing service items to a PSR. You can now query for a customer order by Authorization codes when copying existing items to a PSR.
PSR 72732 On a PSR order, after you have assigned a authorization code to Calling Card, it does not display on the service item for that calling card.
Authorization Code will now be displayed in the service item description for the service item, so it will now display in the treeview next to the service item. If multiple authorization codes exist then it will display the first one off of the authorization tab and it will have a ",..." to signify that multiple authorization codes exist.
PSR 73736 Create a PSR Facility product and five circuits as child products, then add circuit information and PRILOC/SECLOC information to the first child circuit and assign the circuit ID.

When you select Generate Circuit ID after assigning the circuit, the Generate Circuit ID window is empty.
The problem reported in the CR is actually 'Working as Designed'.

The originator of the CR tried to apply 'Generate Circuit IDs' without using the 'Copy Attributes' option, for example, without copying the PRILOC/SECLOC information to the other child circuits, which would not display the remaining circuits. So, if the 'Copy Attributes' is applied to the other remaining four child circuits, then the remaining four child circuits should be available.

The following steps would display the remaining 4 child circuits available:
1. Create a PSR Facility Product with 5 circuit as child products.
2. Add Circuit info and PRILOC/SECLOC info to the first child.
3. Assign the Circuit ID.
4. Right click the first child circuit and Copy Attributes.
5. Copy the attributes [PRILOC/SECLOC is sufficient] of the first child to all others.
6. Now select Generate Circuit ID.
7. The remaining 4 child circuits are available.

In the above steps, the originator had missed the 'Copy Attributes' (Step 5) before 'Generate Circuit IDs'.

Also, to avoid the empty window display, a message will display to the user as 'There are no items eligible for circuit ID generation'.
PSR 73775 When using the signaling type of M-M on a trunk, the application requires a point code for the Z location, when it shouldn't. Point code fields are optional in the PSR Message Trunk Info tab.
PSR 73878 When entering values on the valid values tab of a PSR order, the wrong values are populated in the combo boxes when tabbing from field to field and using up and down arrow keys. When entering values on the valid values tab of a PSR order, the values are correctly populated in the combo boxes when tabbing from field to field, and using the up and down arrow keys, and mouse clicks.
PSR 73966 When you delete information from a NOT REQUIRED valid value, the application displays an error message upon validation that a field is missing and needs to have a value. If the field is not required in the Valid Value values, there should be no error.

PSR 74613 A data problem occurs for the valid value of a given value label in the PSR module whenever more than one distinct value label exists on the PSR order. Therefore, whenever the valid value is deleted from the value label on one product the valid value data is also deleted from another value label that is associated with a different product. The delete process was not using the ID for the service item that the user was deleting the valid value from, so the delete actually deleted other values off of labels with the same name from other service items.
The code in the delete process was changed to include the ID for the service item that the user is deleting the value from. Now when the user deletes a value from a value label only that one specific value will be deleted from the application.
PSR 74639 When we insert a date in a valid value, it saves correctly but when we return to the order item the date changes to the incorrect format and causes validation errors. The date value was being formatted before it was being saved to the database. The formatting was removed. Now the date string will be saved in whatever Regional Setting the workstation is set at.
PSR 74648 Customer reports that the scroll bars under the Labels and Values tab do not work when opening a PSR in View Only mode. Now the user can use the scroll bars with the columns disabled.
PSR 74722 Cannot scroll to the bottom of the Order Information Tab for PSR orders after opening existing orders. Now we can scroll to the bottom of the Order Information Tab for PSR orders after opening existing orders.
PSR 74893 Customer reports that when they add a value to a label on a PSR, then erase that value and click Yes to save changes, the application adds a row for that label with a null valid value.

As a result, they are now required to enter a value for the label and are unable to successfully validate the PSR without it.
The application has inserted a row for that label with a null valid value, when the user adds a value to a label then clears that value and save the changes. Code has been added to check if the label has no value then it won't insert any row.
Technical Framework 73237 If a user loses their password it is necessary to reset that user's password from the security users and groups window in the application. However, after the user password has been changed by ASAP, the user receives a database error when attempting to create their own password when prompted. The error is:

A database error has occurred. The error message is: ORA 01031: insufficient privileges

The SQL statement that caused this error is: ALTER USER XXXX IDENTIFIED BY XXXX
The Change Password window, which appears at logon, now works correctly.
Technical Infrastructure 73540 User data columns of type DROPDOWN cannot have their default value removed once it is set. It can be changed to another value but not removed. Drop-down user data columns now have '(None)' as an option for the data default.
Technical Infrastructure 73930 When updating a network location address (especially when it is changed to the same address as a previously existing net loc address) the network location can no longer be queried in the database. The application was inactivating the address associated to the network location, which is why the location could no longer be retrieved. The address now remains active when it is updated, and the network location can be retrieved. A script has also been provided to cleanup existing network locations that do not have active addresses.
Technical Infrastructure 74107 When you set the preference for Minimum Software Version to a specific EFix level, the you can still log on successfully using an EFix version lower than the Minimum Version defined by the preference. This preference is not needed anymore. Version checking makes sure the client code is the same version as the appserver code. This preference will be removed.
User Setup 71701 Although permissions are set to disable for the User button on the new reservations window, when the User button is selected, the user's User ID is defaulted and the user can then make reservations under the users name. Now the User button on the reservation window is disabled when the user is made disabled in the Security Permissions window.
User Setup 73544 Password changed via ASAP to 1 letter and 9 numbers. Message states that password was changed successfully, yet unable to log in to application when applying new password. Per MetaSolv, passwords must be between 4 and 8 characters long. Message displaying password changed successfully is incorrect. Updated the note in the field definition to say: "Passwords must begin with a letter, contain only letters and numbers (no spaces), and must be between 4 and 30 characters long."
User Setup 73909 Once the password has been changed the user can no longer access the application The code has been modified to allow a numeric in the second character of a password.
User Setup 74380 When Admin tries to scan (F2) the New EWO Order for setting security permissions, the scan function does not occur. In order to set security permissions for the EWO - JSP page, Admin user need to use F12 key, which brings the security permission page. Using F2 key, Admin user can set security permissions to the non JSP, PB windows.
Utilities 73728 CA preview is requiring tbsctrl.ocx to be installed (registered) on the machine. TBSctrl.ocx is now part of the install process and will automatically be registered when using ZAC.
Work Management 70818 In 5.x, the DD task opens the circuit design window when double clicked from work management. You are also able to change the task behavior for smart tasks. The task behavior for the DD task type can now be set to behave like the RID task type so that double clicking a DD task from the work queue manager window will open the service requests circuit window rather than the order search window.
Work Management 72541 In Rules and Behaviors, the user data selection list is showing database values instead of drop-down values. Now when an expression is added, the Values drop-down displays the actual value and not the database value.
Work Management 73416 The application crashes when a custom report that contains retrieval arguments is accessed. Custom reports with retrieval arguments can now be accessed.
Work Management 74007 PSR TN query will not retrieve TNs in NPA/NXXs loaded by LERG. The LERG will now insert/update the status of the prefixes to be in unassigned status instead of in service.
Work Management 74027 Create two new task types based on the functionality of IPASSIGN and E911SMRT. When you attach a provisioning plan to a PSR where these tasks are needed, the system does not recognize the new tasks as being equivalent to IPASSIGN and E911SMRT.
The validation was not looking at the 'related area' of the new task types, which is what specifies that the new task type behaves as a different task type. The validation now looks at the related area, and the new task types can be used in place of IPASSIGN or E911SMRT. The API's have also been updated to include the related area.
Work Management 74102 When you assign a provisioning plan on a PSR, the Desired Due Date and Start Date fields overlap on the Plan Selection tab of the Provisioning Plan Assignment window. The two date fields, "Desired Due Date" and "Start Date", are not overlapped.
Work Management 74321 Customer reports that Search Criteria is not working properly in Work Management. When the user sets a specific criteria for tasks to query for, the tasks displayed are not showing what the Search Criteria was set for. 1. A new preference was added that will allow the user to determine the maximum number of rows that will be retrieved in the queue manager at all times. The new preference will default to 1000 but it can be changed by going to the new preference under Work Management / Work Queue Manager. If the maximum number of rows is reached when doing a retrieval in the queue manager, then the current text that displays the number of rows found will have the text " - Limit Reached" attached to the end of it to let the user know that there are more rows in the work queue that are not currently being displayed. If the maximum limit is reached for a work queue the user can either move the limit up by changing the preference which has a max of 99999 or they can add some selection criteria that will bring the number of rows retrieved within the current maximum limit.
2. Code was fixed so that when the search criteria is set up, the search criteria will always be saved and used in the retrieval of the data for the work queue.
Work Management 9999 DD task completion validation is very slow. It was taking 12 seconds for a 672 trunk order in the 5.2.7 release. The same order is now taking over an hour. The delay is between the time to right-click the DD task in the queue manager and choose complete task to the time the task completion window opens. Improved performance for completing DD tasks with large numbers of circuits.

 

MSS 6.0.4

Component

Fixed Issue

Description

ASR

Issue ID: 74117

Internal CR#: 140019

Problem: On an ASR MSL order, the ILAM task is not accessing the End User Information on the order.  Also, for an MSL leg/circuit where the SECLOC is a CLLI, the ILAM window is displaying the wrong CLLI code. 

Resolution: Altered the ILAM task window so that, for ASR MSL orders, it will display the SECLOC end-user location name and address when an end-user location is used for the MSL leg SECLOC.  Also modified it so that the proper CLLI code is displayed if the MSL location is a CLLI.

DB

Issue ID: 75459

Internal CR#: 144635

Problem: Problem with the 6.0.3 database upgrade. The Setup Guide states that the prodfix SQL Master script starts with a Capital M but code that was delivered, it was a lower case 'm'. 

Resolution: The file has been renamed with a capital 'M.'

DB

Issue ID: 73553

Internal CR#: 140563

Problem: Customer is experiencing performance issues in Equipment Assignment in Connection Design. The equipment window is taking more than 30 seconds to open. 

Resolution: Expanding a piece of equipment in Equipment Inventory via the Connection Summary will now be faster.

Engineering

Issue ID: 75821

Internal CR#: 169901

Problem: In existing embedded optical networks, some of the connections are not appearing on the canvas. Also, when you try to embed an optical network into a new optical network, none of the connections display.  

Resolution: When an optical or SONET network is embedded in Optical, the connections are now displayed.  The user will now see all the connection drawings in the embedded networks.  If the user tries to embed an optical network into a new optical network, the new network must be saved, closed, and reopened for the connections to display correctly. 

Engineering

Issue ID: 74254

Internal CR#: 137776

Problem: For a physical connection, when trying to associate to a network in Connection Design, the application gives a java.sql.SQLException error. 

Resolution: User will no longer get a java exception error when trying to associate to a network in Connection Design.  If an element cannot be found, the user will now get a descriptive error message stating so.

Engineering

Issue ID: 75102

Internal CR#: 142412

Problem: Getting "Database Error" when attempting DLC Group Assign. 

Resolution: The DLC Group Assign now processes without any errors after syncing the window column sizes to the table column sizes.

Engineering

Issue ID:

Internal CR#: 174571

Problem: Unable to generate DLC Capacity Management Report. 

Resolution: DLC Capacity Management Report will now be generated successfully

Engineering

Issue ID: 75702

Internal CR#: 169957

Problem: When autobuilding optical facilities, user receives an Out Of Memory error message. 

Resolution: Made another change to how the data is being saved when Finish is clicked in the Autobuild wizard.  The data will still be saved incrementally, but the amount of data kept in memory is now further reduced.

Engineering

Issue ID: 73784

Internal CR#: 133008

Problem: Groom jobs are not completing. 

Resolution: The library list for groom jobs has been corrected. Now you can post the groom jobs to the background without any error.

Engineering

Issue ID: 74839

Internal CR#: 140961

Problem: A SONET node shared with another SONET node, cannot be also shared between TWO optical networks This is illustrated when the user embeds a SONET network with a shared node into an optical network, then attempts to share that same node with the second optical network. 

Resolution: The original design of the software was not intended to allow Optical Components to be shared with a SONET node. Code changes have been made to support this. When a SONET node is shared with an Optical Component, any changes made in the Managing an Element window to either the Name or the Network Element ID will be kept in sync with the Name and Target Identifier fields found on the Node Properties window which is accessed from SONET and vice versa. 

In the Managing an Element window, the Status field will not be editable if the component is shared with a SONET node. A warning message will appear if the user tries to edit the field. 

Furthermore, validation in SONET will prevent a node from being deleted (or removed if the SONET network shares the node) if it is shared with an Optical component and connections in the Optical network terminate at the node.

Engineering

Issue ID: 75260

Internal CR#: 143904

Problem: The groom tool allowed circuits associated to a network to be used for a groom project. 

Resolution: Equipment assignments made through the SONET provisioning assistant can no longer be pulled into the groom tool.

Engineering

Issue ID:

Internal CR#: 032889

Problem: Using 'LIKE' (or Contains) for the criteria on the two-six code secondary search fields has a performance issue. 

Resolution: Connection Design - using 'LIKE' (or Contains) on two-six code performance has been improved.

Engineering

Issue ID: 74970

Internal CR#: 141143

Problem: Cancelled facilities are appearing on the facility utilization report with channels listed as spare. 

Resolution: Channels of canceled facilities will no longer appear on the facility utilization report as spare capacity.

Engineering

Issue ID: 73357

Internal CR#: 141846

Problem: Create an order for a T3 and work the order through RID and completed RID but not DD. Create an order to add 3 T1s to the T3, and assign the T1s to the T3 but leave them pending and do not complete RID. Supp the T3 order to cancel and reopen RID. In RID, select to Cancel Change the T3. You receive notice that there are underlying facilities riding the T3. The circuit cancellation process appears to continue and Cascading Reconcile is triggered. At this point there is an error and the T3 order is put in Problem status. 

Resolution: In the scenario above, processing will stop after the message stating that underlying riders exist.  A second message will be displayed stating that the circuit will be put in Problem status.

Engineering

Issue ID: 75302

Internal CR#: 143708

Problem: When a user enters a contact, via the PSR, for the PRIOLOC/SECLOC that exceeds 15 characters an error appears when trying to open the design for the circuit. 

Resolution: When a user enters a contact, via the PSR, for the PRIOLOC/SECLOC that exceeds 15 characters no error will appear and the end user contact will be truncated to 15 characters.

Engineering

Issue ID: 72466

Internal CR#: 143942

Problem: You cannot cancel Trunk Assignment. 

Resolution: The user will now have the option to send the Assignment Cancel, the Change Cancel, and the Disconnect Cancel processes to the Background Processor if the Background Processor is enabled.

Engineering

Issue ID: 74947

Internal CR#: 141801

Problem: When making a change order for a large trunk group (around 1500 trunks), hitting the trunk group info button can take approximately 7 minutes to open the Trunk Group Information window the first time. 

Resolution: Selecting the trunk group info button after a change order has been put in for a large trunk group, will take approximately 25% less time than in previous versions.  Please keep in mind that a large amount of conditional validation is being done.

Engineering

Issue ID: 74805

Internal CR#: 170097

Problem: Network Design for a large optical network takes too long to open. 

Resolution: Modified the way Optical networks open so that not all the data for the system and its connections are retrieved when the system is opened. The data will now be retrieved as it is needed.

Engineering

Issue ID: 76236

Internal CR#: 173332

Problem: The Grooming Preference "Maximum Number to Process in the Foreground" is a SYSTEM preference, but the online Help states that it is a USER preference.  

Resolution: Online Help was corrected to match the software.

Engineering

Issue ID: 75454

Internal CR#: 144587

Problem: Customer receives error "unable to open file". The file was removed, so the call needs to be removed. 

Resolution: Removed call to script cr34203.sql from pfixsql_master.

Engineering

Issue ID:

Internal CR#: 144641

Problem: When creating a new Component Type and you do not enter a Component Type or Component Type Name, the error message displays using the incorrect term, Element, instead of using the term, Component. 

Resolution: The error message will display using the correct term, which is "Component".

Engineering

Issue ID: 75260

Internal CR#: 144527

Problem: The groom tool allowed circuits associated to a network to be used for a groom project. 

Resolution: Equipment assignments made through the SONET provisioning assistant can no longer be pulled into the groom tool.

Engineering

Issue ID: 74693

Internal CR#: 141063

Problem: The Capacity Management report is not handling facility assignments.

Resolution: The Capacity Management report now handles facility assignments.

Engineering

Issue ID:

Internal CR#: 142356

Problem: On the Network Area Definition window, the Network Area Type cannot be saved. 

Resolution: This problem only occurred if the Network Area Type was first set to 'None', saved, and then set to another value.  The new value would not save.  The save logic has been corrected, and the Network Area Type can be successfully saved.

Engineering

Issue ID:

Internal CR#: 144200

Problem: This is a known issue that was found in the Standalone Network Elements w/o Equipment section of the Network Element Migration (NEM). This is the final section in the NEM, which is a part of the Next Gen Migration.  

Network Elements in this section of the NEM appear here because they were unable to be processed in previous sections of the NEM up this point. These are pre-M6 Network Elements (created via Equipment > Network Element) that do not have an association to Equipment or Network Systems.  

When a record is saved in this section, a blank Error Text window will appear and the row will not be able to be processed. Please refer to the workaround for a solution to correct this error.

Resolution: PMAT is now showing the results for all of the queries.

Engineering

Issue ID:

Internal CR#: 144293

Problem: This problem is specific to the Pre-Migration Analysis Tool that is used in conjunction with the Next Generation Migration. The tool is referred to as PMAT and it is a separate .exe file that is used to analyze some of the data in your current production database that will be affected by the Next Generation Migration. In the Order section of the PMAT, there is a query to display the number of Service Items that with no Connection ID. This query is not displaying the results as it should. 

Resolution: This problem will be fixed in the next release of PMAT.

Engineering

Issue ID: 75859

Internal CR#: 171112

Problem: For a DLC Network, the user is allowed to delete an equipment association to an element even if the equipment's ports or its installed equipment's ports have been used in the DLC provisioning assistant. 

Resolution: For a DLC network, you will not be able to delete an equipment association to an element if the equipment's ports or its installed equipment's ports have been used in the DLC provisioning assistant.   To delete the association, you must first remove all provisioned DLC assignments to that equipment and element.

Engineering

Issue ID:

Internal CR#: 054444

Problem: The DLC Network link in Connection Design was enabled for non-ordered PSR Special Circuits (i.e. Telephone Numbers).   If the user clicked on the DLC Network link in this scenario, the application would freeze, and the user would have to shut down the application via the Windows Task Manager. 

Resolution: The DLC Network link will only appear in Connection Design for PSR ordered Special Circuits (i.e. Telephone Numbers) and will work properly when selected.

Engineering

Issue ID: 75299

Internal CR#: 143962

Problem: When trying to autobuild a connection created between an embedded optical and SONET network, the application crashes. 

Resolution: When autobuilding optical connections CLLI code should be used to build the ecckt, corrected code where it passes the network location name in the ecckt. It caused the application to crash when name was longer than 20.

Engineering

Issue ID: 74575

Internal CR#: 138750

Problem: Performance problems when adding facilities to the Group Assignment window. 

Resolution: If the selected facilities are assigned to port address, the chain of cross-connected ports will be also checked to make sure all the ports are available, so that the circuit position can be displayed as available ones. So, for adding some facilities it will take longer than ones not assigned to a port.  

Code has been modified to bundle SQLs together to reduce traffic to the server.

Engineering

Issue ID: 74637

Internal CR#: 139770

Problem: When auto-building an optical connection, the autobuilt assignments are not mapping to the equipment correctly.

Resolution: When the connection has been auto-built, the connection is assigned to a port and the mapping call is issued.

Engineering

Issue ID: 73627

Internal CR#: 142246

Problem: Changing the designations of a facility in an SDH ring, the system automatically modifies the rate code. 

Resolution: Changing the designation of a facility in an SDH ring will not change the rate code of the selected facility.

Engineering

Issue ID: 74903

Internal CR#: 142871

Problem: When a large Trunk Group Range has been defined for a service type group used in a Trunk connection, an error message will display for SP_CALCULATE_TGN_NUMBER and trunk group information will not save. 

Resolution: When a large Trunk Group Range has been defined for a service type group used in a Trunk connection, the trunk group information will save without giving an error message.

Engineering

Issue ID: 74814

Internal CR#: 143910

Problem: When using multiple pending orders, if the user is going in to create a new issue for a circuit and they get the Design Issues window, choosing Create New will not correctly change any previous issue for that circuit and order to overridden. It leaves it as Pending, which makes it hard to tell which issue is the correct Pending issue. 

Resolution: On the Design Issues window, the Create New option should only be enabled if the circuit is of a New activity.  Also, if an issue has already been created for the particular order the user is currently working on, and it is determined the Design Issues response window should show to pick an issue to create from. It should only list the issue already created for this order and nothing else.

Engineering

Issue ID: 75108

Internal CR#: 144162

Problem: A new and a change order are created for a connection.  The disconnect order is used to access the design of the connection before the new order is.  As a result, the issue for the disconnect order appears before the new one. 

Resolution: A new and a change order are created for a connection.  The user cannot access the design of the connection from the disconnect order until an issue is created for it from the new.

Engineering

Issue ID: 39883

Internal CR#: 145789

Problem: When SUPP Correcting an order to reduce trunk qty and trunks are in the 'In Progress' status (known as a partial cancel), the system will not allow it. Reduction in trunk quantity requires a SUP to Cancel the entire order. (PSR has a cancel preference). Window will prompt with message stating that circuits cannot be deleted once design lines have been drawn. 

Resolution: When SUP Correcting an order to reduce trunk qty and trunks are in the 'In Progress' status (known as a partial cancel) the system will allow it. Reduction in trunk quantity will take place even if designs have been drawn for the trunk circuit.

Engineering

Issue ID: 75600

Internal CR#: 170244

Problem: In a multiple pending order scenario, if there is a pending disconnect assignment for order B under order A and order B is sup-cancelled, the cancel change process does not remove the pending disconnect assignment for order B. 

Resolution: In a multiple pending order scenario, if there is a pending disconnect assignment for order B under order A and order B is sup-cancelled, the cancel change process will now remove the pending disconnect assignment for order B.

Engineering

Issue ID: 73765

Internal CR#: 133009

Problem: ISR End User Location Access telephone number is not showing on circuit design. 

Resolution: ISR End User Location Access telephone number will show on circuit design.

Engineering

Issue ID: 74177

Internal CR#: 140076

Problem: Customer reports the following errors when attempting to search for Connections using Connection Design: 

A database error has occurred. The error message is: ORA-00907: missing right parenthesis 

A database error has occurred. The error message is: ORA-00933: SQL command not properly ended: 

This only affects two specific user IDs. 

Resolution: The DB error that occured due to SQL parsing while retrieving connections was fixed and users can view results with out any interruption.

Engineering

Issue ID: 73705

Internal CR#: 132144

Problem: Optical Provisioning Assistant is not finding a path when shared nodes are used. 

Resolution: The code that retrieves connection information did not handle shared SONET Node. Added new code to handle the shared node.

Engineering

Issue ID: 75294

Internal CR#: 146291

Problem: In a big network (networks which contains embedded networks and rings) make a connection between nodes of an embedded SONET ring with a node in embedded optical network.  After saving (with networks compressed) on reopening the parent network, the link goes invisible in graphical view of the parent network, but the connection ID appears in the component relationships of the Network details.  Also the same connection ID can be found in the hierarchical view of the network. 

Resolution: This fix is considered a partial fix. The scenario of embedding two networks into the same network where those two embedded networks have a common shared node is not currently graphically supported. This situation causes the canvas to become 'confused' as to which instance of the element to connect the lines to. 

This fix corrects a problem with lines disappearing that are connected to a SONET node in an embedded SONET network (minus the scenario mentioned above). This fix does make all of the 'missing' connections from the common node scenario to appear but most of them only appear inside the expanded clouds. But, they can now be autobuilt as desired. The canvas still does not know which instance of the element on the canvas to use, so it uses the first one it finds.  

The fix also takes care of the following:

1. Deleting an Optical Element that has been shared with a SONET node:

Validation has been added to prevent the Optical Element from being deleted. A message will inform the user that the element must be deleted from within the SONET network. Instead the user will now have a new popup menu option to 'Remove From Drawing'.  This option will remove the element from the from the network drawing without deleting the Optical Element. 

2. The user could not successfully delete the shared SONET nodes from the SONET networks under a certain scenario. That scenario was to first share the SONET node with an Optical Element and then to subsequently embed the SONET network of that node into another Optical Network. Code was added in the delete logic of the SONET node to support this scenario. 

3. The action of sharing a SONET node with an Optical Element and then subsequently embedding that SONET network into an Optical Network was causing data corruption. A prod fix sql file called CR143751.sql has been included to fix the data and all code surrounding this scenario has been fixed to prevent further data corruption.

Engineering

Issue ID: 74585

Internal CR#: 138779

Problem: Users are not always presented with same error message when they are trying to DD complete a circuit that has blocking circuits that must be completed before the current order. 

Resolution: Users will be presented with the option to view the blocking orders when the order being DD completed has connections riding facilities that are also on open orders with a DD before that of the current order.

Engineering

Issue ID: 74307

Internal CR#: 142030

Problem: User receives an error during provisioning that says all segments have to be assigned. However, the SONET assistant is not displaying the unassigned segment when the link for that segment is clicked. 

Resolution: Corrected the code error where the optical page did not send the correct SONET route ID to the SONET provisioning assistant.

Engineering

Issue ID: 75208

Internal CR#: 142949

Problem: Placement of entry field for "Constant For Freeformat Circuit ID" is outside the boundaries of the System Preference window. 

Resolution: Placement of entry field for "Constant For Freeformat Circuit ID" is not outside the boundaries of the System Preference window.

Engineering Work Order

Issue ID: 74238

Internal CR#: 136873

Problem: Connections cannot be removed from a new Engineering Work Order after the Connection Design window has been opened for any of the circuits. 

Resolution: Connections without design lines can be removed from a new Engineering Work Order after the Connection Design window has been opened for any of the circuits. The connections with design lines will not be removed from the order even if it is selected to be removed.

Equipment

Issue ID: 75817

Internal CR#: 148955

Problem: Cannot print the cross connect assembly report. 

Resolution: Enabled the ability to print the cross connect assembly report in pdf format.

Equipment

Issue ID: 73988

Internal CR#: 136383

Problem: When adding a new piece of equipment using an Engineering Work Order on a location that does not have any equipment installed, the Equipment Install window will not save changes if slot name is selected as a column to display in the Equipment Description Preference. 

Resolution: When adding a new piece of equipment using an Engineering Work Order on a location that does not have any equipment installed, the Equipment Install window will save changes if slot name is selected as a column to display in the Equipment Description Preference. When the slot name was not found in the database, the code assumed there was an error and the equipment was not installed.

Equipment

Issue ID: 74692

Internal CR#: 141229

Problem: The remove functionality does not allow for the removal of supp canceled EWO that has never had equipment, connections, or tasks. 

Resolution: Supp canceled EWOs that have no equipment, connections or tasks can now be removed.

Equipment

Issue ID: 73530

Internal CR#: 145630

Problem: Cross-connect completes and refreshes back to the top. 

Resolution: The right section index has been recorded before the redraw section, so that after cross connect, it will not redraw to the top.

ISR

Issue ID: 75604

Internal CR#: 172234

Problem: If the user changes the ecckt of an existing trunk group on an order for a large number of trunks, it takes a long time to add the trunks to the order.  In one example, 3000 trunks took 20 minutes to be added to the order.  For comparison, creating a new order for 3000 trunks took just 2 minutes. 

Resolution: Moved the code for validation for trunk circuits to a package and stored procedures.  This eliminates the network latency involved in transmitting large results sets to the client machine for processing.

ISR

Issue ID: 74273

Internal CR#: 137086

Problem: When you open the LSO NPA/NXX at the Circuit Identification window and then tab, you receive an error. 

Resolution: Now the LSO NPA/NXX at the Circuit Identification window can be entered without any error.

ISR

Issue ID: 75599

Internal CR#: 146584

Problem: ISR circuit ID creation for CLF does not use 11 byte CLLI when provided. 

Resolution: Now the 11 byte CLLI code populates in the Location A and Z columns.

ISR

Issue ID: 74120

Internal CR#: 141017

Problem: When querying by ISR>Location, results took 5 minutes to display. 

Resolution: Now ISR location search performance has been improved.

LSR

Issue ID:

Internal CR#: 145500

Problem: Persistent changes for MLSR8 DB changes. 

Resolution: Persistent classes are generated for the tables affected with DB changes for MLSR8.

MIP

Issue ID:

Internal CR#: 147322

Problem: Query Telephone Number Inventory and Pre Assign Telephone number where not implemented in the prior release of the XML integration APIs. 

Resolution: Implement the Query Telephone Number functionality in the queryInventoryManagementRequest XML API method on the InventoryManagement Control.  Also implement the pre Assign Telephone Number functionality in the updateEntityByValueRequest XML API method in the InventoryManagement Control.

PSR

Issue ID: 74722

Internal CR#: 140999

Problem: You cannot scroll to the bottom of the Order Information Tab for PSR orders after opening existing orders. 

Resolution: You can scroll to the bottom of the Order Information Tab for PSR orders after opening existing orders.

PSR

Issue ID: 75553

Internal CR#: 147610

Problem: You cannot leave a field null after a value has been inadvertently entered in a User Data drop-down field. 

Resolution: Now you can change the User data value to '(None)' - NULL after it has been selected from some value in the non-required columns.

PSR

Issue ID: 73814

Internal CR#: 138557

Problem: The application allows duplication calling card numbers and PIN number (Auth Codes) to be entered for multiple calling card products that exist in a pending status. 

Resolution: Now in the Authorization/Account/PIN Code Maintenance window, the column 'Unique' has been modified to a drop-down list. The list shows the following values: 

            Not Unique
           
Single Use Only
           
By Customer
           
By Customer & Catalog Item 

a) Not Unique: System will allow the duplicate values. 

b) Single Use Only: System will check the Auth Code, whether it is used on any customer and any catalog item. 

c) By Customer : System will check the Auth Code, whether it is used on Any Catalog items for that Customer 

d) By Customer & Catalog Item : System will check the Auth Code, whether it is used on Same Catalog item for that Customer.

 If the Auth code is used already, system will show the alert message.

PSR

Issue ID: 75977

Internal CR#: 171001

Problem: There are two problems. 1. When you change the price for a product, the value is not displaying correctly in the application. You have to add it again for it to actually show correctly. 2. When adding a new base price, the default value of 0.00 is not accepted unless it's manually typed.  

Resolution: 1) Code is added to show the price correctly for the first time as well.

2) In the pricing window, the column will accept the default value of 0.00.

PSR

Issue ID: 74639

Internal CR#: 143698

Problem: When you insert a date in a valid value, it saves correctly but when you return to the order item the date changes to the incorrect format and causes validation errors. 

Resolution: The date value was being formatted before it was being saved to the database. The formatting was removed. Now the date string will be saved in the Regional Setting the workstation is set at.

PSR

Issue ID: 74297

Internal CR#: 137348

Problem: Customer reports that the correct statuses of all services items are not being reflected after a multi disconnect.  Some of the products still show as In Service. 

Resolution: When you perform a multi disconnect, all products designated to be disconnected show the disconnected status.

PSR

Issue ID: 74893

Internal CR#: 141155

Problem: Customer reports that when they add a value to a label on a PSR, then erase that value and click Yes to save changes, the application adds a row for that label with a null valid value. 

As a result, they are now required to enter a value for the label and are unable to successfully validate the PSR without it.

Resolution: When the user added a value to a label, then cleared that value and saved the changes, the application would insert a row for the label with a null valid value Code has been added to check the label.  If the label has no value then a row will not be inserted.

PSR

Issue ID: 75172

Internal CR#: 142947

Problem: If a valid value has a length limitation (between 1 and 22 characters), if you try to enter a word up to 22 characters, it gives a validation message, but if you join spaces in the valid values, the validation doesn't count them. 

Resolution: Spaces will be counted as valid data when entered as valid values.

PSR

Issue ID: 75296

Internal CR#: 143709

Problem: When entering values into the User Data Category window there is enough room to enter values up to 51 characters.  When entering PSR User Data approximately 30 characters are visible in the combo box.  As a result, we are not able to see the entire user data value if it has more than 30 characters. 

Resolution: To fix this issue, the width of the drop-down column has been increased based on the max number of characters in the list.  A horizontal scroll bar has been included to the drop-down column.

PSR

Issue ID: 74584

Internal CR#: 139764

Problem: Customer reports that the names for their Next Gen products disappear when a change order is placed against them then later that change order is Supp Cancelled. 

Resolution: When supp canceling a PSR order with an NGN product,  the auth code delete functionality was executed even though the product has no auth code.  This functionality caused the item to display without the product name. 

A condition has been added to check the auth code for each product. If it exists, it will execute the auth code delete functionality. Now the name of the product shows without any problem.

PSR

Issue ID: 76093

Internal CR#: 171530

Problem: Customer reports the following error when they create a new PSR for a Next Gen product, give it a specific Short Name, supp cancel the PSR prior to provisioning plan assignment and try to create another Next Gen order using the same Short Name: 

"The Short Name XXXXXXXX is not unique. Short Names must be unique on all network systems". 

Resolution: Corrected the code to allow the reuse of a disconnected/cancelled short name.

PSR

Issue ID:

Internal CR#: 141281

Problem: Customer would like a stored procedure exit that runs BEFORE validation. It should work just like PSR Custom Validation, but rather than running at the end of validations, run before any begin. 

Resolution: A new stored procedure, SP_PSR_CUSTOM_PRE_VALIDATION has been added. This procedure is called immediately before the rest of the java validations run. The procedure receives the document number as an argument.

PSR

Issue ID: 75248

Internal CR#: 143606

Problem: Customer reports that when you click "Copy Existing Services" then select a parent item to be copied, if you right-click to bring up the pop-up window, then click on the white space without selecting an option, the application will freeze, then shut down shortly thereafter. 

Resolution: Due to recursive call, the system was being halted when the user clicked in the white space after right-clicking on an item. Now new logic is implemented to avoid this error.

PSR

Issue ID:

Internal CR#: 143745

Problem: A preference was added in 5.2.14 to allow the user to determine what the function code should be when disconnecting an LNP number for an E911 record.

"Function Code to Set for LNP Disconnects"
U (Unlock)
D (Disconnect)
Disconnect should actually say Delete. 

Resolution: The wording has been changed to read "Delete".

PSR

Issue ID:

Internal CR#: 146554

Problem: PSR API: When exporting an order that has an IP Address on it, the number inventory ID for that IP Address exports as 0. 

Methods
ExportNGNServItem
ExportNGNPSR
ExportPSR_v3
ExportServItem_v3 

Resolution: The number inventory id will now export for IP Addresses when any of the four methods are executed.

PSR

Issue ID:

Internal CR#: 148393

Problem: The email name doesn't get exported.  The domain and domain suffix gets exported correctly, but not the email name. 

Resolution: The email name was being queried for using the wrong activity code. This has been corrected and the name should populate correctly in exportPSR_v3, exportServItem_v3, exportNGNPSR, and exportNGNServItem.

PSR

Issue ID:

Internal CR#: 143755

Problem: The default sort on the E911 smart task is descending when it should be ascending.  So, the user sees

Line-4
Line-3
Line-2
Line-1

It should be the opposite. 

Resolution: The sort on the E911 smart task has been corrected to sort by service item, then by telephone number.

PSR

Issue ID: 74962

Internal CR#: 141090

Problem: When attempting to perform a Service Request Search using Search By: All Customer,  and if the user sets criteria in the Customer Name field using the LIKE operator, the user sometimes gets an error indicating that the value in "customer_name does not pass validation test".  When the error message is closed, the search returns a list of results with the Customer Name field blank on all rows. 

Resolution: Fixed window to eliminate the error.

Technical Framework

Issue ID: 74620

Internal CR#: 148405

Problem: Error message keeps appearing due to sql not being properly generated for sql. 

Resolution: Modified the appserver code to correct the improperly generated sql.

Technical Framework

Issue ID: 74971

Internal CR#: 145475

Problem: Under Read Only Security role, the user had the right-click options enabled for "Copy" and "NewFrom" for groups and users. 

Resolution: Rows were added to base data through prodfixsql to address the new popup menu options that were added to the right-click menu in maintaining users and groups. To take advantage of this new data, security admin will need to navigate to Permissions, select Popup Menus, and then select the RO_Security role. Under Popup Menus, select the window "w_pfcsecurity_usermgmt.m_lv_menu.m_groupgroup". Two new rows will appear on the right window pane with Permission set to "Not Set". Change these to "Disabled". Do the same thing for window "w_pfcsecurity_usermgmt.m_lv_menu.m_usergroup".

Technical Framework

Issue ID: 75295

Internal CR#: 143748

Problem: Customer reports that when a user logs into the application and changes their password (through Preferences > User Info > Password) and they do not close out the application (i.e. they allow the app to time out), they get the following message: 

"You have reached this message because you have either not logged on through MetaSolv Solution or your session has timed out." 

They click the link that allows them to re-login, and they get an error that says:  

You entered an invalid User ID and Password combination. 

ORA-01017: invalid username/password; logon denied

Resolution: Modified application code in preferences to prevent the problem when the re-login screen appears.

Technical Infrastructure

Issue ID: 74358

Internal CR#: 137425

Problem: The user is unable to disable the links for New Product Service Request,  New Internal Service Request, New Access Service Request, New Local Service Request and New Trouble Ticket - all of these are pointing to w_neworder if you right-click and look at the properties of the links.  This window is not accessible from security in order to lock it down. The only other way to actually remove the links is disabling the software option, but that is not an option because all users will be affected by that.  

Resolution: Added a row to the security_templates table for w_neworder (which is not a real window). The name "w_neworder" is tied to the navbar items for New ISR, ASR, LSR, PSR, USO, Trouble Ticket. So, now the system administrator can go into security and lock out these navbar items via the w_neworder object. In addition, the "new" menu item on w_query_monster_sheet will also have to be disabled to prevent users from creating a new order from the link on the main order query window. This object is to be used only for removing the objects from the navbar. Setting w_neworder to "READ ONLY" will have no effect on whether users can create a new order.

User Setup

Issue ID: 75692

Internal CR#: 147308

Problem: Add a mailto: link when customizing My Navbar and the link does not work. 

Resolution: Modified framework code to allow mailto: links.

User Setup

Issue ID: 75197

Internal CR#: 143139

Problem: Inconsistent behavior in assigning permissions within Security.  If the security administrator highlights a user account, right-clicks, and chooses to Assign Permissions, the Assign Permissions window, User/Group drop-down automatically defaults to the User previously selected as expected.  However, if a Group is highlighted for permissions to be set, the window defaults to the DEFAULT user group. 

Resolution: Modify the IF block to work properly by using a unique keyword 'ASGN-PERMNS'.  Now the IF block will work effectively to process respective values being passed and the User/Group drop-down automatically selects the User/Group name for whom the Assign Permission options was selected.

User Setup

Issue ID:

Internal CR#: 147196

Problem: Incorrect message on length of user id in security administration. 

Resolution: Modified message to match up with edit mask on security window.

User Setup

Issue ID: 74754

Internal CR#: 139415

Problem: Customer reports that the open to print in Work Queue Manager is disabled and cannot be enabled in Security. 

Resolution: The Print menu option is now enabled for the Work Queue Manager window for any selected task and can be maintained in Security. 

Utilities

Issue ID: 75490

Internal CR#: 145168

Problem: Once a CA is created, it cannot be deleted.  There is no delete functionality working including the Delete Icon, Edit/Delete from the toolbar menu, and the highlight, right-click, delete procedure.  It should be noted that all of these procedures are enabled within the application and user can perform them with no warning messages.  However, they have no affect on the data. 

Resolution: Enabled the delete functionality for CAs.  Unit tested for the following cases :

1. Retrieve a CA, highlight, click the delete icon, Yes to the message. The CA is deleted.

2. Retrieve a CA, highlight, right click, select delete, Yes to the message. The CA is deleted.

3. Retrieve a CA, highlight, Click on Edit from toolbar menu, select delete, Yes to the message. The CA is deleted.

Utilities

Issue ID: 75487

Internal CR#: 145170

Problem: Within Utilities, when working with CAs, the user cannot use the Control C or Control V hot key functionality.  Also, from the toolbar Edit menu, the copy and paste items are greyed out.  

Resolution: Now the toolbar Edit menu items Cut, Copy and Paste were Enabled and the user now able to use the Ctl+X, Ctl + C and Ctl + V hot key functionalities to cut, copy and paste the text.

Utilities

Issue ID: 75488

Internal CR#: 145174

Problem: When creating a new CA within the Utilities module, if a cursor left in Max Value Length field with no text entered and user tries to go to another application, a warning message regarding required fields is given. 

Resolution: Now the error message is not thrown when moving within/across application.  Anyway all the columns will be validated while saving the "Custom Attributes".   So, we can remove the validation check from the "itemerror" event, which is a redundant process.

Utilities

Issue ID: 75496

Internal CR#: 145190

Problem: within the Custom Attributes Rules window, under the CA Dependent Valid Values tab, there is a problem with the row selection.  Rows selected are held and won't release so they stay selected.   

Resolution: Now, only the selected rows will be highlighted. 

Utilities

Issue ID: 75489

Internal CR#: 145192

Problem: When creating CAs and adding dependencies, the screen does not update with the proper data when dependencies are selected.  In order to see the updates, the user must back out of CAs and come back into the specific CA being edited.  Once this is done once, the data is always displayed. 

Resolution: The screen will update with the proper data when dependencies are selected when creating CAs and adding dependencies.

Work Management

Issue ID: 74027

Internal CR#: 141162

Problem: When you create two new task types based on the functionality of IPASSIGN and E911SMRT, then attach a provisioning plan to a PSR where these tasks are needed, the system does not recognize the new tasks as being equivalent to IPASSIGN and E911SMRT.  

Resolution: The validation was not looking at the 'related area' of the new task types, which is what specifies that the new task type behaves as a different task type.  The validation now looks at the related area, and the new task types can be used in place of IPASSIGN or E911SMRT.  The API's have also been updated to include related area.

Work Management

Issue ID: 75109

Internal CR#: 142220

Problem: User is able to assign provisioning plan without CKT ID task and without assigning CKT ID inside PSR. Error message does not occur like it does in 5.2.x. Other tasks, like the NET_DSGN and E911 task, may also have this problem. 

Resolution: Application would not allow a circuit product to be provisioned without a CKTID task when user has not assigned a circuit ID in the PSR previously. The validation is true with NET_DSGN and E911 task as well.

Work Management

Issue ID: 75776

Internal CR#: 169572

Problem: Customer can't launch TRANS task for EWO orders. 

Resolution: The SQL used in opening the TRANS task was altered so that if the order is not ASR or ISR that data will still be returned.  This prevents the "Error 6" and the application crash.

Work Management

Issue ID: 74973

Internal CR#: 141265

Problem: User receives errror: "multiple drawings exist". 

Resolution: Added code to allow the users to correct a PERT chart drawing that may have become invalid.  The user can now right-click from within the PERT chart and choose the "Rebuild Drawing" and the PERT chart will be rebuilt.

Work Management

Issue ID: 74664

Internal CR#: 140957

Problem: User receives error when saving binding information. 

Resolution: Now, the Binding Location and Service Name information are saved correctly.

Work Management

Issue ID: 75189

Internal CR#: 142866

Problem: Users receive an informational message requiring an IPASSGN task on a Pre Order Prov Plan.  A pre order plan cannot be attached to a PSR if the plan does not have an IPASSIGN task.  This occurs if the order contains IP Address items.  When these actions have occurred and the user opens the Tasks window to assign the pre order plan, the message is received after clicking OK. 

Resolution: The new changes will not require IPASSIGN task for a pre order plan.

Work Management

Issue ID: 75654

Internal CR#: 146738

Problem: Need New/From functionality for Rules and Behaviors. 

Resolution: Added a New From link to the Rules and Behaviors window. You can click this link to copy and create a new rule.

 

MSS 6.0.5

Component

Fixed Issue

Description

ASR

Issue ID: 77301

Internal CR#: 183532

Problem: ASRStartup.init() failed in *.mss.log file after deploying ASR30.2 on 6.0.4.54 with the XML APIs.

Resolution: You can now install ASR30.2 on an M6 application server with the XML API option.

ASR

Issue ID: 76062

Internal CR#: 171174

Problem: An error message appears when saving the Circuit ID on a Bandwidth ASR where the PSPEED field option is set to four characters.   

Resolution: Database changes were made in the table "bandwidth_ckt_bit_rate". The "bit_rate_quantity" column width was increased to NUMBER(11,5). 

ASR

Issue ID: 76151

Internal CR#: 172099

Problem: The CABS Extract Date is not populated when the Billing record has successfully interfaced with CABS. 

Resolution: At completion of the CAD task, the CABS Extract Date is updated in addition to the CABS Extract Ind being set to 'Y'.

ASR

Issue ID: 76434

Internal CR#: 175112

Problem: You are unable to change the A LSO on the Circuit Identification window for an End User Special ASR with ACI forms. 

Resolution: When the PRILOC type is set to "end-user", the "LSO A" fields on the Circuit Identification window will be enabled. This will be effective for ASR orders with or without ACI forms, where the Priloc may be an end-user. When the order is "special access", the Priloc must be an ACTL; thus, editing of the LSO is not allowed on the order.

DB

Issue ID: 75459

Internal CR#: 171201

Problem: For a 6.0.3 database upgrade, the Setup Guide states that the prodfix SQL master script starts with a capital 'M', but the code that was delivered contained a lower case 'm'. 

Resolution: The file was renamed with a capital 'M.'

Engineering

Issue ID:  

Internal CR#: 171388

 

Problem: The IP Technology Module software option was not functioning correctly. The IP network templates were available to all customers, regardless of whether or not they purchased the technology module. 

Resolution: Now, only customers who purchased the IP Technology Module will have access to the IP templates.

Engineering

Issue ID: 75791

Internal CR#: 148111

Problem: When trying to provision a circuit to ride a network, a variety of errors can occur.  Out of memory, null pointer exception, and array index out of bounds errors have all been seen after picking the entry and exit nodes and clicking Next to find available routes. 

Resolution: Path Analysis can now handle much larger networks without errors. However, it can still take a long time to provision when the hops allowed exceed 35 hops.

Engineering

Issue ID: 75821

Internal CR#: 171330

Problem: In existing embedded optical networks, some of the connections are not appearing on the canvas. Also, when you try to embed an optical network into a new optical network, none of the connections appear.  

Resolution: When an optical or SONET network is embedded in Optical, the connections are now displayed. The user now sees all the connection drawings in the embedded networks. If the user tries to embed an optical network into a new optical network, the new network must be saved, closed, and reopened for the connections to display correctly.

Engineering

Issue ID: 74533

Internal CR#: 172769

Problem: Circuits are not appearing in Equipment Inventory, but they do have an equipment assignment block on their design lines. 

Resolution: Logic in the Group Assignment process was changed to correctly filter out equipment that circuits have already been assigned to. This prevents the equipment assignments from being overlaid, which resulted in the difference between what was shown in the design lines and what was in Equipment Inventory.

Engineering

Issue ID: 76043

Internal CR#: 174627

Problem: In the SONET module in Network Systems, two users can open the same SONET ring without receiving a message that the system is locked by another user.  

Resolution: A lock will occur when a SONET ring is opened.  Other users will have the option to open the ring in 'View only' mode.

Engineering

Issue ID: 75420

Internal CR#: 177205

Problem: When viewing the connection properties for a connection that's in an embedded optical network, the hierarchy is missing. The connection should have circuit positions below it in the hierarchy, but they are not displaying on the properties window. 

Resolution: The optical hierarchy is loaded with data when the optical network is embedded.

Engineering

Issue ID: 76649

Internal CR#: 177342

Problem: The system is not allowing the reuse of an A or Z TGN from a disconnected or cancelled circuit. 

Resolution: You will now be able to reuse an A or Z TGN that was previously on a disconnected or cancelled circuit.

Engineering

Issue ID: 76409

Internal CR#: 177571

Problem: If you create an EWO with one new circuit and close the EWO, there are two issues for the completed order. Issue 2 shows to be Pending for the completed order. 

Resolution: The Engineering Work Order logic was modified to stop the creation of a new issue when the order is Due Date Complete or Order Complete.

Engineering

Issue ID: 76871

Internal CR#: 179701

Problem: When printing the TCO Report from within an ASR or from the Trunk Group Information window, you receive an error message and the application shuts down. 

Resolution: When printing the TCO Report from within an ASR or from the Trunk Group Information window, the report will print without displaying the error message and causing the application to crash.

Engineering

Issue ID: 76746

Internal CR#: 179970

Problem: When network assignments are removed, circuits are getting marked as Pending Disconnect on optical networks when there is no open order associated with the circuit. 

Resolution: If an order is already Due Date completed, the block can be deleted. You can now go back to delete these pending disconnect blocks and the assignments.

Engineering

Issue ID: 76881

Internal CR#: 180491

Problem: You receive an error message when you click the "Go To" button during the auto-build process for a connection. After the error, the application crashes. 

Resolution: The code was modified to resolve the null object reference. The 'GoTo' window can now be used as designed.

Engineering

Issue ID: 76405

Internal CR#: 175743

Problem: The EWO summary does not refresh when changing circuit status, but automatically refreshes when other data is changed. 

Resolution: The Engineering Work Order logic was modified to refresh when the Connection Design window closes.

Engineering

Issue ID: 76827

Internal CR#: 179179

Problem: There are inconsistencies in the way the A and Z Point Code drop-downs for an Engineering Trunk Group function. 

Resolution: The point codes were changed to smart drop-downs to resolve another reported issue regarding performance. The A and Z point code drop-downs (in Engineering Trunk Group) are now more consistent in their selections and functionality.

Engineering

Issue ID: 73844

Internal CR#: 172766

Problem: A two-six code was entered on a PSR order, but it did not appear on the CLR. 

Resolution: Now, the two-six code is populated on the Properties tab of the Connection Design window.

Engineering

Issue ID: 76389

Internal CR#: 174853

Problem: You received Java errors when attempting to open the design for disconnected trunks. 

Resolution: The trunks being opened no longer had an associated trunk group. The remedy for this is two fold.  A script will delete all cancelled or disconnected trunks that do not have a corresponding trunk group.  In addition, all related circuits will be removed when deleting a trunk group from the trunk group query window.

Engineering

Issue ID: 76289

Internal CR#: 175572

Problem: When looking at a Trunk Group on the Trunk Group Information window, TCICs are being re-sequenced on the Trunk Group Information TCIC tab, even though the TCICs are stored correctly in the database. 

Resolution: When looking at a Trunk Group on the Trunk Group Information window, TCICs will no longer be re-sequenced on the Trunk Group Information TCIC tab when the window is not updateable (read-only).

Engineering

Issue ID: 76027

Internal CR#: 177757

Problem: Trunks that were added to an order and given TCIC and A/Z member numbers before being removed and re-added to the order, show up under the assigned trunk circuit list and the unassigned trunk circuit list (TGN and Member Assignment tab on the Trunk Group Info window).  It appears that when the trunks were removed from the order, they were not totally removed or that when they were added again, the code did not see that some of the needed information already existed. 

Resolution: The TGN and Member Assignment tab on the Trunk Group Information window will not display duplicate trunk circuits when the trunk group deleted contained TGN information and the trunk circuits are re-added to the same order. The "Assigned Trunk Circuit "data window will no longer display disconnected or canceled circuits.

Engineering

Issue ID: 76002

Internal CR#: 170251

Problem: A user with Read Only security permissions to the w_networkspec_maint window is able to create duplicate network templates as well as a reference template for an existing network template. 

Resolution: The system was not checking access permissions when populating the popup menu for the Search/Hierarchy Option for Network Templates. This has been corrected. Users with Read Only access to this window will not be able to create duplicate templates and reference templates, or delete templates.

Engineering

Issue ID: 76004

Internal CR#: 170362

Problem: Even though the Network Template Maintenance window is set to Read Only, the user can add new Component Types or Connection Specs. 

Resolution: Users with Read Only access can no longer add or delete component types or connection specs.

Engineering

Issue ID:

Internal CR#: 175461

Problem: When creating a new Component Type and you do not enter a Component Type or Component Type Name, an error message displays using the incorrect term, Element, instead of using the term, Component. 

Resolution: The error message will display using the correct term, which is "Component".

Engineering

Issue ID: 75859

Internal CR#: 171186

Problem: In a DLC Network, the user is allowed to delete an equipment association to an element even if the equipment's ports or its installed equipment's ports have been used in the DLC provisioning assistant.  

Resolution: In a DLC network, you are no longer able to delete an equipment association to an element if the equipment's ports or its installed equipment's ports have been used in the DLC provisioning assistant. To delete the association, you must first remove all provisioned DLC assignments to that equipment and element.

Engineering

Issue ID: 75740

Internal CR#: 149016

Problem: The user navigates to Network Locations and on the Network Location Search window, right-clicks the mouse to bring up the popup menu options. One of the menu options (that is disabled) is "User Data."  The user highlights this grayed out (disabled) option with the mouse. Immediately, the application displays three fatal error messages and the application terminates. 

Resolution: The code was changed so that clicking a disabled menu option does not cause the application to terminate.

Engineering

Issue ID: 75798

Internal CR#: 172094

Problem: The circuit status does not change from 'In Progress' to 'DLR Issued' when using the Connection Design Print window from within Connection Design. 

Resolution: The circuit status now updates appropriately.

Engineering

Issue ID: 76900

Internal CR#: 181003

Problem: In 5.2, when you right-click the Element Info/Name field, the Set Criteria option is available. This option is not available in 6.0.4. 

Resolution: Now, the Set Criteria pop-up menu will appear.

Engineering

Issue ID: 75297

Internal CR#: 175019

Problem: When trying to auto-build a circuit on a network system from a STM16 - VC4 - TUG - VC12 - EC1, an error occurs on the auto-build of the VC12s saying that "More than one circuit has been defaulted to " xxxx ecckt.  This is working correctly as the path around the network needs the same name. The validation should allow for this. 

Resolution: Modified the code to handle mixed service types of VC and TUG.

Engineering

Issue ID: 76598

Internal CR#: 179972

Problem: The application is allowing circuits to be mapped to a port that has been reserved/blocked. 

Resolution: When a port in the cross-connect chain is blocked and reserved, circuit position mapping should not be allowed. You will receive a message box when you make an assignment and the enabled ports are cross-connected to blocked ports or reserved ports. Validation will also occur when trying to add a cross-connect from enabled ports to blocked or reserved physical ports.

Engineering

Issue ID: 75703

Internal CR#: 181494

Problem: You are allowed to provision to a Pending optical network, and Pending optical elements. 

Resolution: You will only be able to provision to In Service optical networks and In Service optical elements.

Engineering

Issue ID: 74975

Internal CR#: 143582

Problem: It takes too long for the Group Print window to open for large trunk groups. 

Resolution: To decrease the time it takes the Group Print window to open from the Service Request Connections window, the method used to pass data to the print window was changed. An order containing 576 trunk circuits that previously took over a minute to open the print window, now takes only seven to eight seconds to perform the same action.

Engineering

Issue ID: 74978

Internal CR#: 148700

Problem: Need to improve the performance of the group assignment functionality. 

Resolution: The main scenario affecting the performance of group assignment involved group assigning trunks with facility assignments and equipment embedded within the facility blocks. The code was changed to call a stored procedure to build the facility blocks and thereby reduce the number of calls to the database from the client. This results in a major improvement for the facility group assignment scenario.

Engineering

Issue ID: 75701

Internal CR#: 171002

Problem: When working the CKTID task, the user selects OTS circuit format. Once that is selected, the "A" location is grayed out and unavailable for selection. 

Resolution: The LSO drop-downs will always be enabled. They will be defaulted if possible, but they will always be enabled so the user can change them.

Engineering

Issue ID: 75701

Internal CR#: 172010

Problem: When on the CKTID task, the user selects an OTS circuit format. Once that is selected, the "A" location is grayed out and unavailable for selection. 

Resolution: The LSO drop-down lists are now always enabled. They are defaulted if possible, but are enabled so the user can change them.

Engineering

Issue ID: 75600

Internal CR#: 173957

Problem: In a multiple pending order scenario, if there is a pending disconnect assignment for order B under order A and order B is sup-cancelled, the cancel change process does not remove the pending disconnect assignment for order B. 

To recreate:  Create order A for a circuit and assign it to a piece of equipment, but don't complete RID task. Then, create order B from order A and disconnect the equipment from order A and assign the circuit to a different piece of equipment, but don't complete RID task. The equipment must be cross-connected for this problem to occur. 

Resolution: In a multiple pending order scenario, if there is a pending disconnect assignment for order B under order A and order B is sup-cancelled, the cancel change process will now remove the pending disconnect assignment for order B.

Engineering

Issue ID: 74814

Internal CR#: 173958

Problem: When using multiple pending orders, if you go in to create a new issue for a circuit and get to the Design Issues window, choosing Create New does not correctly change any previous issue for that circuit.  It leaves it as Pending, which makes it difficult to determine which issue is the correct Pending issue. 

Resolution: On the Design Issues window, the Create New option will only be enabled if the circuit is of a New activity.  Also, if an issue has already been created for the particular order you are currently working on, the Design Issues response window will only list the issue already created for this order and nothing else. Also, the Create New button will be disabled. If you select Create From, a new Pending Issue will be created for this order, and the old Pending issue will now be overridden.

Engineering

Issue ID: 76668

Internal CR#: 177439

Problem: Once a group assign job is completed in the background processor, the DLRD/RID group print functionality will not work. The task is not released back to the user's work queue. 

Resolution: The background processor will release the task back to the user after the group assignment logic has been completed.

Engineering

Issue ID: 76157

Internal CR#: 179874

Problem: Occasionally, the application shuts down after adding a second entry to the Ownership tab in Ownership of Inventory prior to saving. 

Resolution: The application will no longer shut down when saving after modifying the second entry on the Ownership tab of Ownership of Inventory.

Engineering

Issue ID: 71617

Internal CR#: 180465

Problem: The reconciliation process will not start after the circuit ID has been changed at the order entry level for supp corrected orders. 

Resolution: Saving a circuit after its circuit ID has been changed on a supplement, excluding cancel, to a new order will cause the reconciliation process to execute.

Engineering

Issue ID: 73317

Internal CR#: 182254

Problem: While using the SONET network provisioning assistant for provisioning a SONET network, an error was encountered. 

Resolution: To avoid the null pointer exception error, added appropriate checking to ensure a working path was found before continuing.

Engineering

Issue ID: 76936

Internal CR#: 187620

Problem: It appears that jobs run through the Background Processor are missing commit logic. The Background Processor should not cause database locking issues. 

Resolution: Added necessary commits to the Background Processor logic.

Engineering

Issue ID: 76442

Internal CR#: 176433

Problem: The Group Assign window doesn't display CLT circuits in order, so the user cannot use the Sequential Assign process. 

Resolution: The Group Assign window will now display CLT circuits in order.

Engineering Work Order

Issue ID:

Internal CR#: 173306

Problem: When you create a new circuit on an EWO and click OK, you get the following database error: 1400: ORA-01400 cannot insert NULL into (ASAP; SRSI_SR_LOC,SERV_ITEM_ID).  This error only occurs for non-US customers. 

Resolution: You can now create a circuit via an EWO without a database error occurring.

Engineering Work Order

Issue ID: 76412

Internal CR#: 176456

Problem: Group Assignments and Group Disconnects can be made on an EWO after the EWO is completed. This is inconsistent behavior considering this is not an option in ISR, PSR, or ASR orders. 

Resolution: The Group Assignment and Group Disconnect links will not be visible for view-only or read-only EWO orders. This encompasses completed EWOs.

Engineering Work Order

Issue ID: 76395

Internal CR#: 176881

Problem: There is nothing in the application that indicates to the user that an EWO order is In Progress. 

Resolution: The Work Queue Task List was modified to display 'EWO' (in column 'cf_type_of_sr_txt') for tasks belonging to an Engineering Work Order. In addition, the bitmap field was modified to display a blue notepad bitmap to indicate tasks belonging to an Engineering Work Order.

Equipment

Issue ID: 76468

Internal CR#: 177194

Problem: Equipment installed differently using an EWO appears differently in the Equipment Inventory. If the user chooses to install from equipment specs, the equipment does not appear on the EWO. 

Resolution: The Engineering Work Order logic was corrected to properly add the equipment to the EWO when the user chooses to install from equipment specs (method 1 - using the "Equipment Specs" right-click option from the Equipment Inventory Search window).  

The "inconsistency" between the copy of equipment (method 2) versus adding new equipment (method 3 - using the "add..." right-click functionality on the "Installed Equipment" treeview window) is due to the "Name" and "Net Loc (Equipment)" values being copied over when the copy method was performed. When the add method was performed, the "Name" and "Net Loc (Equipment)" values were not entered in by the user.

Equipment

Issue ID: 75817

Internal CR#: 180097

Problem: The Assembly Report does not open up in PDF format so that users can print it out. 

Resolution: The logic in the Assembly Report that was preventing it from displaying the PDF report was corrected.

Equipment

Issue ID: 75389

Internal CR#: 055828

Problem: The Geographical Area drop-down menu does not consistently appear on the Location Search window. 

Resolution: The Country, Geographical Area, and City column label names were not set appropriately to match with the corresponding columns. This was corrected by naming each column with the appropriate name. 

Equipment

Issue ID: 76598

Internal CR#: 179975

Problem: There seems to be a problem with Equipment Reservations in M6. Equipment that is mapped to a circuit position can be reserved, and the circuit position can be mapped to a circuit in spite of the reservation. 

Resolution: When a port in the cross-connect chain is blocked and reserved, mapping should not be allowed. You will receive messages when you make assignments but the enabled ports are cross-connected to blocked ports or reserved ports. Validation will also occur when trying to cross-connect enabled ports to blocked or reserved physical ports.

 Added a filter in the reservation query window. When physical ports are mapped due to a cross-connection to enabled ports, these ports cannot be reserved.

Equipment

Issue ID: 76045

Internal CR#: 173230

Problem: When copying 'Under Construction' equipment, the application asks if you want the Install Date to be today's date or the original date. The install date should always be blank for equipment under construction. The message is misleading since the Install Date should be blank. 

Resolution: When copying 'Under Construction' equipment, the Install Date will be Null and no message will be displayed.

ISR

Issue ID: 76604

Internal CR#: 176622

Problem: The Notes section on the order printout is too big.  If you print the Auto notes, it takes up too much blank space on the printout. 

Resolution: Now the Auto Notes do not take up too much space on the printout.

ISR

Issue ID: 76605

Internal CR#: 176624

Problem: Some fields on an ISR Trunk order printout need to be widened because data is getting cut off. 

Resolution: The width of the columns 'Associated Provider Order Number' and 'Trunk Circuit Id Code' have been increased to resolve this issue.

ISR

Issue ID: 76623

Internal CR#: 176745

Problem: You receive a database error when you use the full End User field on the ISR Multipoint Service Leg tab. 

Resolution: The End User field has been changed to accept 25 characters.

ISR

Issue ID: 76715

Internal CR#: 178080

Problem: If you enter an ISR where the PRILOC and SECLOC CLLIs are the same, deleting one of the locations removes both from the order. 

Resolution: Now, the deletion of locations functions correctly.

ISR

Issue ID: 76716

Internal CR#: 178186

Problem: The Billing Indicator field on an ISR is disabled when you choose X-Broadband Services as the Request Type, and then save, close, and reopen the ISR. 

Resolution: The existing code was written to disable the Billing Indicator field when opening the Broadband ISR. The new code changes will enable the Billing Indicator field when opening the Broadband ISR.

ISR

Issue ID: 76751

Internal CR#: 178343

Problem: On an ISR, the Activity field is disabled as soon as you save the Administration tab.  You must close and reopen the order to enable the field. 

Resolution: Now, the Activity field remains enabled even though the Administration tab is saved. The field will not be disabled until circuits are assigned.

ISR

Issue ID: 76744

Internal CR#: 178274

Problem: When you create a new Special ISR and add CLLI locations, you receive an error message. 

Resolution: You no longer receive an error when creating a Special ISR and adding CLLIs.

ISR

Issue ID: 76969

Internal CR#: 180483

Problem: When you enter TCIC numbers on the Trunk Group Information of an ISR, the 'skip 4' message occurs intermittently.  

Resolution: You now consistently receive the 'skip 4' message when you enter TCIC numbers.

ISR

Issue ID: 76767

Internal CR#: 178443

Problem: The Order Complete Date is not being populated for orders that are supplement canceled. 

Resolution: Now, the Order Complete Date will be populated for supp canceled orders.

ISR

Issue ID: 75536

Internal CR#: 169612

Problem: The customer created a trunk group and assigned it to an ISR order, and then cancelled out of the window. The window is not refreshing and the customer is under the impression that the assignments were not created. 

Resolution: Added a "re-retrieve" of the circuit information for the order following the close/cancel of the trunk circuit identification window.  The trunk group on which the action was taken will be immediately displayed.

ISR

Issue ID: 75604

Internal CR#: 170509

Problem: If you change the ECCKT of an existing trunk group on a order for a large number of trunks, it takes a very long time to add the trunks to the order.  In one example, 3,000 trunks took 20 minutes to be added to the order. By comparison, creating a new order for 3,000 trunks took just 2 minutes. 

Resolution: Moved the code for the validation for trunk circuits to a package and stored procedures.  This eliminates the network latency involved in transmitting large results sets to the client machine for processing.

ISR

Issue ID: 75453

Internal CR#: 181018

Problem: Trunk augment information is not deleting correctly when canceling the augment order.  

Resolution: A correction was made for ISR so that when you do a trunk augmentation and/or change with a "new" activity order, you can properly supp-cancel the order by:

- Deleting the trunk group from the order via the Trunk Circuit tab. This action will reset values for the trunk group properly as long as no multiple pending order (MPO) situation exists.

- Supp-canceling the order.

- If in an MPO situation, you will be informed and notified that you must reset the trunk group values (ECCKT, location, TCICS, point-codes, etc.) manually (via that order) or another order. You can choose to continue the deletion, or cancel that action. Even if MPO, you do not need to remove any "new" trunks added. The "delete" action via the circuit list will take care of that.

ISR

Issue ID: 75960

Internal CR#: 169940

Problem: Trunk ranges are not displaying properly on ISR orders. 

Resolution: The data window that is used for the trunk range selection was altered so the From and To range columns are fully visible when the scrollbar appears. This prevents the columns from shifting when tabbing between columns.

ISR

Issue ID: 76050

Internal CR#: 170958

Problem: The ISR Billing Indicator field no longer defaults to None for Request Types of Specials. 

Resolution: The code was changed so when a user selects a Request Type of Special or Broadband Services, the Billing Indicator field defaults to None.

ISR

Issue ID: 76064

Internal CR#: 171205

Problem: When you modify ISR MSL information, the address information is blanked out. 

Resolution: When changing the 'end user' column information in the "Multipoint Service Leg Maintenance" window, the existing script was resetting the address information.  Code changes were made to resolve this issue.

ISR

Issue ID: 76683

Internal CR#: 177599

Problem: On a trunk order, user received the message 'Would you like to skip TCICs ending in 97,98,99,00?', when the TCICs created only went up to 96.  This message should appear for the next TCIC assignment for the given point codes. 

Resolution: Changes were made in the code so the system will not display the error message at the incorrect time.

ISR

Issue ID: 76971

Internal CR#: 180245

Problem: The LSO CLLI on an ISR is pulling from the City field rather than the NPA/NXX. 

Resolution: Changes were made to satisfy the following conditions:

1) Keep the default of the LSO NPA/NXX and CLLI as is

2) If the defaulted LSO CLLI is not what would have resulted if the default LSO NPA/NXX were used to determine the CLLI, display a message such as

"The LSO CLLI was defaulted based on the value established by a previous order.  However, this CLLI does not match the ACTEL/WKTEL that is used on this order.  Do you want to set the LSO based on this order's values?" --> "Yes" or "No"

3) If user replies "Yes", set the LSO CLLI to what would have resulted by using the NPA/NXX determined.  Otherwise, keep the LSO as initially defaulted.

LSR

Issue ID: 77319

Internal CR#: 185044

Problem: The user uncommented the LSRSERVER entry in the gateway.ini file to have the LSRSERVER.ior file created, but the file did not get created. 

Resolution: Altered the MSS core API startup so the LSRSERVER entry in the gateway.ini is recognized (not ignored) for M6.  It was previously bypassed.

PSR

Issue ID:

Internal CR#: 176310

Problem: The Customer Profile does not show circuits that are In Service, but that were never on an order. 

Resolution: The SQL has been modified and circuits (In Service) that have never been on an order will now be shown in the Customer Profile.

PSR

Issue ID: 76152

Internal CR#: 172142

Problem: You receive an error message and are booted out of the system when attempting to print notes from the Notes tab of the Order Information section of a PSR. 

Resolution: This problem was caused by a wrong column name being mentioned in the print object. The code was changed to specify the correct column name for the print object.

PSR

Issue ID: 74349

Internal CR#: 179412

Problem: Some incorrect text (&#39) is appearing on the Customer Profile title bar. 

Resolution: The thin client page was modified to filter out the control characters before displaying the page to the user. The control characters will not appear in the title.

PSR

Issue ID: 76895

Internal CR#: 179959

Problem: When you retrieve a customer, open Customer Profile, and click the Network Systems link, you receive an extensive error message. The first part of this error message is: 'The server encountered the following Exception: java.sql.SQLException: ORA*01652: unable to extend temp segment by 128 in tablespace TEMP at oracle.jdbc.driver.' 

Resolution: The SQL query causing the Oracle error was tuned. The Network Systems will now be displayed and the Oracle error will not appear.

PSR

Issue ID: 75733

Internal CR#: 169247

Problem: The following error appears when attempting to view All In Service Values for a Trunk product on a PSR:
SP_TGUD ORA-06502: PL/SQL: numeric or value error occurred do you wish to continue retrieving History Data?
 

Resolution: The dynamic SQL built for Trunk Group User Data had a limit of 1,000 bytes. The limit was increased to 2,000. Now there is no error when viewing the Service Item History.

PSR

Issue ID: 76893

Internal CR#: 180138

Problem: Alphanumeric or numeric valid value fields on a PSR do not stop you from entering more than the maximum number of characters in the field. 

Resolution: Logic was added to monitor the data as it is entered and disallow entry after the character limit is reached.

PSR

Issue ID: 76859

Internal CR#: 180441

Problem: A user created a new PSR. The first time they clicked the drop-down for Business Type (User Data Information), the system populated a value of "3178" in the field. This value is not even a part of the drop-down list.  The user then clicked off this field, and the value changed to "NONE". The user was able to go back to the drop-down and make a selection. The "3178" value was not in the list. 

Resolution: The drop-downs in PSR User Data Information will now display the values correctly. 

PSR

Issue ID: 76678

Internal CR#: 181442

Problem: When creating a new PSR, the user selected a customer, entered a desired due date and organization under Order Information, and clicked on 'Services'. An error message appeared - 'Required value missing for 'Order Activity'. Please enter a value.' The user clicked OK on the error message box, and all of the order information was then blanked out.  

Resolution: You no longer receive the error message.

PSR

Issue ID: 75952

Internal CR#: 170240

Problem: Users granted Read Only access to the Customer Account Search window can make updates to the window.  

Resolution: The code was changed to prevent users with Read Only access from updating the window.

PSR

Issue ID:

Internal CR#: 145525

Problem: PSRAPI exportPSR_v3, exportNGNPSR, exportServItem_v3 and exportNGNServitem:
Execute one of the above APIs for an order with a service location and service items below the service location. The location ID is not exported for the service items, but the address ID is for the following two scenarios:

1. If an existing service location of type 'PRILOC' or 'SECLOC' is added to the order as the service location.

 2. If the service item is a circuit with end user locations as the PRILOC or SECLOC. 

Resolution: 1. For the first scenario, the correct location ID and address ID are now exported.  

2. For the second scenario, the location ID and address ID will be blank. These fields are only populated for the parent that is directly below the service location. These fields are blank for all children except for children that are strictly PREMISE products and have location information stored in the MetaSolv database (e.g., Line).

PSR

Issue ID: 76981

Internal CR#: 183190

Problem: When using multiple pending orders (MPO), you are able to complete the Due Date task of subsequent change orders before the new order. 

Resolution: The logic to complete a task has been modified to make sure the MPO validation at Due Date is run. This validation will not allow you to complete the DD task if a service item is on another open PSR order as New.

Technical Framework

Issue ID:

Internal CR#: 176462

Problem: When the calendar control is used, the control pops up a separate window (from the application) that causes some security-related script errors while working in EWO. 

Resolution: Instead of popping up a separate window for the calendar, the control was rewritten so that the calendar now shows up in an IFrame that is part of the parent document and should avoid the java script/security errors caused by the popup window.

Technical Framework

Issue ID:

Internal CR#: 175471

Problem: URLNaming service was not properly registering the servers from different applications.

Resolution: Modified the framework to allow the applications to properly register their servers.

Technical Framework

Issue ID: 76726

Internal CR#: 179011

Problem: The startup script for the Proxy Server uses the console and does not run as a background process. 

Resolution: Instructions were added to the Proxy Server appendix in the Setup Guide for editing the startup script to run in background mode.

Technical Framework

Issue ID: 75559

Internal CR#: 177494

Problem: You cannot replace the generic MetaSolv Software corporate logo with your own company's logo. This is caused by a defect with BEA 8.1. 

Resolution: To get around this defect, the weblogic.xml file in the nur.ear was changed. Additionally, the start scripts used to start the application server now reference a patch file CR183350_810sp3.jar from BEA.  Also, the images directory under the domain directory is now logo/images instead of just images. As a result, your company logo will now display properly in the application for Windows and Unix installations.

Technical Framework

Issue ID:  

Internal CR#: 186612  

 

Problem: The default for the Oracle DB connections was set to 10. 

Resolution: The default for the minimum Oracle connections has been set to 1. This will need to be adjusted to the appropriate value for your environment. The maximum value is set to 100. This should also be adjusted for your environment.

Technical Infrastructure

Issue ID: 75801

Internal CR#: 169935

Problem: The customer was unable to query for a network location when the street name contained lower case letters. The Query field currently defaults to upper case. However, even if lower case letters were allowed, users would not always be able to find a location because they might not know the case of the address. 

Resolution: Network location addresses now contain all upper case letters.

Trouble

Issue ID: 77161

Internal CR#: 187178

Problem: When attempting to transfer or refer a trouble ticket, the Assigned To drop-down does not show any names contained in the selected organization. The originally chosen name is displayed as the numeric ID instead of the text representation. The drop-downs work fine on a new ticket, but do not work on the transfer/refer windows. 

Resolution: The problem occurred when the Responsible Organization Assigned To and Administrative Organization Assigned To fields were changed to be required fields in Trouble setup (Required Ticket Fields).  When this happened, the drop-downs for Admin Org Assigned To and Resp Org Assigned To on the New/Edit ticket and Transfer Administration/Internal Referral windows would show up empty, which would cause the number to display.  The code was changed so that the drop-down is not empty when setting either of these fields to required.  This eliminates the number showing up in these fields.

Trouble

Issue ID: 76137

Internal CR#: 177667

Problem: Externally Referred tickets can be canceled, cleared, and closed without verifying the external referrals. 

Resolution: Now, a ticket's external references will be verified while canceling the ticket, similar to the clear ticket option.

Trouble

Issue ID: 76875

Internal CR#: 180690

Problem: Some user-defined views are not retrieving tickets into the Ticket Queue window.   

Resolution: Now, the Ticket Queue view filters and sort work for hidden columns too. The query performance has also been improved for the view.

User Setup

Issue ID: 75781

Internal CR#: 169424

Problem: The Telephone Number Threshold Percentage Report seems inaccurate.  When the user generates the NPA NXX Utilization Report with different percentages in the Threshold Percentage field, the results do not change. Also, the report only displays a blank space where the % threshold should appear. 

Resolution: The application was not using the data entered by the user as a parameter to populate the report. This was corrected by modifying the data window's SQL and modifying the report to show the Threshold percentage on the header.

User Setup

Issue ID: 75078

Internal CR#: 145457

Problem: When a user or group is given Read Only access to the Transmission Bit Rates window, they are able to add or modify data on the window. 

Resolution: The code was changed so users with Read Only access can no longer add or modify data.

User Setup

Issue ID: 76150

Internal CR#: 171991

Problem: When permissions for the  IP Addresses-External window are set to No Access, the user cannot select the 'Select Customer on New Product Service Request (PSR)' link. 

Resolution: The 'Select Customer' and 'IP Addresses - External' links bring up the same window (w_customer_account_query_response). Assigning permissions for the window through one link will affect the other, since security permissions are associated with the "w_customer_account_query_response" window rather than the link (area) from where it is called. If the window "w_customer_account_query_response" is set to "No Access" through security, then both links are affected the same way.  

You will now be able to set up check points --and access the External IP address window from a New PSR (choosing Select Customer) and as well as establish security for accessing this window from the Navigation bar (using a password).   You should not set 'No Access' to the window, if you want to use the checkpoint functionality.

User Setup

Issue ID: 76123

Internal CR#: 172407

Problem: There are inconsistencies between the New and New From options to create a new Security group. There are two inconsistencies:  

1. The number of characters allowed. (Between 4 - 8 characters allowed using the New From option.)  (Between 1 - 16 characters allowed using the New option.)  

2. The type of characters allowed. (Spaces are not allowed using the New From option.)  (Spaces are allowed using the New option.) 

Resolution: Now the restriction of the New From option matches that of the New option when creating a new Security group.

User Setup

Issue ID: 76003

Internal CR#: 170257

Problem: A user with Read Only access is able to Remove a Lock for a circuit via Network Templates even though the user permissions are set to Read Only for the 'w_nst_row_in_use' window. 

Resolution: Now, a user with No Access to this window is unable to remove locks. Instead, a message appears. For users with Read Only access, it will appear as though the lock was removed, but it was not. When you reopen the window, the lock reappears.

User Setup

Issue ID: 75919

Internal CR#: 171393

Problem: When in Security, you cannot print the entire permissions list for a user or group. Instead, you must scroll through the list and print each screen. The Security Admin would need to print many screens to capture all the data in hardcopy.  This is inconsistent with the way the rest of the system operates for printing on-screen data. 

Resolution: You can now print the entire list of permissions for a group or user in the Security Permissions window.

User Setup

Issue ID: 76279

Internal CR#: 173965

Problem: When Security is set as Read Only for certain windows and a user accesses the windows, the READ ONLY message appears at the top of the windows twice. 

Resolution: Now the READ ONLY title appears only once on a window. 

User Setup

Issue ID: 76377

Internal CR#: 176469

Problem: When you access Security for Rules and Behaviors, the window name is the same (w_rulesandbehaviors) when you query for existing rules and behaviors as when you attempt to create a new rule. This behavior is inconsistent. 

Resolution: All Web-based windows show the same name along with the name of the jsp next to it. The problem was that the list window was not showing the name of the jsp as the ole object did not have focus. So, only the name of the window was being shown. Now for the list window, you will see the name of the window as w_ rulesandbehaviors and the jsp as rulelist.jsp. 
Note: The properties of a link will show the action as coded- it cannot show the .jsp.

USO

Issue ID: 76080

Internal CR#: 188103

Problem: When you add a USO order, then add information on the MSL and press OK, the information doesn't appear on the Multipoint Service Legs view. 

Resolution: During MSL entry, if the option is End User location, the system did not update the end user location ID in the location_id_2 field in the multipoint_service_leg table. If it is a CLLI code, the system was populating the CLLI code in the location_id_2 field.  The code was changed to update the location_id_2 field when the MSL entry is an End User location, as well as to update it when the  CLLI option is selected.

USO

Issue ID: 76055

Internal CR#: 170964

Problem: When you query by USO / CCNA, the results window appears to be cutoff. 

Resolution: Now when you query by USO/ CCNA, the Order Detail and Tasks appear on the results window properly.

USO

Issue ID: 76057

Internal CR#: 171110

Problem: When you copy a USO where the ACNA is set to ZZZ, the BN2 information doesn't copy. 

Resolution: When performing a New From on a USO, the code was checking the CCNA value. It was corrected to check the ACNA value.

USO

Issue ID: 76077

Internal CR#: 172245

Problem: On the ILAM for USO orders, the Exchange field is populated by the Telephone Number, not the LSO. 

Resolution: The existing code had the value of 'End User Location Access Tel Number' in the 'Exchange' field in the 'Loop Assignment and Makeup Request' window.  Changes were made to display the 'LSO' in the 'Exchange' field instead of the 'Access Tel Number'.

USO

Issue ID: 76465

Internal CR#: 175623

Problem: You are unable to select BN2 on the USO Billing Tab when the ACNA = ZZZ. This happens when the Access Customer Address is missing the secondary name. 

Resolution: If you want to populate the Billing Name2 field on the Billing tab, you must enter the ACNA as well as the ACNA Name. According to the ACNA Name, the BN2 field is getting populated. This is working as designed.

After you enter a valid ACNA that is an access customer name abbreviation, the system will retrieve and validate the access customer name in the ACNA Name field. If the record count is 1, it will retrieve the ACNA name and it will disable the ACNA Name column. If the record count is more than 1, it will enable the ACNA Name column and allow you to select the ACNA Name. Here, you must select the ACNA Name from the drop-down list by populating any search criteria. Only then will the system enable and populate the BN2 field.

USO

Issue ID: 76624

Internal CR#: 176774

Problem: You get an error message when you enter the full length of the BN1 field on a USO. The error message doesn't clearly explain what the problem is. 

Resolution: Now the BN1 field does not allow more than 25 characters. You can enter all 25 characters in the BN1 field and populate all the related billing information without getting an error.

USO

Issue ID: 76443

Internal CR#: 177471

Problem: The ILAM Remarks are being copied when you use New From on an existing order with existing remarks. 

Resolution: The code in the ASR New From stored procedure is now changed to exclude the remarks for the ILAM task.

USO

Issue ID: 76765

Internal CR#: 178467

Problem: When entering a USO, the system is performing a validation on the first character of the Order Number, and you are unable to proceed. This is no longer a valid validation. 

Resolution: When entering a new USO, the first letter validation of the Order Number will no longer occur.

USO

Issue ID: 77095

Internal CR#: 181817

Problem: When you attempt to copy an existing USO order using the New From function, the system displays a Stored Procedure error. This is currently happening on orders where the PRILOC and SECLOC are set to CLLI.   

Resolution: You no longer receive a Stored Procedure error when using the New From functionality.

USO

Issue ID: 76345

Internal CR#: 174709

Problem: When you supp cancel a USO that has circuits attached, you cannot remove the circuit or add tasks if you close the order for any reason. 

Resolution: You can now remove (delete) the circuits from a SUP Cancel USO request.

Work Management

Issue ID:

Internal CR#: 180998

Problem: New functionality needs to be added to gateway events to support a new table that will house work order detail data that will be linked to gateway events. 

Resolution: New logic was added to WDI API to support the getting and setting of work order details to the new table Integration_Event_Status that will be linked to the gateway event tables.

Work Management

Issue ID: 76235

Internal CR#: 173179

Problem: (None) is not an available option in the Rules and Behaviors drop-downs. 

Resolution: Is_NULL and IS_NOT_NULL are two new operators added to the Rules and Behaviors drop-downs.

Work Management

Issue ID: 75654

Internal CR#: 178894

Problem: When rules are created using "New From", the Before/After property in the Insert Task for behaviors is not being copied. 

Resolution: The code was changed so this property and the checklist items will be copied.

Work Management

Issue ID: 76936

Internal CR#: 185563

Problem: When you work in Work Management, the application becomes unresponsive, the Oracle connections grow and do not shrink, and locks are held on the Oracle database. 

Resolution: When you work in Work Management, after copying service request notes to a customer, the Oracle lock will be released.

Work Management

Issue ID: 75846

Internal CR#: 148976

Problem: If you double-click a column heading in the Work Queue Manager, the action associated with double-clicking the first task in the list is executed. The expectation is that the task list will be sorted, based on the column selected. 

Resolution: Code was added to enable you to double-click a column heading in the Work Queue Manager to sort the tasks based on the column data. You also still have the ability to single-click a heading to sort.

Work Management

Issue ID: 76065

Internal CR#: 171328

Problem: During task generation, if you select multiple tasks and right-click the first task, all other tasks are deselected. 

Resolution: The code was changed to avoid the de-selection of selected rows when you right-click.

Work Management

Issue ID: 76071

Internal CR#: 171352

Problem: When you remove a task that you just added to a new provisioning plan, you receive an error message. 

Resolution: You no longer receive an error when removing a task that you just added to a plan.

Work Management

Issue ID: 76125

Internal CR#: 171867

Problem: When you change the due date on a provisioning plan to be forward-dated, the arrow indicator doesn't immediately change to forward. 

Resolution: When you change the due date on a provisioning plan to forward-dated, the arrow indicator now immediately changes to forward.

Work Management

Issue ID: 76153

Internal CR#: 172410

Problem: When an order is canceled, most of the tasks that were still open have the queue status removed. 

Resolution: The queue status was getting removed only for tasks on canceled ASR orders. For other order types, the queue status of all the tasks is set to S(SUP). Similar changes have now been made to ASR. Now when an ASR is supplemented, all tasks on that order will get a queue status of S.

Work Management

Issue ID: 76352

Internal CR#: 174716

Problem: The LAM Request form that is printed with the ILAM task, cuts off the ISR Order Number if it is more than five characters. 

Resolution: Now the Order Number is fully displayed without any cut off in the printout.

WorkManagement

Issue ID: 76481

Internal CR#: 175869

Problem: When writing Rules and Behaviors, the list of Before/After tasks available is limited to the tasks in the provisioning plan selected as part of the criteria in the expression section. 

Resolution: When writing Rules and Behaviors, the list of Before/After tasks available will now have all the tasks in the provisioning plan selected as part of the criteria in the expression section along with any other tasks that are being inserted as behaviors. (These tasks are the only ones that make sense for being candidates for Before/After tasks.)

Work Management

Issue ID: 76413

Internal CR#: 176715

Problem: The Assign Tasks link still appears after an EWO is completed.   

Resolution: The Assign Tasks link will not be visible for a completed EWO.

Work Management

Issue ID: 76755

Internal CR#: 178283

Problem: User was in Trouble Management and was not set up as a work force employee. The message "Signed on user must be set up as a Workforce Employee to edit trouble ticket templatess."  The word Templates is misspelled. 

Resolution: The typo was corrected.

Work Management

Issue ID: 76110

Internal CR#: 172124

Problem: The user is able to open the CABS billing on the CAD task when the task is in a pending status. 

Resolution: Changes were made for the CAD task such that it behaves the same as the CID task with respect to when the task is allowed to be processed.

Work Management

Issue ID: 76092

Internal CR#: 174712

Problem: You received an error message when generating tasks for an ASR Trunking Disconnect order. 

Resolution: The problem was in the code, while building the sql expression. Code changes were made to correct the error.

MSS 6.0.6

Component

Fixed Issue

Description

ASR

Issue ID: 71409

Internal CR#: 180503

Problem: ASR: ILAM task - the printed LAM request does not reflect the revised due date.

Resolution: Now the printed LAM request will show the correct dates for LAM, RID and DD as entered in the ASR order or from the assigned task date.

ASR

Issue ID: 74276

Internal CR#: 182390

Problem: Unable to change and save a ECCKT on ASR Change order (or Inside Move).

Resolution: Previously, the Circuit Identification window uses the same object to display the circuit detail for order and non-order circuits. Created a separate object for a non-order circuit, this object will open only for a non-order circuit.  Now the user can change and save the ECCKT on an ASR order.

ASR

Issue ID: 77018

Internal CR#: 180988

Problem: The Service Request Search by tasks cuts off the display of the tabs and the Show checkboxes.

Resolution: Now the Service Request search by task window displays all of the column titles and the result page displays completely without any cut off to the tabs and Show checkboxes.  Also, all the views are listed.  

ASR

Issue ID: 77137

Internal CR#: 182392

Problem: Unable to determine which fields relate to the LAM task and which fields relate to the CONF task when adding columns to the Service Request Search.

Resolution: In the existing code, the reason for the duplication of fields in the 'Available Fields' in the objects, there is no difference in the column alias names for (CONF TASK_TYPE  and LAM TASK_TYPE ) and (CONF WORK_QUEUE_ID  and LAM WORK_QUEUE_ID). Now, made changes all the fields to understand the field as LAM_CONF_TASK_TYPE, LAM_CONF_WORK_QUEUE_ID and CONF_TASK_TYPE , CONF_WORK_QUEUE_ID. In the new code change, if we click the View > Format Fields, it is easier to differentiate the fields. The alias name change has been handled for the following cases :

    1. ASR - Service Request  
   
2. ASR - CCNA  
   
3. ASR - Circuit  
   
4. ASR - Location

ASR

Issue ID: 77193

Internal CR#: 183463

Problem: When you open an order in View Only mode, you are still able to edit the Location, MSL and Circuit windows.

Resolution: Now the Location, MSL and Circuit windows will open in view only mode when the order is view only.  

ASR

Issue ID: 72391

Internal CR#: 186279

Problem: Need to validate the presence of a Surcharge USOC.  

Resolution: Now Cabs billing will validate successfully for a Surcharge USOC based on the SURCH category.

ASR

Issue ID: 76089

Internal CR#: 171537

Problem: Bill Prep Validation error messages continue to appear even after the error is corrected.

Resolution: This has been corrected by resetting the validation error report before doing the validation process. Now, the Bill Prep validation error messages do not continue to appear after correcting the errors.

ASR

Issue ID: 77141

Internal CR#: 182419

Problem: Unable to sort by the Circuit ID (Foreign) column at the ASR / Circuit search results window. Unable to sort by the Circuit ID (Foreign).

Resolution: The name of the column header 'Circuit ID (Foreign)' was not named in MetaSolv's standard -- this is the reason the sort was not worked.  New changes made in the object, now the sort works fine for 'Circuit ID (Foreign)' as well.

ASR

Issue ID: 77143

Internal CR#: 182534

Problem: Service Request Search of ASR / Location is not finding orders with an ACTL using the City query.

Resolution: Because of the SQL query it was not working properly. In SQL, where clause SERV_LOC_USE field has checked only with PRILOC condition, it may have ACTL also. The SQL has been modified so that it is working correctly.

ASR

Issue ID: 77144

Internal CR#: 182591

Problem: Query at Service Request Search by ASR / Location retrieves no rows found when you search by the Request Type = V - Broadband Services.

Resolution: Query at Service Request Search by ASR / Location retrieves no rows found when you search by the Request Type = V - Broadband. When you click the 'Search' button, data is getting retrieved, based on the input criteria. But in the retrieval screen, filter criteria are restricting the data where request type is ('A', 'E', 'M', 'S', 'X'). Now the filter criteria have been removed and it is working for all the request types.

ASR

Issue ID: 77106

Internal CR#: 184042

Problem: Service Request Detail for ASR MSL order prints the SECLOC information for the legs and runs into the General Detail section.

Resolution: Now the SECLOC information will be printed in the SECLOC area itself and it will not be carried over to any other section.

ASR

Issue ID: 68785

Internal CR#: 183240

Problem: Unable to select trunks for Disc when SECLOC is blank

Resolution: Previously the application was not checking the company-owned trunk group location to enable the Trunk Nbr's button. It checked company-owned primary and secondary location. Now, the application looks at the TSC field and checks the trunk group location whether it is company-owned or not. The  Trunk Nbr button will be enabled.

Documentation

Issue ID: 202548

Internal CR#: 206741

Problem: Help is not displaying for Service Request Search window.

Resolution: The online Help displays correctly when you click F1 on the Service Request Search window.

Engineering

Issue ID: 74121

Internal CR#: 139328

Problem: After creating a Broadband ASR - The LAM task in Work Management is missing the ECCKT.

Resolution: After creating a Broadband ASR - The LAM task in Work Management is not missing the ECCKT.

Engineering

Issue ID: 76676

Internal CR#: 183231

Problem: Duplicate assignments are appearing on the DLR.

Resolution: The DLR will not show duplicate assignments within a facility block.

Engineering

Issue ID: 76047

Internal CR#: 176328

Problem: When viewing the properties of the schematic design, the hyperlinks are not consistent. The General link is not underlined initially, and clicking on equipment, the link then goes away once the new window appears.

Resolution: All hyperlinks function correctly now.

Engineering

Issue ID: 74967

Internal CR#: 142017

Problem: When multiple virtual connections exist on one order, there is no way to distinguish between them in the CKTID task.

Resolution: For connections, the service item alias will now display in place of the category if there is not a circuit ID assigned.  Once the circuit ID is assigned, the display will show the category as before. This is only for Connections.

Engineering

Issue ID: 77543

Internal CR#: 187022

Problem: The Virtual Connection Status does not change to Record Issued on the Service Request Connections window until after it is closed and re-opened.

Resolution: If the status for a Virtual Connection is changed to Record Issued, when the Connection Design window is closed, the Service Request Connections window will be refreshed with the updated status.

Engineering

Issue ID: 76917

Internal CR#: 190218

Problem: Customer is getting a misleading message about CA values when trying to design first (schematic design).

Resolution: The user will receive a message indicating the custom attributes must be verified and saved before the connection can be designed and the system will take the user to the Custom Attributes window.

Engineering

Issue ID: 76896

Internal CR#: 198895

Problem: Sometimes when adding a hard connection to the virtual circuit design, it can take more than 15 seconds to process.  Other times, it adds the connection within a few seconds.

Resolution: When adding a hard connection to the virtual circuit design, the time that it takes to place the connection on the drawing canvas will be significantly reduced. The validation that was checking if any CA's were modified has been changed to check a Boolean variable rather than looping through every value that is on the CA page.

Engineering

Issue ID: 77271

Internal CR#: 189416

Problem: Provisioning assistant doesn't filter the channels available based on the connection chosen. Shows all the eligible or matching channels available for all connections exists between the nodes in context.

Resolution: Only loads the channels for the base connection that is selected.

Engineering

Issue ID: 72364

Internal CR#: 148680

Problem: Reporting-Cross Connect Report: User selects multiple relay racks and then clicks OK to see the report. When they try to save or print the report, the windows take a long time to display.

Resolution: A sql query has been tuned. The response time is now less than half the previously reported time.

Engineering

Issue ID: 76325

Internal CR#: 179714

Problem: Physical connections are allowed to be added in an equipment groom.  Physical connections are not groomable and should not be allowed to be placed in the groom project and order.  Currently grooming allows physical connections into the groom project, but the Process Groom option is disabled in the design task.

Resolution: Physical connections will not be pulled into a groom project.  Should a user select one, a message will be displayed.

Engineering

Issue ID: 77116

Internal CR#: 181784

Problem: When creating a Network Location Alias (as a Coded Location) from an End User Location, the Located in Building should not be required.  This being a required field forces the user to specify in which Network Location building the End User Location is located.  This is not valid.

Resolution: The column, Located in Building, will not be visible/required when creating a network location alias from an end user location.

Engineering

Issue ID: 76157

Internal CR#: 183227

Problem: Ownership of Inventory:  After updating/changing information on the Leased Circuit Association tab, received error message "with an ownership code of "other", at least one of the two network locations must not be owned by your company. "  

Resolution: The message stating that at least one of the locations must not be owned will not manifest itself when one of the locations is an end user location (which is not owned).

Engineering

Issue ID: 77078

Internal CR#: 184492

Problem: When running a Mass DLR reconcile in the background processor from a equipment move or equipment edit it sometimes dies without any reason.  They fall to a 'Not Responding' state, and no combination of canceling and restarting will cause them to proceed beyond the last reported % complete.  Running the same job in the foreground gave the following error: Array Boundary exceeded in of_adddlrlines.

Resolution: The logic responsible for adding the equipment information to the DLR was re-using an index variable instead of using a new variable. This led to an array index out-of-bounds exception for certain equipment configurations. A new variable is now used where appropriate. The Mass DLR reconcile in the background processor will not die or fall into a 'Not Responding' state.

Engineering

Issue ID: 77281

Internal CR#: 185201

Problem: Cancel Assign function shows IN BACK, but job has been completed. Background processor didn't release it back to the work queue and the task cannot be completed.

Resolution: The transaction that is responsible for updating the task status was not being committed. The task status is now updated and may be completed.

Engineering

Issue ID: 77117

Internal CR#: 185394

Problem: When trying to add premise equipment on a circuit design for an end user location, a network location is currently required for the equipment to be added.  Since they are using video equipment, a network location is not available and should not be required to add premise equipment to circuit

Resolution: The user will be able to add premise equipment for an end user location.  The Premise Equipment block will use the end user location name instead of the CLLI Code on the outside of the block. This is the same as an end user equipment assignment.

Engineering

Issue ID: 77372

Internal CR#: 188451

Problem: SONET Provisioning Assistant - Channel selection window takes more time to display the available channels in the network route chosen.

Resolution: The response time for the channel selection window in the SONET provisioning assistant has been improved.

Engineering

Issue ID: 76602

Internal CR#: 189633

Problem: Updating the Serial Number on an STM64 card is taking longer than expected. It appears that the code is looping through the port address table when no changes are being made to the port addresses. Since there are several thousand ports on this card, this is very time consuming.

Resolution: Tuned the code for updating datawindows, so that unnecessary calls are avoided.

Engineering

Issue ID: 75757

Internal CR#: 203166

Problem: A change order exists for a facility in which there are child trunks riding it.  Only the facility is on the order but a disconnect order exists for the child circuits.  A change is made to the design of the circuit so that a cascading reconcile creates a design issue for the child circuit.  If that child circuit is being disconnected on another order and the disconnect order is completed before the change order, then when the change order is completed, the pending issue from the cascading reconcile does not get updated and remains in a pending status.

Resolution: When the Change order for the parent circuit is due date complete, the issue for the child circuits will be updated to 'Overriden'. The DD complete process could not find the children that were riding on the parent circuit since they were already disconnected. Additional logic was added in the Due Date logic to find the disconnected children.

Engineering

Issue ID: 76936

Internal CR#: 203979

Problem: If there are any circuit assignments reconciled during an Equipment edit or move, the background processor gets a syntax error, "No SQLCA defined". Once this occurs, it locks the database.

Resolution: Jobs through the background processor were missing commit logic. Fixed the syntax error for committing the change to the database.

Engineering

Issue ID: 77023

Internal CR#: 181886

Problem: The user cannot do a swap group assign in the Group Assign window.

Resolution:  Pending Disconnect circuit positions are now available as group assignment candidates

Engineering

Issue ID: 76458

Internal CR#: 185200

Problem: The Remarks from a USO are not coming forward to the connection design.

Resolution: The remarks from the USO will display in the Connection Design window.

Engineering

Issue ID: 74065

Internal CR#: 187294

Problem: End User location information that is entered via a USO is not pulled over onto the Locations tab in circuit design.

Resolution: End User location information that is entered via a USO displays in the Locations tab of the circuit design.

Engineering

Issue ID: 74065

Internal CR#: 204804

Problem: End User location information that is entered via a USO is not pulled over onto the Locations tab in circuit design.

Resolution: End User location information that is entered via a USO is displayed in the Locations tab of circuit design.

Engineering

Issue ID: 77383

Internal CR#: 187470

Problem: In Network Systems, the user is unable to delete the multi-value CAs for a network component.

Resolution: In Network Systems, you can delete multi-value CAs for a network component.

Engineering

Issue ID: 77507

Internal CR#: 188153

Problem: The user is unable to select EUL for OTS or CLS type circuits when creating EWO.

 

Resolution: New functionality was added to the Connection Identification window within the application to allow the user to select an End User Location as a terminating point for new connections that are not in CLF or CLM format.  

A new field and "search" picture button have been added below the Network Location fields to display the location name when an End User Location is selected. This is the same functionality currently available in the Equipment Inventory Search window.  

This functionality is available when creating new connections with or without an order. Because a user may now select an End User Location as a termination point of a connection, the Connection Design Query Results window has been slightly modified. The A and Z Network Locations (now titled Originating and Terminating Locations, respectively) will now display the Location Name when a CLLI code is not available.  

To query for a connection by End User Location, select "End User Location" from the right-click menu in both Connection Design Search and Connection Hierarchy.

Engineering

Issue ID: 75983

Internal CR#: 200504

Problem: The application locks up when you click on the View button in equipment spec.

Resolution: When the window opens, after the data is retrieved, it is not locked. The user can use the scrollbar to view data and close the window after they finish reviewing.

Engineering

Issue ID: 76000

Internal CR#: 170250

Problem: Customer reports that even though the w_equipinstall_query, w_equipinstall_maint, and w_equip_structure_types windows are set to Read Only, that the user can still access Equipment Structure Types

Resolution: The Structure Types window to maintain Read Only permissions and not allow a Read Only user to add new structure types.

Engineering

Issue ID: 76691

Internal CR#: 177754

Problem: Unable to move the bar on the Equipment tab of Reconcile Assignments window off the design.

Resolution: The bar on the Equipment tab of the Reconcile Assignments window can now be moved.

Engineering

Issue ID: 77575

Internal CR#: 187446

Problem: The Install At option is not available for structures when trying to install base equipment.

Resolution: The Install At option is available for structures when trying to install base equipment with 0 mounting positions.

Engineering

Issue ID: 71778

Internal CR#: 189708

Problem: SONET STS1 in OC192 taking too long to process.  Auto Building STS1 to DS3 for SONET OC192 rings is taking an unacceptable amount of time.

Resolution: The time required to autobuild and save the OC192 network has been dramatically reduced.  All large networks will take less time to autobuild and save when compared to previous releases; however, the ratio for the time reduction recognized for this network cannot be applied to all networks.  The number of segments, autobuild connections and provisioned connections all play a part in the time it takes to autobuild and save.  The greater the number of segments and autobuilt connections (autobuilt in the current network), the longer the autobuild and save process will take.

Engineering

Issue ID: 75982

Internal CR#: 170510

Problem: When using the find function in the Equipment Install window at design time, equipment with blocked ports are offered as option.

Resolution: A new drop-down of condition code has been added to the Equipment Search window.

ALL: Include condition code.

None: Exclude condition code. If all the ports on a card have condition code, then the card will be excluded in the result set.

Blocked: Only cards that have blocked condition code ports will be included.

Informational Only: Only cards that have informational condition code ports will be included.

Engineering

Issue ID: 76857

Internal CR#: 179307

Problem: The Connection Design Search window doesn't work when trying to query using LIKE on Trunk Group Number columns when querying for Trunk Connections.

Resolution: When running a Connection design query using LIKE on Trunk Group Number column for Trunk Connections, Oracle was returning a ORA-0600 error. This error was not visible. The SQL generated by the window was modified so that rows will return when using LIKE on the Trunk Group Number column.

Engineering

Issue ID: 76864

Internal CR#: 190383

Problem: User states it takes 9-10 minutes to open the NET_DSGN task. After waiting 10 minutes, a error occurs.  

Resolution: The code was modified to improve performance. The network maintenance window will now open in a reasonable time for new and existing network systems.

Engineering

Issue ID: 77417

Internal CR#: 186095

Problem: The Network Location drop-down in Connection Hierarchy Search, Connection Design Search and Trunk Group Search windows is not wide enough.

Resolution: The Network Location drop-down is wider in the Connection Hierarchy Search, Connection Design Search and Trunk Group Search windows.

Engineering

Issue ID: 40998

Internal CR#: 187271

Problem: An inaccessible preference in 6.0.4 seems to be causing a problem with the Connection Design query. User receives a sql error if this preference is set to 'Y' instead of 'N'.

Resolution: The concept of Warn When Retrieve Exceeds"in the Properties tab of Connection Design Query is available in R5.2.x code stream.  The same code is available in M6 as well.  So, the application tries to frame a SQL to calculate the maximum number of rows -- results in framing an invalid SQL. This is the reason for the SQL error.  To resolve this issue, a code change was made so that the SQL error would not appear anymore.

Engineering

Issue ID: 77378

Internal CR#: 188698

Problem: When users print CLR, they are getting an extra page at the end with just the Trunk Group User Data header on it.

Resolution: You will not receive the extra page at the end, if the trunk group user data is not available.

Engineering

Issue ID:

Internal CR#: 207236

Problem: The GLR is displaying the Originating Element as the Terminating Element when the virtual circuit is opened initially for the Service Request Circuits window. When the user selects Schematic Design, the error 'The Terminating Element has not been Selected' appears.

Resolution: When the GLR opens, only the Originating Element will be selected if there are multiple terminating elements to select and the user will be able to design the virtual.

Engineering

Issue ID: 76918

Internal CR#: 189705

Problem: The user opens the PVC (Virtual) circuit first before designing the Port (Physical) connections. After receiving the correct warning, the Originating/Terminating connection could not be determined, and the user goes back and designs the Ports. After the user designs the PORTs and re-opens the PVC ,the Originating and Terminating Element names still show 'NONE'.  In 5.2 for this scenario, after re-opening the PVC, the Originating and Terminating would be appear; no further work was needed. But in 6.0.4, the user now needs to click NONE and select each. This is an extra step that user should not have to complete

Resolution: After re-opening the PVC, the Originating and Terminating element names will appear and no further work is needed as long as only 1 originating and 1 terminating element is found.

Engineering Work Order

Issue ID: 75888

Internal CR#: 171503

Problem: Cannot get to security screen in Engineering Work Order when you hit F2.

Resolution: Modified framework tag to trigger the permissions security window from F12 to F2 to be consistent with the rest of the framework.

Engineering Work Order

Issue ID:

Internal CR#: 188465

Problem: Users cannot remove an Engineering Work Order when User Data is present.

Resolution: User will now be able to remove an Engineering Work Order when User Data is present.

Equipment

Issue ID:

Internal CR#: 204070

Problem: The Allow Lower Rates functions in the cross connect window, but not in the connection design equipment install, assign circuit function.

Resolution: When assigning a connection and validating the port' rate code whether it matches the connections, or whether it is 'N/A', a check was added to see whether the allow lower rates indicator is on, and if so, whether the rate code is higher than the connections' rate code, so that the assignment can be made.

Equipment

Issue ID: 75741

Internal CR#: 148698

Problem: filters are not applied correctly to search criteria in query

Resolution: In d_equipsearch_user_data_results data object sql was not correct. And we are adding field in d_equipsearch_user_data_query data object dynamically. The dynamically added columns were not added in d_equipsearch_user_data_results  data object dynamically. Because of this our system retrieved all the rows irrespective of search criteria.Now I added that new fields which has been added dynamically in d_equipsearch_user_data_query  object.Now Its working fine. 

Now the Equipment user data columns can be used as search criteria to find equipment.

Equipment

Issue ID: 77198

Internal CR#: 183470

Problem: Cannot get an accurate retrieve out of Equipment Inventory Search when the location has a name with an "&" in it such as "PLANTXX01    AB & C".

Resolution: The framework was changed to allow for these special characters and now prevents the application server from generating the xml parser errors.

Equipment

Issue ID: 77798

Internal CR#: 193120

Problem: Options grayed out when you right-click.

Resolution: When deleting items in optical network systems, remove mappings if there are any so that network systems will be successfully saved.

Equipment

Issue ID: 76670

Internal CR#: 200502

Problem: Equipment assignments are being removed by the reconcile process when a card is moved from one position to another.

Resolution: When moving a piece of equipment that has placeholders cross-connected to a mounting position that does not have placeholders defined, the enabled ports mappings will still have the correct A_Z_OTHER identifier so that the parent equipment information is displayed on the DLR correctly.

Equipment

Issue ID: xxx

Internal CR#: 203098

Problem: Add a Links tab to the Equipment and Equipment Spec windows. The Links tab should enable the user to add, edit and delete links. Further the Equipment window should also display links created in the Equipment Spec window.

Resolution: A Links tab has been added to the Equipment and Equipment Spec windows. The user will be able to view the Equipment Spec links in the Equipment window. However they will have to go to the Equipment Spec window to perform any edits on these links.

Equipment

Issue ID: 71198

Internal CR#: 187276

Problem: When the equipment spec contains a set of quotes in the acronym field, the application crashes when trying to view the report for the cross-connected equipment.

Resolution: The equipment cross-connect report will display without error when the equipment spec acronym field contains double quotes.

Equipment

Issue ID: 77454

Internal CR#: 187953

Problem: The equipment specification usage report is adding more pages each time it prints.

Resolution: The equipment spec usage report will print only what is expected.  Extra pages will no longer be printed.

Equipment

Issue ID: 75362

Internal CR#: 200618

Problem: Changes to Node Address of installed equipment removes the address of the next lower rate port.

Resolution: Changing the node address on installed equipment will not remove the addresses defined on the enabled ports.  Changing the node address of a port will cause its children to reflect the change, unless the child does not contain the original node address of the parent or it has a hard override.

Equipment

Issue ID: 75741

Internal CR#: 148698

Problem: If the User Data field is used as search criteria, all equipment appears in the display field regardless of the filter criteria used.

Resolution: Now the Equipment user data columns can be used as search criteria to find equipment and returns the correct results.

ISR

Issue ID: 75468

Internal CR#: 170082

Problem: A new order for a circuit or trunk exists and a change or record order is entered for the same circuit before the new order is completed.  If the new order is then sup-cancelled there are no messages telling the user completing the change or record order that the order may not be valid anymore.  Completing the change or record order can also cause the circuit to go to an incorrect Inservice status.

Resolution: Now the message occurs which prevents the new order from being supplement cancelled prior to canceling the change order, since it has the same circuit association. Once the change order is cancelled, the new order is allowed to proceed with the supplement cancel.

ISR

Issue ID: 76969

Internal CR#: 182822

Problem: A TCIC 'skip 4' message occurs intermittently in the ISR for trunk group information.

Resolution: In the ISR,  for the trunk group information, when you enter TCIC numbers, the 'skip 4' message did not prompt in some cases. Made few code changes to resolve the issue.

ISR

Issue ID: 76214

Internal CR#: 183778

Problem: The customer still has issues after running the CR174999.sql and CR172744.sql scripts.  After deleting the trunks and re-adding them, an error occurs saying the TCICs already exist.  When the user tries changing the ecckt to get around the error, another error stops them saying that a incorrect number of trunks already exist.  

Resolution: This script is a data cleanup for Trunk circuit rows that have been cancelled but still have trunk_circuit rows that have a TCIC assignment. This script will look for all cancelled trunk circuits that have been cancelled that still have a TCIC assignment and it will delete the circuit. The procedure SP_DELETE_CIRCUIT is called so that all the appropriate tables are updated and processed.

ISR

Issue ID: 75453

Internal CR#: 189619

Problem: The CLM window is enabled on ISR view-only.

Resolution: In the View-Only ISR the CLM window and Trunk Number Assignment window are disabled.

ISR

Issue ID: 76968

Internal CR#: 180232

Problem: When processing a Trunk Change order, a prompt displays that makes it look like trunks are being deleted.

Resolution: In the script there was no checking for the condition for a change order. Now the condition has been applied that resolves this issue.

ISR

Issue ID: 71407

Internal CR#: 180435

Problem: When application bar has two rows at the bottom of the screen, the Number of Circuits Requested text is overlapping the bottom row on the list making it impossible to see all of the trunks.

Resolution: When the application bar has two rows at the bottom of the window, the Number of Circuits text will not overlap the bottom row so that you can view all of the trunks.

ISR

Issue ID: 77219

Internal CR#: 182888

Problem: When printing TCO from the trunk ordering process, two extra fields appear on the Circuits tab of the Print window.

Resolution: The two extra fields will not appear on the Circuits tab of the Print window.

ISR

Issue ID: 76604

Internal CR#: 187400

Problem: The Notes section on the order printout is too big.  If you print the notes, there is too much blank space on the printout.

Resolution: The blank space has been removed from the notes on the printout.

ISR

Issue ID: 77330

Internal CR#: 188671

Problem: When previewing an order (Internal Service Request View), the control window button in the upper-right corner of the window does not close the window for individual reports.

Resolution: In the object properties, the 'controlmenu' property was not included. Now the control button property has been included, and the Close Window button will be enabled.

ISR

Issue ID: 76862

Internal CR#: 188127

Problem: Continuous Add doesn't work when adding multiple facilities to an ISR.

Resolution: While clicking the OK button in the multiple facilities to an ISR, there is no condition for generating the Facility Designation numbers automatically for CLF format. Now the condition has been included and the Facility Designation number is generating automatically.

LSR

Issue ID: 77319

Internal CR#: 185107

Problem: Uncomment the LSRSERVER entry in the gateway.ini file to have the LSRSERVER.ior file created but the file does not get created.

Resolution: Added code needed for the URLNaming service initialization.  The fix for the LSRServer (pre-LSR6) initialization is actually needed in "core" appserver.jar class.

MIP

Issue ID:

Internal CR#: 203424

Problem: An error message is received when running the updateServiceLocation routine is called from the XML-API.  The error message states that an End User Location ID is required.  This error is received despite having an End User Location Id on the input XML.

Resolution: The XQuery that mapped the XML data into a java bean did not map the End User Location Id field correctly.  The transformation was updated to map the End User Location Id field to the correct field in the XQuery before being sent to the API logic.

MIP

Issue ID:

Internal CR#: 203820

Problem: The createOrder request goes into infinite loop when importing an NGN order with Connection information.  The issue arises only when there are validation error messages encountered during the API process.  For example, when the jurisdiction code is set to 0, the validation error message is seen repeatedly in the appserver_log.xml file.

Resolution: The problem arises because of the way the API manages error messages.  The API keeps error messages in two different ErrorHandler instances.  Within the code, there is logic to copy errors from handler A to the handler B.  However, the issue was happening because the XML-API EJB was copying errors from handler B to A.  The resolution was to remove the redundant code in the XML-API EJB to copy errors from one error handler to another.

MIP

Issue ID:

Internal CR#: 204050

Problem: If a connection has logical port assignments on another connection rather than direct port assignments on a piece of equipment, the connection assignment data exposed via the Activation API will not include custom attributes associated with the connection.

Resolution: The Activation API was fixed to include custom attribute data for a connection with logical port assignments.

MIP

Issue ID:

Internal CR#: 205368

 

Problem: Appserver does not have the ability to accept multiple integration events even though the schema allows it.

Resolution: Modified the appserver logic and UpdateIntegrationEvent workflows to allow multiple instances of integration events to be sent for a single MSS event.

MIP

Issue ID:

Internal CR#: 205727

 

Problem: Incorrect CA's are displaying when making the activation API call. The logic is checking for In Service issues first before checking for Pending issues on both physical and virtual connections.

Resolution: Fixed logic so that if the document number is entered then it will check the Pending issue first instead of the In Service issue for both physical and virtual connections.

Plant

Issue ID: 77521

Internal CR#: 198883

Problem: You should be able to save a Dedicated Plant canvas containing NW Loc with a name more than eight characters.

Resolution: Now you can create a dedicated plant with equipment chosen from a Network Location that has CLLI code more than 11 characters.  After adding the equipment you can go to the "Details" Tab without getting any import error.

PSR

Issue ID:

Internal CR#: 185543

Problem: Execute the executeFinishOrder API for any document number  and you get the following error:  

Field: [LMetaSolv.CORBA.WDI.WDIError; = Array (values following)

                        [0]        Field: code = 39990

                        [0]        Field: reason = Miscellaneous Error: Closed Statement: next.

Resolution: The executeFinishOrder API will now execute correctly without throwing the error.

PSR

Issue ID: 77764

Internal CR#: 198958

Problem: Customer reports that the Value Labels are not defaulting correctly.

Resolution: Now these values will be defaulted on the products when creating a PSR.

PSR

Issue ID: 77909

Internal CR#: 202962

Problem: You are unable to associate international geographic area hierarchy to Network Area.

Resolution: Now the State drop-down will display region information and the City drop-down will display the State information.

PSR

Issue ID: 75979

Internal CR#: 171877

Problem: User is receiving a scripting error when adding links to the PSR order, because the file name contains an apostrophe.

Resolution: Code was changed to allow you to add links that have an apostrophe.

PSR

Issue ID: 76919

Internal CR#: 180458

Problem: When adding a new location on an ATM/FRAME relay order, the street suffix drop-down displays Z to A, instead of A to Z.

Resolution: The Street suffix values will be displayed in  A to Z order.

PSR

Issue ID: 76748

Internal CR#: 183198

Problem: When using the arrow key(s) to move around in PSR valid values, operation is erratic.

Resolution: Code is added so that you can now arrow up and down in PSR valid values

PSR

Issue ID: 77109

Internal CR#: 185873

Problem: Users are not able to associate a connection spec to a product specification that was converted as part of the broadband migration.  The product specification is related to a product bundle spec and has been used to build product catalog items.

Resolution: The logic in the Product Specification has been changed. Now the users will be able to associate connection specs created from the Broadband Migration.

PSR

Issue ID: 77370

Internal CR#: 190386

Problem: The DD task is failing in the background processor with an E911 extract error.  Nothing has changed on the customer account.

Resolution: A section of code was not comparing SVC values correctly.  This caused the customer account changed message even though the data had not changed.  The code was changed so that the values being compared are compared correctly.  Another issue occurred in the due date logic.  The due date code was calling the e911 processing code when the e911 task had already been completed.  The best practice for e911 smart tasks is to place them after the due date task to prevent data issues, but there are rare instances where the e911 smart task is placed before due date.  The due date code should not be calling e911 processor code when the e911 smart task is completed.

PSR

Issue ID: 76981

Internal CR#: 185080

Problem: PSR MPO:  The customer is able to complete the DD task of subsequent change orders before the new order.

Resolution: The MPO validation will be executed when trying to complete the Due Date Task.

PSR

Issue ID: 76262

Internal CR#: 177209

Problem: In the Connection Design window, on the Customer Information tab, the Contact Name and Contact Number does not display.

Resolution: In Connection Design window the Contact name and number information will be displayed.

Technical Framework

Issue ID: 77874

Internal CR#: 199000

Problem: The user receives a runtime error, and the application crashes when you try to assign a provisioning plan to a PSR.

Resolution: The SQL parser on the client was not processing extended ASCII characters, which caused the error. The SQL parser has been modified to accept extended ASCII characters.

Technical Framework

Issue ID:

Internal CR#: 182886

Problem: There is currently no way to see which MSS end user is currently accessing the database on an APP_MSLV connection due to the connection pools used by the application server.

Resolution: Added ability to modify V$Session view with a client identifier (userid) as each user logs in.

Technical Framework

Issue ID: 74937

Internal CR#: 190004

Problem: JMaster.exe freezes on * A database error has occurred: Error * no SQLCA defined

Resolution: The root cause is a series of socket exceptions on the application server when the Background Processor is polling for information with the result being that an empty xml package arrives back at the client. At that point the client tries to process the results and finds it empty and issues a message with an Ok button. If the button isn't pressed the Background Processor just gets locked up. This fix will suppress the error message and the Background Processor should be able to proceed normally.

Technical Framework

Issue ID: 73614

Internal CR#: 184192

Problem: The application cannot be started as a Windows service.  BEA provides a script to start up the server as a windows service. However, this script does include startup parameters, nor does it start the ORB.  Hence, the application will not start properly.

Resolution: After running the installer, Windows customers must create a service for the WebLogic server as well as jBroker. Two scripts are provided to enable creating and deleting the WebLogic service. The procedure is documented in the Setup Guide (M6.0.5+).

Technical Framework

Issue ID: 76720

Internal CR#: 178354

Problem: Installation of a 6.0.4 cluster causes an error message while trying to copy the WebLogic Config source files.

Resolution: During the installation process, if encounter permission or disk space issue, the install will pop up an error message and then a Cancel dialog box. The cancel dialog will ask if the user wants to exit the installation or not. The user should exit the installation, correct the permission or space problem, and then restart the installer.

Technical Framework

Issue ID: 76726

Internal CR#: 179009

Problem: M6.0 cluster: Scripts to start the Admin server are not included in the installation.

Resolution: Scripts were added to start admin and proxy servers. Scripts are provided as a model and must be modified for customer's environment. Scripts are added to domain directory: startAdminServer, startAdminServer_wli, startProxyServer.

Technical Framework

Issue ID: 77605

Internal CR#: 188216

Problem: The Upgrade option in the application server installation does not copy over the procs or prodfixsql files

Resolution: The application server Iinstaller will no longer add procs and prodfixsql folders. Only the DBINSTALLER will do that.

Technical Framework

Issue ID:

Internal CR#: 199503

Problem: There is no Jbroker Corba implementation for the AIX platform and this was causing several Jbroker related error messages to appear in the log files when the application was started up on an AIX platform.

Resolution: Changes were implemented to bypass Corba related code if the server platform is AIX.

Technical Framework

Issue ID: 74937

Internal CR#: 190004

Problem: JMaster.exe freezes on the * A database error has occurred: Error * no SQLCA defined.

Resolution: The root cause is a series of socket exceptions on the application server when the Background Processor is polling for information with the result being that an empty xml package arrives back at the client. At that point, the client tries to process the results and finds it empty and issues a message with an OK button. If the button isn't pressed the Background Processor just gets locked up. This fix will suppress the error message and the Background Processor should be able to proceed normally.

Trouble

Issue ID: 76879

Internal CR#: 205594

Problem: Business Unit user data column is displaying in numeric format on trouble tickets.

Resolution: The display value is now shown instead of the numeric key.

User Setup

Issue ID: 74413

Internal CR#: 137516

Problem: Attempts to customize the navigation bar in 6.0.x render the application non-functional.  The left side menu goes completely blank.

Resolution: The code was modified to take the data stored in the database for the custom navbar and do an intermediate conversion to a character array before doing the transform, which renders the xml based on the xsl file being used.

User Setup

Issue ID: 76907

Internal CR#: 182573

Problem: The timeout preference does not work.  In previous releases, the application was closed after the timeout period was passed and there was no activity by the user.  The user is logged in indefinitely in 6.0.4.

Resolution: The timeout preference was removed.

User Setup

Issue ID: 76907

Internal CR#: 184485

Problem: The timeout preference does not work.  In previous releases, the application was closed after the timeout period was passed and there was no activity by the user.  The user is logged in indefinitely in 6.0.4.

Resolution: The timeout preference was removed.

User Setup

Issue ID: 77185

Internal CR#: 190535

Problem: You cannot secure the delete functionality without making the window read only first.

Resolution: we can see if the "w_ngn_network_design" window is read-only then the delete option is made invisible in the code.  This is done to support the read-only functionality, because if a screen is read-only then we should not allow modify/deletion activity in it.   Hence this behavior is not from the user security permissions.  No matter if the user security permission set or not, the above code will make the "Delete" popup menu item invisible if the network system is in read-only mode.  

Basically the customer is trying to secure a Popup Menu in the Network Systems, but they are assigning permissions for the standard "View --> delete" menu on the top of the window.  The above process makes the customer think that the security is behaving improperly.  But the user security permission is working as designed.

To secure a Popup Menu, we have to assign permissions for the respective popup menu in "Popup Menus" section of the "Assign Permissions' security screen.  To do this we have to insert the details of the popup menu into the "Security_template" tables.  This should be supported through a prodfix sql.   

The above has been introduced by inserting rows in "ASAP.SECURITY_TEMPLATE" for the popup menu items.   Now the customer can secure these popup menu items in network systems. There are no Client-side (PB) code changes involved in this resolution.  

How to secure the popup menu options in security?

1.  Open the Notes window  
2.  Click F2, Assign Permissions window will be displayed.  
3.  Select the appropriate User/Group for which the menu options should be secured.  
4.  Expand the Popup Menus branch in the left side of the window and select the notes window "w_ngn_network_design.m_netdes_dockpanel_popup.m_list".  
5.  After selecting the Notes window, the menu options will be shown in the right side of the Assign Permissions window.  
6.  Set permission as needed for the respective menu options.  
7.  Close the Assign Permissions window.  
8.  Now open the Notes window again after restarting the application to see the Notes window with menus secured.

Note: Changes do not appear to the user until the user's next log-on to the application.

User Setup

Issue ID: 75150

Internal CR#: 054898