1 MetaSolv Solution 6.2.1 Release Notes

This chapter provides the following information about Oracle Communications MetaSolv Solution Release 6.2.1.

For installation instructions, see MetaSolv Solution Installation Guide.

Software Support

MetaSolv Solution 6.2.1 supports the following software versions:

  • Oracle Linux Server release 5.5 (Carthage)

  • Red Hat Enterprise Linux Server 5

  • Oracle Solaris 10 update 5/08 or higher (on a SPARC machine)

  • AIX 6.1 or higher (on a POWER6 machine)

  • HP-UX 11.23 or higher (on an Itanium machine. 32-bit and 64-bit JAVA supported)

  • Windows Server 2008 R2

  • Oracle WebLogic Server 10.3.1

  • Oracle Database 11g R2

  • JacORB 2.3.1

Workstation Client

The MetaSolv Solution client supports the following software versions:

  • Windows 7

  • Windows XP Professional SP3

  • Windows Server 2008 R2

See MetaSolv Solution Planning Guide for more information.

Product Enhancements

This section describes new enhancements introduced in MetaSolv Solution 6.2.1.

MetaSolv Solution 6.2.1 includes enhancements that were delivered until June 2013. For more information, see the What's New document for the latest MSS 6.2.1 patch set.

To download the latest MSS 6.2.1 patch set, visit the My Oracle Support Web site:

https://support.oracle.com

Added Support for IPv6 Address Management

MetaSolv Solution now supports Internet Protocol version 6 (IPv6) address management.

An increasing need for IP addresses resulted in the development of IPv6, which offers a large address space. Mobile phones, personal digital assistants (PDAs), and other wireless devices need Internet access, and each device requires its own unique IP address.

IPv6 offers extended address length, thus eliminating the need to use other techniques, such as network address translation, to prevent the exhausting of available address space. IPv6 contains addressing and control information to route packets for the next-generation Internet.

The IPv6 prefix notation is similar to the way IPv4 addresses are written in Classless Inter-Domain Routing (CIDR) notation. The notation appends the prefix length, written as a number of bits preceded by a slash.

MetaSolv Solution supports the following types of IPv6 addresses:

  • Local Unicast addresses: A Local Unicast address may be created by an organization (or an individual) for use in its private networks or intranets. It is not routable on the Internet; however, a private IPv6 network needs to be unique within the private network or the intranet on which it is used.

  • Global Unicast addresses: A Global Unicast address is allocated by an Regional Internet Registry (RIR) to an organization or an individual (known as the owner). It is routable on the Internet; therefore, it has to be globally unique. It is a unique address assigned to each IPv6 interface on the Internet.

An IPv6 Global Unicast address is a combination of the following components:

  • Global Routing Prefix (m bits - usually 48 bits): Identifies the IPv6 network; Assigned by an RIR to a site.

  • Subnet ID (n bits - usually 16 bits): Identifies the IPv6 sub-network (subnet) within the site; Assigned by the site administrator.

  • Interface ID (128-m-n bits - usually 64 bits): Identifies an IPv6 interface (homed within an IPv6 host) in the network. The Interface ID is represented as 128 bits minus the lengths of the Global Routing Prefix (m bits) and the Subnet ID (n bits).

MetaSolv Solution displays IPv6 addresses using the standard notation, which represents the IPv6 address as eight 16-bit hexadecimal words separated by a colon (:). IPv6 addresses can also be represented in compressed notation, which uses a double colon (::) to represent a single contiguous group of zero fields in an IPv6 address. You can use the compressed notation when entering IPv6 addresses.

For example, the following are valid IPv6 addresses:

  • 2001:0db8:0000:cd30:0000:0000:0000:0000/60

  • 2001:0db8::cd30:0:0:0:0/60

  • 2001:0db8:0:cd30::/60

    The /60 is the appended prefix length.

The new MetaSolv Solution Internal IPv6 Management functionality enables you to efficiently manage your IPv6 address inventory. MetaSolv Solution provides a tree view of your IPv6 address inventory as well as tools that enable you to group your inventory to make address retrieval easier. By expanding the tree, you can see the base IPv6 addresses, the subnets you created, and the subnet properties.

