Oracle® Communications Design Studio

Release Notes

Release 7.4

E99956-01

October 2018

Oracle Communications Design Studio Release Notes, Release 7.4

E99956-01

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

- Technology Updates

- Conceptual Model Synchronization with External Catalog

- Importing Exchange Format Data from External Catalog

- Log4j Removal from CMWS

- Realization Support for Configuration Item Hierarchy

- Fixes in This Release

- Known Problems

- CMT Tool Download Information is Incorrect

- XML Catalog Files Appear in the Problems View

- Help Page is Not Displayed from Import XF Wizard

2 Design Studio for ASAP

- Known Problems

- Activation Test Case Hangs and Fails for Design Studio in Systems with Multiple Interfaces or IP Addresses

- 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

- UI Customizability for Automated Tasks to Improve Fallout Management

- Known Problems

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

- OSM Solution Sometimes Fails to Build Due to SocketTimeOut Exception

- Composite Cartridge Behavior Details are Inconsistent in Task Level

- Composite Data View is Inconsistent Behavior on Task and Order Level

- Order Level Data Instance Behavior Configuration is Not Getting Refreshed in Task

- Getting Project Upgrade Error for Newly Imported CommonDDProject

- Behavior Defined for Node Should Not be Editable in Task Editor Composite Data

- 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

E99956-01

October 2018

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.4:

- Technology Updates

- Conceptual Model Synchronization with External Catalog

- Log4j Removal from CMWS

- Realization Support for Configuration Item Hierarchy

Note:
The Design Studio Online Help was not updated for the features delivered in this release.

Technology Updates

Design Studio 7.4 is compatible with Oracle Enterprise for Eclipse version 12.2.1.7 (or later), based on Eclipse Oxygen 4.7.0. Design Studio leverages the new features and capabilities of Eclipse version 4.7.0 to provide a better environment for solution designers and software developers.

Conceptual Model Synchronization with External Catalog

Design Studio 7.4 enables you to import conceptual model entities from external catalogs. You import external definitions using Exchange Format XML files. Earlier versions of Design Studio enabled you to use the Exchange Format XML files only for exporting entities. This enhancement enables you to also import entities, more fully integrating Design Studio into an overall design environment that includes other systems.

You can import the following conceptual model entities, along with supporting data elements, data schemas, and model projects, into Design Studio:

- Product

- Customer facing service

- Resource facing service

- Resource

- Service action

- Technical action

The Exchange Format XML file is a consistent representation of Design Studio entities and external catalog system entities. You can import multiple entities across multiple projects with a single input XML file.

You can perform a partial or complete import of the XML file. A partial import is intended to preserve existing definitions, allow new projects, entities, and elements to be added, and allow information on existing projects, entities, and elements to be added or updated. In addition to supporting incremental operations, complete imports remove enumerations and information from existing entities when this information is not included in the import file.

For more information on performing the import, see Importing Exchange Format Data from External Catalog.

Note:
Partial import is the default option.

A partial import:

- Creates new projects, entities, and elements if they are not present in the workspace

- Appends new information and updates the existing information for entities or elements

- Leaves existing information on entities and elements, if information is not included in the import file

Note:
Partial import does not support the removal of information from existing entities or elements.

A complete import:

- Creates new entities or elements if they are not present in the workspace

- Replaces existing information on entities and elements with information that is provided in the import file

- Removes information from existing entities or elements if that information is not included for these entities or elements in the input file

- Handles enumerations as follows:

- Removes existing information of entities or elements if they are missing from the input file

- Updates existing entities or elements with information that is modified in the input file

- Handles non-list or elements (for example, Copyright information, project name) as follows:

- Defaults existing entities or elements with information that is missing from the input file

- Updates existing entities or elements with information modified in the input file

Note:
Unique external identifiers must be provided for new instances of projects, entities, and elements that are imported.
Identifiers for existing or imported projects, entities, and elements cannot be modified by import operations.

The limitations on Conceptual Model imports are as follows:

- Import operations will not update sealed projects, read-only projects, or read-only entities

- Import operations will not rename existing projects, entities, or elements

