Oracle® Communications Design Studio

Release Notes

Release 7.3.5

E79089-01

February 2017

Oracle Communications Design Studio Release Notes, Release 7.3.5

E79089-01

Copyright © 2004, 2017, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Related Documents

- Documentation Accessibility

- Document Revision History

1 Design Studio Platform

- New Features

- Action Parameter Enhancement for ASAP MCLI

- Design Studio Express Installer Enhancement

- Improved Realization Field Layout

- Support Multi-Value EntityRef Tokens

- Technical Action Family Consolidation

- Technology Updates

- Fixes in This Release

- Known Problems

- Application Role Naming Conflicts

- XML Catalog Files Appear in the Problems View

- Error Preventing Multiple Specialized Action Names for an Action Code

2 Design Studio for ASAP

- Fixes in This Release

- Known Problems

- Activation Test Cases Failing

- NEP Deploy Fails Intermittently

3 Design Studio for Inventory

4 Design Studio for Network Integrity

5 Design Studio for Order and Service Management

- New Features

- Reduced Memory Footprint for Cartridges

- Fixes in This Release

- Known Problems

- The "Do not rollback during undo" Setting is Not Being Contributed

- OSM Solution Sometimes Fails to Build Due to SocketTimeOut Exception

- Removed Features

- Customer Asset Manager and Account Manager Modules Removed

- Design Studio Cartridge Migration

Preface

This document provides release notes for Oracle Communications Design Studio Platform and all Design Studio features. Each chapter describes, if applicable for this release, Design Studio new features, fixes, and known problems.

Audience

This document is intended for designers, developers, testers, and administrators responsible for modeling and managing Oracle Communications products in Design Studio.

Related Documents

For more information, see the following documents in the Oracle Communications Design Studio documentation set:

- Design Studio Installation Guide: Describes the requirements and procedures for installing Design Studio.

- Design Studio System Administrator's Guide: Describes information about administering Oracle Communications Design Studio. This guide includes information about configuring deployment settings for test environments, backing up and restoring Design Studio data, and automating builds.

- Design Studio Concepts: Explains how to use Design Studio to manage and configure data for use across Oracle Communications service fulfillment products. This guide provides a conceptual understanding of Design Studio.

- Design Studio Developer's Guide: Provides common solution development guidelines and best practices for cartridge design and development. The recommendations included in this guide apply to all the solutions that leverage one or more of the supported Oracle Communications applications.

- Design Studio Security Guide: Provides an overview of security considerations, information about performing a secure installation, and information about implementing security measures in Design Studio.

- Design Studio Help: Provides step-by-step instructions for tasks you perform in Design Studio.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Document Revision History

The following table lists the revision history for this book.

Version

Date

Description

E79089-01

February 2017

Initial release.

1 Design Studio Platform

This chapter provides release notes for Oracle Communications Design Studio Platform.

- New Features

- Fixes in This Release

- Known Problems

New Features

This section includes information about new features introduced in release 7.3.5:

- Action Parameter Enhancement for ASAP MCLI

- Design Studio Express Installer Enhancement

- Improved Realization Field Layout

- Support Multi-Value EntityRef Tokens

- Technical Action Family Consolidation

- Technology Updates

Action Parameter Enhancement for ASAP MCLI

Design Studio 7.3.5 enables you to tag a simple data element with a new Target tag. If you run a design pattern that realizes an ASAP CSDL or ASDL structure from a technical action, Design Studio automatically maps the tagged data element to the Atomic Action Label field and populates this field with the value MCLI. The MCLI value represents the target of the action.

See Design Studio Help for more information.

Design Studio Express Installer Enhancement

Design Studio 7.3.5 enables offline installation (using the existing Design Studio installation script) for the BIRT (Business Intelligence and Reporting Tool) feature and for the Graphical Editing Framework Zest Visualization Toolkit feature. Both features are required prerequisites for Design Studio installation.

For example, if you intend to install Design Studio onto a run-time server that does not have access to the public Internet (or, if you want to install Design Studio to a server only to build and deployment cartridges), you can now install the prerequisite features offline.

See Design Studio Installation Guide for more information about

Improved Realization Field Layout

Design Studio 7.3.5 includes changes to the order and appearance of some fields on the Conceptual Model editor Properties page. These changes are intended to improve understanding of the expected behavior of realization settings, reduce UI clutter, and ensure a consistent, logical presentation of fields.

See Design Studio Help for more information.

Support Multi-Value EntityRef Tokens

Design Studio 7.3.5 includes a new element that design pattern developers can use to enable design pattern users to select multiple entities from a list.The new element is called allowMultiple. This element can take a value of true or false, and it is an optional element available to the EntityRef token.

See the Design Studio Developer's Guide for more information.

Technical Action Family Consolidation

Design Studio 7.3.5 improves the technical action design experience by:

- Providing associations between technical actions and application roles. Application roles represent types of downstream delivery systems that are responsible for specific types of delivery, such as activation, supply chain management, work force management, and so forth.

- Enabling you to associate action codes in a technical action family with specialized action code names. A specialized action code is an action code that you rename to align a technical action with an application role (a downstream fulfilment system). For example, you may need to rename the Create action code to Activate to better align with code defined in a downstream activation system. For a supply chain management system, you may need to rename the Create action code to Ship.

- Providing associations between technical actions and targets. Targets can be any resource in the work space or, less frequently, a resource facing service.

- Providing a new Data Map tab for technical actions, where you can view and define the applicability of data elements to the actions in an action family. For example, you can specify whether a data element value must be supplied to or returned by each action in an associated action family.

- Removing unnecessary associations between technical actions and fulfillment patterns and technical actions and fulfillment functions.

See Design Studio Help for more information.

Technology Updates

Design Studio 7.3.5 is compatible with Oracle Enterprise for Eclipse version 12.2.1.4 (or later), based on Eclipse Neon 4.6.0. Design Studio leverages the new features and capabilities of Eclipse version 4.6.0 to provide a better environment for solution designers and software developers. Also, Design Studio 7.3.5 supports Windows 10 (64-bit).

See Design Studio Installation Guide for more information.

Fixes in This Release

Table 1-1 lists the Design Studio Platform release 7.3.5 fixes and provides a brief description of the resolution.

Table 1-1 Fixes in Design Studio Release 7.3.5 Platform

Service Request (SR) Number

BugDB Number

Description

n/a

23701085

Design Studio now filters the Comprehensive Entity Standard Detail report to ignore elements with missing typeId values. This filter prevents duplicate element relationship details from appearing in the Element Summary section.

n/a

24324302

Clean builds of workspaces that include Inventory projects with resource realization now complete successfully.

n/a

25359054

From the Studio Projects view, you can now delete closed projects from a Design Studio workspace.

n/a

24305122

When defining attributes of data elements, the Unbounded attribute now overrides the value defined in the Maximum Length field.

Known Problems

This section describes existing software problems and any workarounds recommended to avoid the problems or reduce effects:

- Application Role Naming Conflicts

- XML Catalog Files Appear in the Problems View

- Error Preventing Multiple Specialized Action Names for an Action Code

Application Role Naming Conflicts

BugDB: 25505298

When upgrading to Design Studio release 7.3.5, Design Studio adds application roles to all projects. The application role names can create naming conflict errors.

To work around this problem, delete all application roles from all projects with names that begin with OracleComms_Model_Base. However, do not delete the application roles from the OracleComms_Model_Base project.

XML Catalog Files Appear in the Problems View

BugDB: 24821492

The Problems view displays errors for invalid XML catalog files, such as .xsd, .xml, .xsl, .html, .jsp, and .wsdl files. While these errors may not impact the project compilation, Oracle recommends that you correct these files.To work around this problem, perform clean and build of all projects in the workspace.

Error Preventing Multiple Specialized Action Names for an Action Code

BugDB: 25509902

When defining multiple specialized action names for the same action code in a technical action family, Design Studio may display an error to state that the action code already exists.

To work around this problem, do the following:

1. In the Action editor, click the Action Codes tab.

2. In the Specialized Action Code area, click Add.

3. In the Action Code field, click Select and select an action code.

4. In the Specialized Action Name field, enter the specialized name for the action code.

5. Click Cancel and then save the changes to the editor.
The action code and corresponding specialized action name appears in the table.

2 Design Studio for ASAP

This chapter provides release notes for Oracle Communications Design Studio for ASAP.

- Fixes in This Release

- Known Problems

Fixes in This Release

Table 2-1 lists the Design Studio ASAP release 7.3.5 fixes and provides a brief description of the resolution.

Table 2-1 Fixes in Design Studio Release 7.3.5 ASAP

Service Request (SR) Number

BugDB Number

Description

SR:3-13237154481

24753204

A new field, Compound Parameter Identification Token, now appears on the Project editor Locations tab. Use this field to identify the logic necessary to read compound parameters. You use an existing field, Indexed Parameter Identification Token, to identify the CSDL label suffix pattern for Indexed type parameters.

When importing projects from previous Design Studio versions, both of these fields are defined with the Indexed Parameter Identification Token field value. When you create new projects, both of these fields are initially defined with the [] Square Brackets value.

Also, a new field, Index Parameters Default Suffix, now appears on the Oracle Design Studio Activation Preferences page. When enabled, the CSDL label suffix value for Indexed type parameters is defaulted with ++ in the generated ASADL.xml file for all the projects in the workspace.

Known Problems

This section describes existing software problems and any workarounds recommended to avoid the problems or reduce effects:

- Activation Test Cases Failing

- NEP Deploy Fails Intermittently

Activation Test Cases Failing

BugDB: 21694483