The new MetaSolv Solution IPv6 Address Management functionality lets you do the following:

  • Create base networks: The base network (basenet) is the IPv6 address an Internet service provider (ISP) receives from a regulatory body or an upstream ISP. ISPs use their basenet as their starting point. The ISPs enter the basenet into their systems and create more subnets using this basenet.

  • Create subnets: A subnet is a sub-network or division of a single base IP address. When creating a subnet, you divide the available addresses within the network. You can also divide a subnet into more subnets.

  • Create IP pools: An IP pool is a block of addresses from which you can create subnets. You create IP pools from a block of free hosts in a basenet or another IP pool. When you further divide a subnet, the addresses that remain are placed into an IP pool. The difference between an IP pool and a subnet is that you cannot assign/allocate an IP pool; whereas you can assign/allocate a subnet and any of its hosts.

  • Combine subnets: You can create a large block of IP addresses by combining two or more subnets into a single address block. Combining subnets gives you additional IP addresses available for assignment. When you combine subnets, the hosts within each subnet are removed. You can manually create hosts within the combined subnet.

    The following rules apply to combining subnets:

    • The addresses in the subnets must be contiguous and in Unassigned status.

    • The subnets' hosts must be in Unassigned status.

    • The subnets must fall within valid bit boundaries.

  • Delete a base network, subnet, or IP pool: You can delete the created base network, subnet, or IP pool.

    The rules for deleting a basenet, subnet, or IP pool are as follows:

    • You can delete a basenet only if all of its subnets and the subnets' hosts are in Unassigned status. When you delete a basenet, all the addresses are physically removed from the inventory. This action cannot be undone.

    • You can delete subnets individually or in multiples by clicking each subnet, which places a red check mark beside it. The subnets you select for deletion must be in the same basenet or IP pool. Deleting a subnet removes only its definition and reinstates the addresses to the parent IP pool/basenet.

    • You can delete an IP pool only if all of its host addresses are in Pooled status and all of its subnets are in Unassigned status. Deleting an IP pool removes only its definition and reinstates the addresses to the parent IP pool/basenet.

  • Designate planned usage of IPv6 addresses with use groups and use codes: Use groups and use codes are user-defined labels that provide the ability to efficiently organize your IP address inventory. Define use groups; define one or more use codes within each use group, and then associate these labels to the IP address inventory. When you search for IP addresses, you can filter the search based on use groups/use codes and view only the addresses associated with these labels.

  • Preset filter for searching for IPv6 addresses by functional area: A functional area is a module of MetaSolv Solution from which you can search for IP addresses. The functional areas are as follows:

    • Ordering

    • Equipment Inventory

    • Network Areas

    • Virtual Layout Record (VLR)

    You can associate use groups/use codes with functional areas. After you associate use groups/use codes with a functional area, the process of retrieving unassigned IP addresses becomes much easier. For example, by associating the use group with the Ordering functional area, you can limit the number of IP addresses that can be retrieved in a search. This enables you to view only a subset of the IP address inventory to select for the order.

  • Search for existing IPv6 addresses: You can search for existing IP addresses based on status, network area, use group, use code, and customer details. You can also search for IP addresses by specifying wild cards (%). For example, LIKE 2001:0db8%.

  • Recall IPv6 addresses for reuse: When IP addresses are returned as part of an order to disconnect service, the addresses are put into PendDisc (pending disconnect) status until the due date for the order has been completed. At that time, the IP addresses are put into Transitional status and cannot be acted upon until the time period specified in the IP Address Transition Days preference has elapsed. After the elapsed time, you must recall the address block to make it available for subnetting or reassignment.

    The recall function creates new records (in Unassigned or Pooled status) and archives the used records in Unavailable status for history.

    The IP Address Transition Days preference is located under Preferences - Application Setup - Internet Services.

    Depending on the setting of the When recalling a disconnected subnet preference, the recall process either retains or deletes the IPv6 subnet addresses. The When recalling a disconnected subnet preference is located under Preferences - Application Setup - Internet Services.

    If the subnet to which the addresses belonged is retained, the status of the IP addresses changes to Unassigned.

    If the subnet to which the addresses belonged is deleted, the addresses are returned to the subnet's parent IP pool and the status of the addresses changes to Pooled.

  • Track lifecycle of an IPv6 address: You can track the lifecycle of an IPv6 address that is in any of the following statuses:

    • Unassigned: The IP address is part of a subnet and is available for assignment.

    • Pending: The IP address has been assigned and is associated with an open order, but the subnet has not been placed in service.

    • In Service: The IP address is currently in service and is being billed to a customer.

    • Unavailable: The IP address has been taken out of service, the transitional period has elapsed, and the IP address has been recalled for reuse. The recall process archives this record for historical purposes. The archived record will remain in Unavailable status indefinitely.

    • PendDisc: The IP address is associated with a disconnect service request and is scheduled to be disconnected.

    • Pooled: The IP address has 0 (zero) subnet bits, has been specified as an IP pool, or is defined as a single subnet under another subnet.

    • Transitional: The IP address has been taken out of service and is in a transitional period that may or may not have elapsed.

  • Reserve IPv6 addresses: You can reserve IP address subnets for internal use and for a specific customer. You can also set the reservation to expire after a specified duration.

  • Associate IPv6 addresses to network areas: You can select available IP addresses from the ISP's number inventory and associate these IP addresses with a network area for provisioning to customers. The number of IP addresses associated with a given network area can be based on, for example, projected usage in that area based on population or the amount of equipment assigned to that network area. You can associate additional IP addresses with network areas at any time through Application Setup when additional IP addresses need to be made available.

  • Specify IPv6 addresses for network elements and network systems: You can specify IPv6 addresses for network elements and network systems. To support this enhancement, the length of the Mgmt IP Addr field has been increased to support IPv6 addresses. The Mgmt IP Addr field lets you enter an IPv4 or IPv6 address. With this enhancement, the IP addresses are saved in the same format in which they are entered. You must enter a valid IPv4 or IPv6 address.

Note:

MetaSolv Solution does not support IP rules and IP reports for IPv6.

See the Help for more information.

Ability to Copy Connection IDs