- Import operations will not delete existing projects, entities, or elements of an entity

Importing Exchange Format Data from External Catalog

To import exchange format data from an external catalog:

1. Open Design Studio.

2. Ensure all changes made in workspace are saved.

3. Run a full build to ensure all model files are up-to-date.

4. Open Studio Projects or Solution view.

5. Open the Context menu by right-clicking the page.

6. Select Import > Import Exchange Format.

7. Click Browse and select the required exchange format file (.xml file).

8. (Optional) Select Complete for a complete import.

9. Click Next.
The Summary Page appears.

10. Check all the entities and elements that are imported and then click Finish.
A dialog box appears to open the generated import log.

11. Click Yes to open the log file, or click No to go back to the previous view.

Log4j Removal from CMWS

Design Studio 7.4 does not support Log4j for modifying log levels. You can now modify them in WebLogic server using WLST commands.

Realization Support for Configuration Item Hierarchy

Design Studio 7.4 supports a new relationship type called ConfigHierarchy.

You can use the ConfigHierarchy relationship to model a specific run-time constraint in Oracle Communications Unified Inventory Management (UIM) in which no real entity is referenced. Instead, an intermediate hierarchical structure is referenced at run-time. You can use this new relationship to characterize the relationship between a resource facing service and a resource component. The ConfigHierarchy relationship indicates that a UIM realization of a resource component should result in a hierarchy of configuration items and should not generate a UIM entity.

Fixes in This Release

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

Table 1-1 Fixes in Design Studio Release 7.4 Platform

Service Request (SR) Number

BugDB Number

Description

n/a

25505298

Application Role Naming Conflicts: Design Studio adds application roles to all projects while upgrading from releases before Design Studio 7.3.5. The application role names were creating naming conflict errors. This was fixed.

n/a

25509902

Error Preventing Multiple Specialized Action Names for an Action Code: While defining multiple specialized action names for the same action code in a technical action family, Design Studio was displaying an error stating that the action code already existed. This was fixed.

Known Problems

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

- CMT Tool Download Information is Incorrect

- XML Catalog Files Appear in the Problems View

- Help Page is Not Displayed from Import XF Wizard

CMT Tool Download Information is Incorrect

BugDB: 26550193

Problem: The Design Studio Developer's Guide incorrectly mentions that the CMT tool can be downloaded directly from the e-delivery site. Instead, the CMT tool is bundled within the Design Studio media pack.

XML Catalog Files Appear in the Problems View

BugDB: 24821492

Problem: 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.

Workaround: Perform a clean and build of all projects in the workspace.

Help Page is Not Displayed from Import XF Wizard

BugDB: 28648349

Problem: Clicking (?) from the Import XF wizard does not display the Help page.

2 Design Studio for ASAP

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

- Known Problems

Known Problems

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

- Activation Test Case Hangs and Fails for Design Studio in Systems with Multiple Interfaces or IP Addresses

- NEP Deploy Fails Intermittently

Activation Test Case Hangs and Fails for Design Studio in Systems with Multiple Interfaces or IP Addresses

BugDB: 21694483

Problem: The provisioning of Activation test cases hangs and fails (with or without VPN), if the system hosting Design Studio is configured with more than one Network Interface or IP address, or if the Hostname of the system maps to a network address that the WebLogic server cannot contact.

Workaround: Add the following to the eclipse.ini file: "-Dweblogic.corba.client.bidir=true"

NEP Deploy Fails Intermittently

BugDB: 22960169

Problem: Unable to establish a connection to Oracle WebLogic Server through the NEP map option (NEP deploy fails intermittently).

Workaround: Perform the following:

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

- Ensure that the META-INF/activation-model.xml file has been generated. Otherwise, perform 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.4 includes several general quality improvements delivered in this release.

4 Design Studio for Network Integrity

Oracle Communications Design Studio for Network Integrity release 7.4 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 Order and Service Management (OSM) release 7.4.

- New Features

- Known Problems

- Design Studio Cartridge Migration

New Features

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

Note:
The Design Studio Online Help has not been updated for the features delivered in this release.

UI Customizability for Automated Tasks to Improve Fallout Management