Activation test cases fail intermittently (over VPN and when not using VPN) when running Design Studio 7.x versions with ASAP 7.x versions.

To work around this problem, add the following to the eclipse.ini file: "-Dweblogic.corba.client.bidir=true"

NEP Deploy Fails Intermittently

BugDB: 22960169

Users are unable to establish a connection to Oracle WebLogic Server through the NEP map option (NEP deploy fails intermittently).

To work around this problem, do the following:

- Ensure that the base cartridge project (the source project that contains the NEs) is in an open state.

- Ensure that the META-INF/activation-model.xml file has been generated, or complete a full clean and build to regenerate the activation-model.xml file.
NEP deploy fails intermittently if the activation-model.xml file corresponding to the mapped NE has not been generated and saved to the cartridgeBin/cartridgeBuild location.

3 Design Studio for Inventory

Oracle Communications Design Studio for Inventory release 7.3.5 includes several general quality improvements delivered in this release.

4 Design Studio for Network Integrity

Oracle Communications Design Studio for Network Integrity release 7.3.5 includes several general quality improvements delivered in this release.

5 Design Studio for Order and Service Management

This chapter provides release notes for Oracle Communications Design Studio for Oracle Communications Order and Service Management (OSM) release 7.3.5.

- New Features

- Fixes in This Release

- Known Problems

- Removed Features

- Design Studio Cartridge Migration

New Features

This section includes information about new features introduced in release 7.3.5.

Reduced Memory Footprint for Cartridges

In this release, cartridges with a target version of 7.3.5 or greater do not perform an automation build in order to be compatible with the "Reduced Cartridge Memory Footprint" feature of OSM 7.3.5. These changes removed the need for an automationBuild.xml file for any cartridge with a target version of 7.3.5 or greater.

For cartridges targeted to earlier versions of OSM, the automation build remains unchanged and the cartridge will be built and packaged compatible with the older target version of OSM.

Fixes in This Release

Table 5-1 lists the Design Studio for OSM fixes and provides a brief description of the resolution in Design Studio for OSM 7.3.5.

Table 5-1 Fixes in Design Studio for Order and Service Management Release 7.3.5

Service Request (SR) Number

BugDB Number

Description

3-13475776371

24850169

Some cartridges were throwing a null pointer exception and failing to build during upgrade. This has been fixed: the null pointer exception is no longer being thrown.

3-13330898231

24707317

If tasks were not configured with execution modes, they were not being included in the cartridge build. This was causing the following error to be generated: "Error attempting to parse XML file" due to the missing task files. This has been fixed: the build files are now being generated correctly.

3-10913327071

21286699

The Order-to-Activate cartridges were generating metadata modeling errors relating to transformation stages. This has been fixed: the Design Studio schema has been updated.

Known Problems

This section describes existing software problems and any workarounds recommended to avoid the problems or reduce effects:

- The "Do not rollback during undo" Setting is Not Being Contributed

- OSM Solution Sometimes Fails to Build Due to SocketTimeOut Exception

The "Do not rollback during undo" Setting is Not Being Contributed

BugDB: 22203278

In solutions where the order template is contributed from order components, the data element's "Do not rollback during undo" setting is not inherited by the order template.

To work around this issue, manually set the value of the data element's "Do not rollback during undo" property on the order template.

OSM Solution Sometimes Fails to Build Due to SocketTimeOut Exception

BugDB: 22691246

OSM Solution Automation build fails periodically due to a SocketTimeOut exception.

To work around this issue, increase the value of Separate JRE timeout setting to 40000.

To increase the value of the Separate JRE timeout setting:

1. In Design Studio, from the Window menu, select Preferences.

2. In the Preferences navigation tree, select Ant.

3. In the Separate JRE timeout (ms) field, enter 40000.

4. Click OK.

Removed Features

The following feature is removed in release 7.3.5.

Customer Asset Manager and Account Manager Modules Removed

The Customer Asset Manager and Account Manager modules have been removed. Oracle recommends that you use corresponding functionality in Oracle Configure, Price, Quote (CPQ) Cloud for your hybrid cloud solution.

Design Studio Cartridge Migration

If you upgrade to Order and Service Management 7.x from a prior version of OSM and your cartridges were developed with OSM Administrator tool, Oracle recommends that you migrate your cartridges into Oracle Communications Design Studio. Use Design Studio as the tool to design and deploy OSM 7.x cartridges. The recommended migration procedure, common migration issues, and issue resolutions are documented in release 7.3.2 Design Studio Order and Service Management Cartridge Migration Guide, which is available at the Oracle Help Center:

http://docs.oracle.com/en/industries/communications/design-studio/index.html

Note:
If your cartridges do not require ongoing modification, you can export them from the current version (pre-7.x) and import them into OSM 7.x using the XML Import/Export tool without using Design Studio. However, Oracle recommends that you migrate all cartridges to Design Studio, unless they do not need any modification or re-deployment.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2017, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.