This enhancement enables you to copy connection IDs to the clipboard from the Connection Reference window.

To copy a connection ID to the clipboard:

  1. Do one of the following:

    • In the Connection References Search window, search for the connection ID that you want to copy, and then double-click the connection ID.

    • In the Connection Design Window - Connection Summary View, under Actions, click Maintain Cross-References.

    The Connection Reference window is displayed.

  2. Right-click the Connection ID field.

    A message is displayed informing you that the connection ID has been copied to the clipboard.

  3. Click OK.

  4. Open any text editor or word processor, right-click, and select Paste.

    The connection ID is copied to the text editor or word processor.

Auto-Generated Allocation Parameters Fall Within the Defined Range

Prior to this enhancement, an auto-generated allocation parameter assigned to a newly-added hard connection in the virtual schematic design may fall outside the range defined in the MetaSolv Solution Utility application. For example, if you defined the range for the auto-generated allocation parameters from 100 to 4095, and if the maximum value (4095) was already assigned to a hard connection, the newly-added hard connection was assigned an auto-generated allocation parameter value of zero (0), which was not within the defined range.

In this enhancement, when assigning auto-generated allocation parameters to a newly-added hard connection in the virtual schematic design, if the maximum value (for example, 4095) has already been assigned to a hard connection, the application auto-generates a lowest unassigned value (for example, 105) starting from the minimum value (for example, 100) of the defined range for allocation parameters. In essence, the application utilizes the unassigned values between the minimum and maximum values of the defined range when assigning auto-generated allocation parameters.

MetaSolv Solution Installer Supports Oracle RAC

In the MetaSolv Solution installer, a new tab, Oracle RAC, has been added that enables you to specify the number of Oracle Real Application Clusters (RAC) nodes and the information of the database instances that are set up as part of the Oracle RAC database.

See MetaSolv Solution Installation Guide for more information.

Improved Work Management Usability

The following updates have been made as part of this enhancement:

Single View for All Work Queues Owned By a User

This enhancement enables you to view all the tasks of all of your personal work queues in a single view in the Work Queue Manager window. To enable this, a new work queue option, <All>, has been added, which displays all the tasks of all the personal work queues owned by the logged in user. You can add the work queue ID as a viewable column and define a view so that the corresponding work queue ID is displayed in the Work Queue Manager window. The number of tasks retrieved in the Work Queue Manager window is based on the Maximum Number of Rows to Retrieve in the Queue Manager preference under Preferences - Work Management - Work Queue Management.

Ability to View All Work Queues in the Work Queue Manager

This enhancement enables an administrative user to view the tasks in any defined work queue in the Work queue manager. In the Work Queue Manager window, a new radio button, All, has been added, which when selected, displays all work queue IDs in the Work Queue list. The All radio button is protected by the security checkpoint, View All Work Queues, under Work Management in the Security Permissions window. You do not have access to this radio button by default.

User-Definable Task Attributes

The existing Task label functionality has been enhanced to add additional task label fields that provide you the ability to define additional attributes for a task. You can view and edit these task labels in the Work Queue Manager window. These task labels can be secured individually in the Security Permissions window. This enhancement also provides display/sort/filter capabilities on these attributes in the Work Queue Manager window. You can manually enter additional information about tasks or auto-populate these task labels through custom extensions or other custom code.

In the Work Queue Manager window, the existing Task Label right-click option has been renamed as Task Labels, which when selected, displays the Task Labels window. In the Task Labels window, you can enter or edit values for the task labels.

A new system preference, Task Label Headers, has been added under Preferences - Work Management - Work Queue Management. This preference contains 15 Task Label fields and five Task Label (Date) fields. Using this preference, you can enter the Label Text/Header, which is the same for all the users. Only those task labels that have Label text/header defined are available for edit in the Work Queue Manager window. You can modify the existing views or define new views to include the newly-added task labels. The existing views need not be modified if you are not using the new task labels.

Ability to Add Gateway Events and Checklist Items to Tasks

Prior to this enhancement, you could not add checklist items and gateway events to a task when assigning the provisioning plan on an order. This enhancement enables you to do the following when assigning a provisioning plan to an order:

  • Add checklist items to newly-added tasks.

  • Add gateway events to the newly-added tasks and to the existing tasks.

A new tab, Task Checklist, has been added in both the Task Generation and Task Maintenance windows. The Task Checklist tab allows you to select a particular task from the Newly Added Task list and add the checklist items to the selected task. After the checklist items are added to the task, the checklist items are displayed in the Checklists tab in Work Queue Manager window.

A new right-click option, Add Gateway Events, has been added in both the Task Generation and Task Maintenance windows. This option allows you to add gateway events to the tasks. After the gateway events are added to the tasks, the gateway events are displayed in Gateway Events tab of the Task Generation and Task Maintenance windows.

Ability to Run Rules and Behaviors at Process Supplement

The Rules and Behaviors functionality has been enhanced to allow the Rules and Behaviors to be invoked when an order is supplemented. This enhancement allows the tasks to be added dynamically through Rules and Behaviors for an order through the supplement process.

In this enhancement, two new process points, Process Supp and Task Generation and Process Supp, have been added in the following lists:

  • When do you want the action to occur? list in the Task Behavior window.

  • When do you want the event to occur? list in the Gateway Event Behavior window.