With this release, automated task definition has been enhanced with the ability to include the specification of behaviors for fallout purposes. You can now define behaviors for automated tasks as well. Behaviors provide a way to extend the functionality and appearance of task data. Each behavior type performs an action; for example, calculating or validating data, or displaying fields in read-only or read-write modes.

When defining behaviors at the task level, you can use the Task editor Task Data tab to create the behavior, the Properties view for the behavior to refine the behavior information, and the Task editor Behaviors tab to view all of the behaviors defined for a task.

To define a behavior at the task level:

1. From the Studio menu, select Show Design Perspective.

2. Use the Studio Projects view.

3. Double-click the automated task entity for which you are defining the behavior.
Design Studio displays the task in the Automated Task editor.

4. In the Task Data area, select the data node upon which to model the behavior.

5. Right-click in the Behaviors area and select Add Behavior.

6. Select a behavior from the list.

Note:
The Calculation, Event, and Lookup behavior types cannot be defined for structured data elements. These behaviors are not relevant because structured data elements do not represent actual data and cannot be acted upon in this way.

Design Studio adds the behavior to the Behaviors area. Each behavior type enables you to dynamically control a specific aspect of your order data model.

7. In the Behaviors area, click the behavior to open the Properties view.
The Properties view is displayed with the set of properties that you must define for the corresponding behavior type.

8. Click Save.

Note:
After you define the behavior properties, you can click the Task editor Behaviors tab to review all of the behavior properties information defined for the task. See Design Studio Modeling OSM Processes Online Help for more information about behaviors.

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

- Composite Cartridge Behavior Details are Inconsistent in Task Level

- Composite Data View is Inconsistent Behavior on Task and Order Level

- Order Level Data Instance Behavior Configuration is Not Getting Refreshed in Task

- Getting Project Upgrade Error for Newly Imported CommonDDProject

- Behavior Defined for Node Should Not be Editable in Task Editor Composite Data

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

BugDB: 22203278

Problem: 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.

Workaround: 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

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

Workaround: Increase the value of Separate JRE timeout setting to 40000.

To increase the value of the Separate JRE timeout setting:

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

2. In the Preferences navigation tree, select Ant.

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

4. Click OK.

Composite Cartridge Behavior Details are Inconsistent in Task Level

BugDB: 28518246

Problem: Behaviors that are inherited from the Composite Cartridge view are not accurately loaded at the Composite Data view window of a manual or an automated task. There is no functional loss because of this issue, but you cannot see accurate data in this behavior.

Workaround: You can go to the Composite Cartridge view to view the accurate behavior data.

Composite Data View is Inconsistent Behavior on Task and Order Level

BugDB: 28526024

Problem: The Behavior window is greyed out at Task level, but at Order level it is not greyed out. Even though the Behavior window is not greyed out at Order level, the system does not allow you to add any behaviors. Therefore, this does not affect any functionality.

Order Level Data Instance Behavior Configuration is Not Getting Refreshed in Task

BugDB: 28531244

Problem: Task level data behaviors are not getting refreshed.

Workaround: Close the tasks for which behaviors are not refreshed and then reopen them.

Getting Project Upgrade Error for Newly Imported CommonDDProject

BugDB: 28706381

Problem: While importing common data dictionary, the Project Upgrade wizard is not loaded. Instead, errors such as "Project Upgrade Error" are received at the end of import.

Workaround: Close the project and reopen it.

Behavior Defined for Node Should Not be Editable in Task Editor Composite Data

BugDB: 28712854

Problem: The Composite Data View tab allows you to modify a behavior that is added in task data editor. The Composite Data View tab only shows behavior details (without populating Node element details) which are added in task data editor.

In general, you can manipulate behavior data in the Task Data window at the Task level. But, because of this issue, you can also modify behaviors from the Composite Data view. There is no functional loss in modifying data at the Composite Data view level. Data is stored accurately even after modifying behaviors at the Composite Data view level.

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 Design Studio Order and Service Management Cartridge Migration Guide for release 7.3.2, which is available on 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-2018, 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.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability 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 Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability 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 pre-General Availability 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.