You can create Rules and Behaviors using the Task Generation and Process Supp process point if you want the rule to be invoked during both task generation and order supplement. You can create Rules and Behaviors using the Process Supp process point if you want the rule to be invoked only during order supplement.

Jurisdiction Code Displayed Beside Provisioning Plan Name

In this enhancement, the jurisdiction code is also displayed beside the provisioning plan name in the header of the Provisioning Plan window. This enables you to view the jurisdiction code even when you are viewing other tabs, such as PERT Chart, Task Checklist, and so on, instead of navigating to the Provisioning Plan tab every time you want to view the jurisdiction code.

Task Start Time Displayed in the Work Queue Manager

Prior to this enhancement, in the Work Queue Manager, only the task due date for each of the tasks was displayed, but the information about when to start a task was not displayed. As a result, the processing of the tasks was started late, leaving the tasks in jeopardy.

In this enhancement, in the Work Queue Manager window, a new column, Task Start Date, has been added, which displays the scheduled start date of a task. This enables the user to start the processing of the tasks on time.

Ability to Expedite Work Intervals for Tasks in the Provisioning Plan

Prior to this enhancement, if the total standard duration in the provisioning plan was greater than the available duration required to complete the order, the tasks at the beginning of the provisioning plan utilized their entire allotted time and the tasks at the end were stacked because they were unable to utilize their full allotted time (work interval).

This enhancement improves the task generation process within MetaSolv Solution for expedited orders by automatically reducing the duration of various tasks on the order when the time to complete the order is less than the standard interval set up in the provisioning plan.

For example, consider a provisioning plan that contains 7 tasks. Each task has a work interval of 5 days so the total task interval is 35 days. When this provisioning plan is assigned to an order that has a due date of 30 September 2010 and the current date is 15 September 2010, the available duration in the order is 16 days, but the tasks need 35 days to complete. In this scenario, the tasks at the end of the provisioning plan are stacked because they are unable to utilize their full allotted time (work interval).

This enhancement prevents the tasks from being stacked at the end of the provisioning plan by expediting the total standard duration. To expedite a particular task, you can specify a value in the newly added Expedited Work Days, Expedited Work Hours, or Expedited Work Minutes fields in the Provisioning Plan Window - Task Assignments tab, Provisioning Plan Window - Task Dependencies tab, or Rules and Behaviors - Task behavior window. If a task cannot be expedited, the Expedited Work Days, Expedited Work Hours, and Expedited Work Minutes fields can be left blank.

When the tasks are generated, if the total standard duration in the provisioning plan is greater than the available duration in the order, the expedited work interval is considered instead of the standard duration; as a result, the tasks are not stacked at the end of the provisioning plan.

Note:

This new functionality to expedite work intervals when generating tasks is also supported by MSS APIs.

Enhanced Application Usability

The following updates have been made as part of this enhancement:

Added Last Modified User and Date Information in Connection Design Window

In this enhancement, in the Connection Design Window - Connection Summary View and Connection Design Search window, two new fields, Modified By and Modified Date, have been added. The Modified By field displays the last modified user ID for both the new and old issues if you select Save as New Issue in the Connection Design window. The Modified Date field displays the last modified date and time for both the new and old issues if you select Save as New Issue in the Connection Design window.

Added Material Code as a Search Criteria in Equipment Spec Search

This enhancement enables you to search for an equipment specification using material code in the Equipment Spec Search window.

In this enhancement, a new search criteria, Material Code, has been added that enables you to specify the material code of an equipment specification when searching for equipment specifications. In the Equipment Spec Search - Results window, a new Material Code column has been added that enables you to sort equipment specifications based on material code.

Added Rate Center as a Search Criteria in Telephone Number Reservation Search

This enhancement enables you to search for telephone numbers by specifying the Network Area (Rate Center) in the Telephone Number Reservation Search window.

In this enhancement, in the Telephone Number Reservation Search window, a new radio button, Network Area, has been added that enables you to search for telephone numbers by specifying Network Area (Rate Center) as one of the search criteria. If you select Network Area in the Telephone Number Reservation Search window, you must select a network area from the Network Area Name list.

Ability to Copy Information From PRILOC Tab to the SECLOC Tab On a PSR Order

Prior to this enhancement, if you wanted to specify the same end user location information on PRILOC and SECLOC, the information entered on the PRILOC had to be repeated in SECLOC location information as the PRILOC information could not be copied to the SECLOC until the PRILOC was saved. To achieve this, you had to enter the PRILOC end user location and save it. Then, open the PRILOC/SECLOC window again and use the same PRILOC information. This process was time consuming.

In this enhancement, a new check box, Copy from Priloc, has been added in the SECLOC tab - End User view. When adding PRILOC/SECLOC information on a PSR order, if the SECLOC end-user information is the same as PRILOC end-user information, you can select the Copy from Priloc check box in the SECLOC tab - End User view. All the information on the PRILOC tab is copied to the SECLOC tab. The Copy from Priloc check box enables you to populate the fields on the SECLOC tab without reentering repetitive information.

New Preference to Default Order types in Child Order Search Window

In this enhancement, a new user preference, Default Order types in Child Order Search, has been added under Preferences - Service Request. This preference allows you to select the default order types in Child Order Search window of the Service Request Hierarchy window. This preference lists the order types: ASR, LSR, DSR, ISR, EWO, and PSR with a check box for each order type. If you do not select any of the check boxes in the Default Order types in Child Order Search preference, the ASR check box is selected by default in the Child Order Search window.

Additional Automation Capabilities

The following updates have been made as part of this enhancement:

Ability to Automate the Provisioning of Facility Circuits

MetaSolv Solution now provides the ability to automate the provisioning of non-templated DS1 and DS0 Facility circuits (CLF and OTF) through the newly-added AUTODSGN system task.

While the AUTODSGN task does provide an out-of-the-box algorithm to determine both an originating and terminating port assignment, along with a channel assignment to a supporting coterminous parent facility, its full potential is realized when executed along with the included Connection Design > DS0/DS1 Automated Design custom extension.

By providing a custom extension, custom logic may be written to determine the appropriate design assignments, based upon unique business requirements. The custom logic will only be responsible for determining which assignments to make (channel, port, network, cable pair, and so on), as the core application logic is responsible for creating the design issues, making the assignments, building the appropriate design blocks, as well as saving and issuing the designs. See MetaSolv Solution Custom Extensions Developer's Reference for more information.

See the Help for more information about the AUTODSGN task.

Ability to Automate the Generation of Connection IDs

MetaSolv Solution now provides the ability to auto-generate connection IDs for CIRCUIT, INTRNCKT, and CONNECTOR products ordered on a Product Service Request, by expanding the capability of the existing CKTID task.

When executed by the System Task Server, the CKTID task will generate Connection IDs in either CLF or CLS format for traditional Facility and Special circuits, while it will generate an OTS-formatted Connection ID for template-based connections.

This capability may also be expanded to adhere to specific naming standards by implementing custom Connection ID generation logic through the newly-available Connection ID Automation custom extension. In addition to the three Connection ID formats listed above (CLF, CLS, and OTS), the logic also supports the creation of an OTF-formatted connection when generated through the custom extension.

The automated CKTID task generates the connection ID using the input values returned by the Connection ID Automation extension. See MetaSolv Solution Custom Extensions Developer's Reference for detailed parameter-level information.

When the Connection ID Automation extension is not defined, the default out-of-the-box functionality is executed.

See the Help for more information about the CKTID task.

Enhanced Support for Virtual Connections

The following updates have been made as part of this enhancement:

Allow Multiple Soft Connections Within Virtual Schematic Design

This enhancement provides the ability to design a virtual connection using multiple soft connections, which may be placed anywhere within the schematic design. This capability is enabled by a new Add Soft Intermediate Connection option within the right-click menu, which allows you to designate the terminating component of the soft connection.

This capability allows you to add a soft intermediate connection between the entry (ingress) and exit (egress) nodes of networks for which the circuit designer does not want to model with permanent connectivity, which will therefore not require a redesign as a result of network changes.

When the new Add Soft Intermediate Connection right-click option is selected, a new Available Nodes window is displayed, which allows you to designate the terminating component. This window is preloaded with the complete list of network components contained within the same networks as the originating component of the soft connection, listed by the containing network system. Initially, only nodes with connectivity outside of the selected network are displayed to limit the result set. To display all nodes within the selected network, deselect the Only Display Internetworking Nodes check box. A new Network Component Search window, opened by clicking the Search button, is also available to search for any network component that may not be in the preloaded list.

Support Partial Redesign of Virtual Connections

This release extensively improves the usability within the schematic design of virtual connections by allowing you to remove any segment within the entire path of the design during all phases of the design process. Prior to this release, only a limited number of scenarios enabled the Remove Connection option, which required you to perform a complete redesign of the connection when only a partial redesign was necessary.

When a connection is removed from the design, the originating and terminating components of this connection are also removed, but only if these components are not connected to any other components by an existing hard or soft connection; the originating and terminating components defined for the connection will never be removed.

By not requiring a complete redesign of the connection, this new capability considerably reduces the time and effort necessary to modify the path of a virtual connection, which leads to increased productivity.

Ability to Order Virtual Connections on an Engineering Work Order

Prior to this release, you were required to create an Internal Service Request (ISR) to manage virtual connections for internal orders. This release expands the capability of an Engineering Work Order (EWO) to now include virtual connections, which gives you another option.

You can create new virtual connections within an EWO by clicking the new Virtual hyperlink within the Create New section of the Actions panel found within the Manage Connections page. This opens the Connection Identification window, which allows you to define and name the virtual connection.

In addition, the existing functionality to Change and Disconnect connections has been enhanced to support changing and disconnecting virtual connections. The order supplement process has also been enhanced to support virtual connections.

Unlike PSR, you are not required to enter the Connection Specification within the order. This information, along with all of the associated custom attributes, can be maintained within Connection Design after the connection has been created/added on the order.

Enhanced Network Grooming Capabilities

The following updates have been made as part of this enhancement:

Added Support for Grooming All Template-Based Connections (Including Virtuals)

Prior to this release, the Network Grooming tool only supported the maintenance of port and channel assignments for traditional Facility, Special, and Trunk circuits, in addition to switch grooming for telephone numbers. In this release, the Network Grooming tool has been enhanced to support all template-based connections, including virtuals, enabling you to manage allocations to and from parent bandwidth connections. Unlike physical connections, any changes to virtual connections made within the grooming workspace will be reflected within the schematic design view of Connection Design once the grooming order has been processed.

As virtual connections do not occupy a specific channel on a parent connection, the Network Grooming tool provides the ability to manage the individual allocation parameters (stored as Custom Attributes) for each parent to child relationship, when applicable.

To enable this capability, a new Specify Virtual Channel... right-click option has been added within the Maintenance and Connection Hierarchy views of the Groom Maintenance window. Allocation parameters are also auto-generated during the Groom To step if the template is set up to provide this capability.

When making design changes for template-based connections within the grooming workspace, you are prevented from making assignments that would break the rules defined for the connection spec of the connection being modified.

In addition to managing virtual connection allocations to parent bandwidth connections, the Network Grooming tool has been enhanced to also support the ability to allocate physical circuits to bandwidth connections using circuit emulation, which are represented by bandwidth blocks on the DLR within Connection Design.

Fixed Issues

In addition to the fixed issues listed in Table 1-1, MetaSolv Solution 6.2.1 includes issues that were fixed in MetaSolv Solution 6.0.15, 6.0.16, and 6.2.0 patches until January 2012. For more information, see the patch readmes for the 6.0.15 patch 13384392, 6.0.16 patch 13384388, and 6.2.0 patch 13384394.

Table 1-1 lists the fixed issues in MetaSolv Solution 6.2.1.

Table 1-1 Fixed Issues

Bug Number Component Notes

14179438

MIP

Problem

When you create a PSR order through the Create PSR Order API with SYSOPTION item type containing telephone numbers and CNAM/LIDB data under Global, the order is created with telephone numbers, but the CNAM/LIDB data is not updated.

Resolution

The code has been modified and now CNAM and LIDB data is successfully saved when you create a PSR order through the Create PSR Order API with SYSOPTION item type containing telephone numbers and CNAM/LIDB data under Global.

14015422

ASR

Problem

When you run the ImportExternalDLR API with the IC field containing CCNA Name, the following error is displayed:

Matching order not found for PON.

Resolution

The code has been modified and now the external DLR information is updated without any error when you run the ImportExternalDLR API with the IC field containing CCNA Name and CCNA Abbreviation.

12916290

EQUIP

Problem

When adding new equipment, the MSS application saves the equipment information partially, even if you click Cancel in the User Data window, and then click Cancel in the Equipment - New window.

Resolution

The code has been modified and now when adding new equipment if you click Cancel in the User Data window, and then click Cancel in the Equipment - New window, the MSS application displays the following message:

There are one or more Engineering Work Orders open against the equipment selected. Continue with the delete.

14061356

TROUBLE

Problem

When creating or modifying a trouble ticket, the Trouble Ticket Queue window and the Trouble Ticket Detail window show different values in the Severity Level field.

Resolution

The code has been modified and now the Trouble Ticket Queue window and Trouble Ticket Detail window show the same value in the Severity Level field when creating or modifying a trouble ticket.

14227961

ENG

Problem

When viewing a virtual connection schematic design that exceeds the window size in connection design window, the right scroll bar is not available.

Resolution

The code has been modified and now the schematic design for virtual connections in connection design window has horizontal and vertical scroll bars if the schematic design exceeds the window size.

14075618

ASR

Problem

When you click the Print icon on an Access Service Request (ASR) order, the ASR forms are not displayed; instead, the application displays a blank JavaScript window.

Resolution

The code has been modified and now the application displays the ASR details within a new MSS print window when you do one of the following:

  • Click the Print icon on the ASR page.

  • Click the Print icon in the Confirmation Notice and Clarification Request forms.

13938940

ENG

Problem

The MSS application takes more time to save the network system after you delete a connection specification, a component, or both connection specification and component.

Resolution

The code has been modified and now the performance of the MSS application is improved when saving the network system after you delete a connection specification, a component, or both connection specification and component.

13958031

WRKMGMT

Problem

Jeopardy codes are not populating when applied at the service order level through the Service Request window.

Resolution

The code has been modified to handle security permissions properly in the Task Jeopardy Codes window. The application does not apply changes to all the tasks if the Apply changes to entire order button is disabled or made invisible. However, if the Jeopardy Codes window is opened from the service order level, jeopardy codes will be applied to all the tasks irrespective of the security permissions on the Apply changes to entire order button.

14016318

EWO

Problem

When assigning a related provisioning plan to the child order with Rules and Behavior to Delete tasks, some of the task dependencies are missing between the parent and the child order.

Resolution

The code has been modified and now you can view the task dependencies between the parent and the child order when assigning a related provisioning plan to the child order with Rules and Behavior to Delete tasks.

13720320

ENG

Problem

Facility designation for bandwidth circuits is not incremented automatically in CLF/CLFI format for Network Design and the following error is displayed:

The Circuit ID you have entered already exists.

Resolution

The code has been modified and you can now create circuits with the proper Auto Populated Facility Designation value.

13991124

MIP

Problem

When executing the CreateOrderByValueRequest XML API to disconnect a CONNECTOR/ELEMENT product with the Use Copy Item when Importing PSR Order preference set to Y, the following error message is displayed:

Service Item Customer System (1396) cannot be disconnected because its child items are not on this order.

Resolution

The code has been modified and now you can successfully create a Disconnect order through CreateOrderByValueRequest XML API for Connector/Element products with Use Copy Item when Importing PSR Order preference set to Y.

13944766

OTHER

Problem

Unable to remove the inactive provisioning plans by selecting the Delete option from the Edit menu.

Resolution

The code has been modified and now the MSS application allows you to remove the inactive provisioning plans without tasks by selecting the Delete option from the Edit menu.

13901113

ENG

Problem

The MSS application does not display any status to track the transfer details when a circuit is transferred.

Resolution

The code has been modified and now the application displays Change (Transfer) in the Activity field in the design section of CLR for the circuits that are transferred from one customer to another.

13345313

APPSERVER

Problem

When servers are uncommented in the gateway.ini file, you get the following error in the appserverlog.xml file:

The server encountered the following Error: Naming service error:java.lang.NoClassDefFoundError:weblogic/rmi/internal/Skeleton.

Resolution

The code has been modified and now you do not get this error in the appserverlog.xml file for every server that is uncommented in gateway.ini file.

10132043

ENG

Problem

When you close the Connection Positions window by clicking the Close icon (on the top right corner), the Connection summary window displays the connection positions as None.

Resolution

The code has been modified and now the Connection summary window does not display the connection positions as None when you close the Connection Positions window by clicking the Close icon (on the top right corner).

8305303

ENG

Problem

The USO order number is not displayed correctly on the CLR/DLR Address Details tab.

Resolution

The code has been modified and now the USO order number is displayed correctly on the CLR/DLR Address Details tab.

13347085

ENG

Problem

The Provisioning Assistant Working Path window displays garbage characters.

Resolution

The code has been modified and now the Provisioning Assistant Working Path window does not display garbage characters.

13767773

ENG

Problem

When a circuit is opened in read-only mode, the external weblink added for the connection is not displayed.

Resolution

The code has been modified and now the external weblink added for the connection is displayed when a circuit is opened in read-only mode.

13487932

ENG

Problem

MetaSolv Solution shuts down when you view CLR Preview for the circuit.

Resolution

The code has been modified and now MetaSolv Solution does not shut down when you view CLR Preview for the circuit.

12432544

ENG

Problem

The Calendar window is not displayed for leased circuit user data when the User Data field is set up as a date. The date has to be entered manually.

Resolution

The code has been modified to display the Calendar window for leased circuit user data when the User Data field is set up as a date. The Calendar window is displayed when you right-click in the Date field.

13079481

EWO

Problem

MetaSolv Solution locks EWO orders after a read-only user views and closes these orders.

Resolution

The code has been modified and now MetaSolv Solution does not lock EWO orders that have been viewed and closed by a read-only user.

9959396

INFRA

Problem

The CO Exchange Area window's OCN field does not save properly when there are multiple OCN values with the same company name. The CO Exchange Area window only saves the first value from the sorted list.

Resolution

The code has been modified and now the CO Exchange Area window's OCN field saves properly even if there are multiple OCN values with the same company name.

10336122

ISR

Problem

The sorting order in the Service Request Wizard and the Service Request Notes windows is not in sync.

Resolution

The code has been modified and now the sorting order for the Service Request Wizard window and the Service Request Notes window is done by "date entered" and the retrieval of notes in both the windows is in the same order.

10104768

LSR

Problem

The Street Number on Directory Listing (DL) PSR maps to the incorrect field on LSR.

Resolution

The code has been modified and now the Street Number that is populated on DL PSR maps to the correct field on LSR.

12999263

MIP

Problem

Unable to create orders with Connector item types containing telephone numbers through XML API and CORBA API.

Resolution

The code has been modified and now you can create orders with Connector item types containing telephone numbers through XML API and CORBA API.

10280387

MIP

Problem

When a PSR order is supp canceled, the TN Category and Subcategory description data does not get copied to the new suffix. This data is copied to the next suffix when a TN is disconnected and the TN Recall process is run against the number.

Resolution

The code has been modified and now the TN Category and Subcategory description data is copied to the new suffix when the PSR order is supp canceled. The new suffix will be in Pending status while the old suffix will move to Unavailable status.

10142932

MIP

Problem

When running the metasolvordertaskeventstatuschange.jpd XML API, the gateway event notes array gets initialized with no values and with the Allow to Maintain Gateway Event Notes preference set to Y, the following error message is displayed:

Exception: IntegrationEventManager::Preference for  Gateway Event Notes is set as 'N'.

Resolution

The code has been modified and now no error message is displayed when running the metasolvordertaskeventstatuschange.jpd XML API with the Allow to Maintain Gateway Event Notes preference set to Y.

13248508

OTHER

Problem

The Export Visible Graphics and Export All Graphics menu options in the Provisioning Plan Maintenance window are not working as expected.

Resolution

The code has been modified and now the graphics are correctly exported when you right-click on the PERT Chart in the Provisioning Plan Maintenance window and select either Export Visible Graphics or Export All Graphics.

12884217

PLANT

Problem

The Plant API option is not displayed in the Software Options window.

Resolution

The code has been modified and now the Plant API option is displayed in the Software Options window.

9729002

PSR

Problem

On the Listings tab of the Directory Service Request window, when you select the Street suffix as Lane - LN, this data is saved in the database as "Ln" instead of "LN."

Resolution

The code has been modified and now on the Listings tab of the Directory Service Request window, when you select the Street suffix as Lane - LN, this data is saved in the database as "LN."

10203811

PSR

Problem

When you suspend all "In Service" service items for a customer account and if there are any disconnected service items tied to that customer account, the customer account status is not changed to Suspended.

Resolution

The code has been modified and now when you suspend all "In Service" service items for a customer account and if there are any disconnected service items tied to that customer account, the customer account status is changed to Suspended.

9694345

PSR

Problem

The name of the Enable Copy of Pending Items preference should be changed as this name does not reflect its functionality.

Resolution

The Enable Copy of Pending Items preference has been renamed as Allow multiple open orders against service items.

13333239

PSR

Problem

Group Assignment fails if a circuit rides on an equipment that has been associated to a network element whose name is more than 50 characters.

Resolution

The code has been modified and now Group Assignment works fine even if a circuit rides on an equipment that has been associated to a network element whose name is more than 50 characters.

12857627

PSR

Problem

The circuit ID is not populated in the Circuit ID field in the Work Queue Manager window for the orders that are created and validated through the StartOrderSync XML API.

Resolution

The code has been modified and now the circuit ID is populated in the Circuit ID field in the Work Queue Manager window for the orders that are created and validated through the StartOrderSync XML API.

9141182

PSR

Problem

A dash is not included between service item and sequence.

Resolution

The code has been modified and now a dash is added between service item and sequence.

12586791

PSR

Problem

When creating an expression for new Rules and Behaviors, the provisioning plan query does not retrieve all the valid active provisioning plans.

Resolution

The code has been modified and now the provisioning plan query retrieves all the valid active provisioning plans.

13351434

TECH

Problem

In all the Search windows, the Add New button appears enabled even if it is disabled through security permissions.

Resolution

The code has been modified and now in all the Search windows, the Add New button appears disabled if it has been disabled through security permissions.

12397308

TROUBLE

Problem

Unable to search and add a trunk circuit by using two six code from the Trouble Ticket Search window.

Resolution

The code has been modified and now you can search and add a trunk circuit by using two six code from the Trouble Ticket Search window. You can also search for the same circuit from Connection Design Search window.

12876880

USER

Problem

If the Change Password Upon Initial Logon preference is set to Y, MetaSolv Solution does not prompt you to change the password at the first logon even if the user name and the password are different.

Resolution

The code has been modified and now if the Change Password Upon Initial Logon preference is set to Y, the application prompts you to change the password at the first logon even if the user name and the password are different. If you change the password to make it same as the user name, MetaSolv Solution prompts you to change your password at a subsequent logon.

13598186

UTILITIES

Problem

The DST Provisioning Tool is not allowing to bind to a different port other than 1521, which is hardcoded internally when using with thin client driver option.

Resolution

The following changes have been made:

  • Hard coding of the port has been removed when using the thin client driver option.

  • The DST.properties file has been updated with the modified usage properties.

11661904

UTILITIES

Problem

In MetaSolv Solution Utilities, when you navigate to Options, then Custom Attributes, then Associate. The Customer Attribute Usage window displays Error #60 when updating the Allow Duplicates value to No Duplicates for Connection on a custom attribute that was participating in a concatenation relationship.

Resolution

The code has been modified and now the Customer Attribute Usage window does not display Error #60 when updating the Allow Duplicates value to No Duplicates for Connection on a custom attribute that was participating in a concatenation relationship.

11927985

UTILITIES

Problem

External Weblinks are not displayed when viewing circuits from the Customer Account window.

Resolution

The code has been modified and now External Weblinks are displayed when viewing circuits from the Customer Account window.

10183389

WRKMGMT

Problem

The Tech Translation Sheet text is difficult to read in preview mode.

Resolution

To read the text, increase the magnification of the data window to 150% and then decrease it to 110%.

10151701

WRKMGMT

Problem

If a task was rejected and a task that was previously in the system queue was reopened and moved to a manual queue, the System check box would still be selected in the Service Request Tasks window.

Resolution

The code has been modified and now the System check box in the Service Request Tasks (Task Generation) window is not selected in the Service Request Tasks window when a task is rejected and the work queue is changed from the System queue to a manual queue.


Known Issues

Table 1-2 lists the known issues in MetaSolv Solution 6.2.1.

Table 1-2 Known Issues

Bug Number Component Notes

13707722

ENG

Issues

The order of the rows in the grooming workspace may change when the Groom To or the Modify Search option is selected.

13835069

ENG

Issues

The layout in the Schematic Design view can get misaligned after you process the groom.

Workaround

You can manually align the components in the Schematic Design view.