oracle® communications design studio › cd › e35785_01 › pdf › e38195.pdf · design...

Oracle® Communications Design StudioRelease Notes

Release 7.2.2

E38195-03

July 2013

Oracle Communications Design Studio Release Notes, Release 7.2.2

E38195-03

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

iii

Contents

Preface ................................................................................................................................................................. v

Audience....................................................................................................................................................... vDocumentation Accessibility ..................................................................................................................... vRelated Documents ..................................................................................................................................... vDocument Revision History ...................................................................................................................... vi

1 Design Studio Platform

New Features in Release 7.2.2 ................................................................................................................ 1-1Design Patterns................................................................................................................................... 1-1Guided Assistance.............................................................................................................................. 1-1Documentation Enhancements ........................................................................................................ 1-2

Fixes in Release 7.2.2................................................................................................................................ 1-2Known Problems in Release 7.2.2 ......................................................................................................... 1-2

Project Upgrades Cause Source Control Errors............................................................................. 1-3Deprecated Features................................................................................................................................. 1-3

2 Design Studio for ASAP

3 Design Studio for Inventory

New Feature in Release 7.2.2.4 ............................................................................................................... 3-1Assigning and Referencing Channelized Connectivities in Service Configurations ............... 3-1

New Features in Release 7.2.2 ................................................................................................................ 3-1TDM Facility and Property Location Extension ............................................................................ 3-1Rate Codes........................................................................................................................................... 3-1


Property Location and TDM Facility Characteristics Appear Incorrectly in the UIM Run-Time Application 3-2Cannot Rename Configuration Items Using Spaces ..................................................................... 3-2Deleting Entities Generates Errors .................................................................................................. 3-3Reference to Documentation is Incorrect........................................................................................ 3-3

4 Design Studio for Network Integrity

New Features in Release 7.2.2 ................................................................................................................ 4-1User Interface Enhancements ........................................................................................................... 4-1

iv

Specification Enhancements ............................................................................................................. 4-1Shared Specifications with Unified Inventory Management....................................................... 4-1Data Modeling Enhancements ......................................................................................................... 4-2Characteristics Enhancements.......................................................................................................... 4-2Scan Parameter Enhancements ........................................................................................................ 4-2

Known Problems in Release 7.2.2 ......................................................................................................... 4-2Cannot Deploy Cartridges to Managed Server in a Clustered Environment ........................... 4-2Cannot Rename Characteristic from Specification Editor............................................................ 4-3Deleting Entities Generates Errors .................................................................................................. 4-3Goto Reference Not Implemented for Editors ............................................................................... 4-3Validation Error After Renaming Scan Parameter Group ........................................................... 4-3

5 Design Studio for Order and Service Management

Design Studio Cartridge Migration Analysis..................................................................................... 5-1New Features in Release 7.2.2.1 ............................................................................................................. 5-1

Enhancements for Honoring Order Item Requested Delivery Dates......................................... 5-2Support for Rule-Based Compensation Strategy........................................................................... 5-2

New Features in Release 7.2.2 ................................................................................................................ 5-2Support for Importing High-Complexity Cartridges ................................................................... 5-2Design Patterns for OSM................................................................................................................... 5-3


Manual Steps Required for Upgrading Custom Automation Plug-ins ..................................... 5-4Model Variable Can Be Picked Up From Wrong Cartridge ........................................................ 5-4Imported Model File Causes Project Upgrade Error Message .................................................... 5-4

v

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.

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

Documentation AccessibilityFor 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 SupportOracle customers 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.

Related DocumentsFor 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.

vi

■ 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.

Document Revision HistoryThe following table lists the revision history for this book.

Version Date Description

E38195-01 January 2013 Initial Release

E38195-02 March 2013 Describes enhancements for honoring order item requested delivery dates and for rule-based compensation strategies. See "Enhancements for Honoring Order Item Requested Delivery Dates" and "Support for Rule-Based Compensation Strategy" for more information.

E38195-03 July 2013 Describes enhancements for assigning or referencing channelized connectivity entities as configuration items in service configurations. See "Assigning and Referencing Channelized Connectivities in Service Configurations" for more information.

1

Design Studio Platform 1-1

1Design Studio Platform

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

■ New Features in Release 7.2.2

■ Fixes in Release 7.2.2

■ Known Problems in Release 7.2.2

■ Deprecated Features

New Features in Release 7.2.2This section describes the new features for Design Studio Platform.

■ Design Patterns

■ Guided Assistance

■ Documentation Enhancements

Design PatternsDesign Studio now includes design patterns, which are templates (or established patterns) that enable automation of complex, repeatable tasks, and enables team members with varying levels of skill to complete these tasks.

In addition to the design patterns delivered with Design Studio, you can also use new design pattern wizards to create and configure your own design patterns, and other team members can implement those design patterns. You use these wizards to create complex sets of entities and relationships using a task-oriented user interface. These wizards eliminate the need for coding and complex configuration, which can reduce errors, simplify modeling, and increase productivity.

For example, an IT department can develop design patterns to enable network engineers to manage VPNs. These design patterns might facilitate tasks such as creating and deleting VPNs, adding sites and removing sites, and so forth.

Guided AssistanceDesign Studio now includes guided assistance, a range of context-sensitive learning aids mapped to specific editors and views in the user interface. For example, when working in editors, you can open the guided assistance to view related Help topics, design patterns, and recorded presentations that are applicable to that editor.

Fixes in Release 7.2.2

1-2 Design Studio Release Notes

You can create and implement new guided assistance by using design patterns delivered with Design Studio. These design patterns are preconfigured for guided assistance development and can help you create a directory structure to which guided assistance learning aids can be saved.

Documentation EnhancementsThree new Design Studio guides are now available:

■ Design Studio Concepts, which 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, which provides common solution development guidelines and best practices for cartridge design and development. The recommendations included in this guide apply to all of the solutions that leverage one or more of the supported Oracle Communications applications.

■ Design Studio System Administrator’s Guide, which describes information about administering 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 documentation is available from the Oracle software delivery Web site:

https://edelivery.oracle.com/

Fixes in Release 7.2.2The following table lists the Design Studio Platform release 7.2.2 fixes and provides a brief description of the resolution.

Known Problems in Release 7.2.2This section describes existing software problems and any workarounds recommended to avoid the problems or reduce effects.

Table 1–1 Fixes in Design Studio Release 7.2.2 Platform

Service Request (SR) Number BugDB Number Description

SR:3-4942345131 13561417 When manual or automatic tasks reference task data from an order, Design Studio no longer generates an error if you change the order name.

n/a 14576945 The Data Schema editor Settings and Characteristics tabs no longer appear when you select a child element in an editor data tree.

n/a 14483399 Characteristic tags can no longer be applied to child simple data elements.

n/a 14208060 You can now define display names in multiple languages for Design Studio model entities.

n/a 14615624 Design Studio now includes logic that generates a blank customization file when there are no characteristics associated with an extended entity.

n/a 14525721 Design Studio cartridge and POMS projects now support 5-digit version numbers.

Deprecated Features

Design Studio Platform 1-3

■ Project Upgrades Cause Source Control Errors

Project Upgrades Cause Source Control ErrorsBugDB number: 15838683

Design Studio projects should include a .studio file in source control, and projects that you previously upgraded might not include this file in source control.

If you check-out from Subversion a project that does not include a .studio file, Design Studio will initiate the project upgrade process, and in this scenario the upgrade process can produce unpredictable results.

To work around this problem, manually uncheck the .studio file derived flag (in the resource properties) before saving the project in source control.

Deprecated FeaturesThe studio.activation.importSar Ant task has been deprecated and is supported only for backwards compatibility.

Note: This issue does not affect Design Studio versions 3.1.x projects when upgrading to Design Studio 7.2.2.

Deprecated Features


2

Design Studio for ASAP 2-1

2Design Studio for ASAP

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

3

Design Studio for Inventory 3-1

3Design Studio for Inventory

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




New Feature in Release 7.2.2.4This section describes the new feature in Design Studio for Inventory Release 7.2.2.4. This release is required to support new features in UIM Release 7.2.2.2.

Assigning and Referencing Channelized Connectivities in Service ConfigurationsUIM 7.2.2.2 supports the ability to assign or reference channelized connectivities as configuration items in service configurations. To enable this functionality, Design Studio for Inventory now enables you to assign or reference the TDM Facility specification as a configuration item in Service Configuration specifications.

New Features in Release 7.2.2This section describes the new features for Design Studio for Inventory.

■ TDM Facility and Property Location Extension

■ Rate Codes

TDM Facility and Property Location ExtensionDesign Studio for Inventory now enables you to extend TDM Facility and Property Location entities by adding characteristics. The new editors that you use to extend these two entities include a subset of the tabs included in the Specification editor, and enable you to define user interface hints, layouts, and detailed entity information. When you define characteristics for these entities and deploy the cartridge to the UIM run-time environment, those characteristics apply to all instances of the entity.

Rate CodesDesign Studio for Inventory now includes a resource called rate code. A rate code is an industry-recognized form of identification for transmission signals, or the speed at with data flows from one point to another, through some type of logical or physical

Fixes in Release 7.2.2


medium. For example, a DS1 rate code refers to a transmission rate of 1.544 metabits per second (Mb/s) for T-Carrier technology.

A new Design Studio for Inventory base cartridge (ora_uim_basetechnologies) includes a predefined set of rate codes. A new Rate Code editor in Design Studio enables you to review the bit rate, unit of measure, and technology associated with each rate code.

You can associate a device interface specification with a rate code; the rate code will be applied to all new device interfaces created from the specification. The rate code on a device interface determines the technology and transmission rate the interface can support to terminate connectivity.

Fixes in Release 7.2.2Table 3–1 lists the Design Studio for Inventory fixes and provides a brief description of the resolution.


■ Property Location and TDM Facility Characteristics Appear Incorrectly in the UIM Run-Time Application

■ Cannot Rename Configuration Items Using Spaces

■ Deleting Entities Generates Errors

■ Reference to Documentation is Incorrect

Property Location and TDM Facility Characteristics Appear Incorrectly in the UIM Run-Time Application

BugDB: 14341399

When you modify the layout of characteristics associated with Property Location and TDM Facility entities, the entities do appear correctly in the UIM run-time application Create and Edit pages.

To work around this problem, in Design Studio open the Property Location or TDM Facility Extension editor, click the Layouts tab, then manually insert a new row between each of the characteristics in the Selected column.

Cannot Rename Configuration Items Using SpacesBugDB: 14562916

Table 3–1 Fixes in Design Studio for Inventory Release 7.2.2


n/a 4681584 The Design Studio project upgrade functionality now correctly migrates Entity Link drop down list types. When you deploy the upgraded cartridge to a run-time environment, the Entity Link drop down type correctly displays the drop down name and list of values.

Known Problems in Release 7.2.2

Design Studio for Inventory 3-3

Design Studio prevents you from using white spaces in configuration item names when using the Refactoring menu Rename option to rename configuration items.

To work around this issue, delete the original configuration item and create a new configuration item with the modified name.

Deleting Entities Generates ErrorsBugDB number: 14735621

When deleting Design Studio for Inventory entities, Design Studio might generate a ruleset error.

To work around this problem, dismiss the message. There is no functional impact.

Reference to Documentation is IncorrectThe Design Studio for Inventory Help includes references to the Oracle Communications Signal Specifications Reference document. The information in this document is now included in Unified Inventory Management Information Model Reference.

4

Design Studio for Network Integrity 4-1

4Design Studio for Network Integrity

This chapter provides release notes for Oracle Communications Design Studio for Network Integrity.



New Features in Release 7.2.2This section describes the new features for Design Studio for Network Integrity.

■ User Interface Enhancements

■ Specification Enhancements

■ Shared Specifications with Unified Inventory Management

■ Data Modeling Enhancements

■ Characteristics Enhancements

■ Scan Parameter Enhancements

User Interface EnhancementsThe Design Studio for Network Integrity feature UI is enhanced to provide consistency across all Oracle Communications Design Studio features and to facilitate a common experience when modeling data across features.

Specification Enhancements Specification editors now include a data tree and a collection of supporting tabs that you use to review and model specifications.

Additionally, the Specification editor Layouts tab includes additional fields that enable you to configure the presentation of characteristics in the run-time application.

Shared Specifications with Unified Inventory ManagementAll specifications supported by the Design Studio for Network Integrity feature are identical to those from the Design Studio for Inventory feature, providing consistency across Design Studio features and increasing cross-application integration.

You can share, copy, or reference supported specifications between Design Studio for Network Integrity and Design Studio for Inventory cartridge projects.



Data Modeling EnhancementsDesign Studio for Network Integrity now uses the Data Dictionary as a logical repository of data types and structures and the key reference point for consistent modeling of data within the solution design. Data required for Network Integrity cartridge projects are defined in a data schema, and then leveraged as data elements for specifications and scan parameter groups. The data schema may be included in the cartridge project, included in a separate model project, or included in a different Design Studio feature (for example, in an Inventory cartridge project).

Characteristics EnhancementsCharacteristics, which previously had been independent entities, are now data elements that can be shared with other applications in Design Studio. All data elements are created in and saved to a data schema. Data schemas enable you to leverage common data elements across Oracle Communications application cartridge projects.

Characteristics that you define for specifications can now exist in a different project in the workspace, which enables you to leverage common definitions and share that data across a solution.

Scan Parameter EnhancementsDesign Studio for Network Integrity now uses scan parameter groups to add additional fields to pages in the Network Integrity run-time application. The new Scan Parameter Groups editor enables you to embed hints and configure the presentation of these fields in the run-time application.


■ Cannot Deploy Cartridges to Managed Server in a Clustered Environment

■ Cannot Rename Characteristic from Specification Editor

■ Deleting Entities Generates Errors

■ Goto Reference Not Implemented for Editors

■ Validation Error After Renaming Scan Parameter Group

Cannot Deploy Cartridges to Managed Server in a Clustered EnvironmentBugDB number: 15832820

You get an error when you try to deploy a Network Integrity cartridge in some clustered environments. This issue occurs only in an Active/Active application server cluster environment with certain front-end proxies or load balancers that expect the Cartridge Management Web Service (CMWS) to be available on all running servers in the cluster.

To work around this problem, disable the front-end proxy before deploying cartridges and reenable the front-end proxy after cartridges are successfully deployed.


Design Studio for Network Integrity 4-3

Cannot Rename Characteristic from Specification EditorBugDB number: 15875767

You cannot rename a characteristic from the Specification editor.

To workaround this problem, you can rename characteristics in the Data Schema editor.

Deleting Entities Generates ErrorsBugDB number: 14735621

When deleting Design Studio for Network Integrity entities, Design Studio might generate a ruleset error

To work around this problem, dismiss the message. There is no functional impact.

Goto Reference Not Implemented for EditorsBugDB number: 9546211

If there is an error in one of the editors, you can click the error to automatically open an editor but it may not navigate to the correct tab.

To work around this problem, manually navigate to find the error.

Validation Error After Renaming Scan Parameter GroupBugDB number: 14646072

After renaming a scan parameter group associated with an action, Design Studio generates validation errors.

To work around this problem, clean and build your cartridge project. The errors do not reappear.

5

Design Studio for Order and Service Management 5-1

5Design Studio for Order and ServiceManagement

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

■ Design Studio Cartridge Migration Analysis

■ New Features in Release 7.2.2.1




Design Studio Cartridge Migration AnalysisIf you upgrade to Oracle Communications Order and Service Management (OSM) 7.2.2 from a prior version of OSM and your cartridges were developed with OSM Administrator tool, it is recommended 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 (renamed from Design Studio Cartridge Migration Analysis Guide in Design Studio 3.1.4). This Guide is included with the Design Studio documentation.

New Features in Release 7.2.2.1This section describes the new features for Design Studio for Order and Service Management Release 7.2.2.1.

■ Enhancements for Honoring Order Item Requested Delivery Dates

■ Support for Rule-Based Compensation Strategy

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.2.2 using the XML Import/Export tool without using Design Studio. However, it is recommended to migrate all cartridges to Design Studio, unless they do not need any modification or re-deployment.

New Features in Release 7.2.2


Enhancements for Honoring Order Item Requested Delivery DatesOSM now calculates the start date for orchestration order components based on the requested delivery date of order items processed by the order components in combination with a configurable order component processing duration. OSM ensures that all order items are processed on or before their requested delivery date if there is a sufficient amount of time to fulfill the order items.

This new functionality depends on the following new control data elements:

■ calculatedStartDate: Stores order component calculated start date values.

■ duration: Stores order component duration values used to calculate the order component start date.

You can also model OSM cartridges to use the calculated start date for specific dependent order components by enabling the Order Component Specification Use Calculated Start Date check box. If you leave this checkbox unselected, OSM starts the order component immediately after the blocking order component completes and all dependency wait conditions are resolved.

OSM always uses the calculated start date for initial order components that do not depend on other order components.

See OSM Concepts for more information about how OSM calculates order component start dates. See OSM Installation Guide for more information about upgrading OSM cartridges to take advantage of this new functionality.

Support for Rule-Based Compensation StrategyYou can now set automation task or manual task compensation strategy using an XQuery expression that queries and calculates the value based on order data.

See OSM Concepts for more information.

New Features in Release 7.2.2This section describes the new features for Design Studio for Order and Service Management.

■ Support for Importing High-Complexity Cartridges

■ Design Patterns for OSM

Support for Importing High-Complexity CartridgesThe level of OSM cartridge complexity directly impacts the time it takes to import a cartridge and the amount of memory required for the JVM. Oracle recommends splitting high-complexity cartridges into multiple cartridges and tying them together using the OSM composite cartridge feature to reduce import time and excessively large JVM memory settings.

OSM provides a cartridge complexity analyzer tool to help determine cartridge complexity. Complexity level is measured based on the estimated import time returned by the cartridge complexity analyzer. The levels are:

Note: You must download and install OSM 7.2.2.1 if you are using Oracle Communications Design Studio 7.2.2.1 features.


Design Studio for Order and Service Management 5-3

■ Low: The approximate cartridge import time can range from a few minutes up to four hours. Low level complexity cartridges do not need to be split.

■ Medium: The approximate cartridge import time can range from four hours to eight hours. Medium level complexity cartridges do not need to be split.

■ High: The approximate cartridge import time is over eight hours. High level complexity cartridges should be split.

Design Patterns for OSMDesign Studio now includes design patterns, which are templates (or established patterns) that enable automation of complex, repeatable tasks, and enables team members with varying levels of skill to complete these tasks.

Design Studio for OSM includes the following new design patterns:

■ Create 3-Stage Base Orchestration Cartridge: This design pattern provides step-by-step instructions to help you creates commonly needed three stage orchestration and base process cartridge entities.

■ Create Base Provisioning Cartridge: This design pattern provides step-by-step instructions to help you creates commonly needed base process cartridge entities.

■ Create Fulfillment Function: This design pattern provides step-by-step instructions to help you creates commonly needed fulfillment function entities.

Fixes in Release 7.2.2Table 5–1 lists the Design Studio for OSM fixes and provides a brief description of the resolution in OSM 7.2.2.


■ Manual Steps Required for Upgrading Custom Automation Plug-ins

■ Model Variable Can Be Picked Up From Wrong Cartridge

■ Imported Model File Causes Project Upgrade Error Message

Table 5–1 Design Studio for Order and Service Management Release 7.2.2 Fixes


3-4662809471 13105139 Permission filters cannot use order data for comparisons. Even though the Data option is disabled for filter expressions, the Data radio button is selected when an XPath expression is supplied in the Value text box. However, the filter expression will not function.

13540679 When importing 6.3.x OSM model XML files into Design Studio using the Import OSM Model option, some Manual Tasks (GenericTaskType) are imported as both Manual and Automated Task. This causes “Naming Conflict – Entity Must be Unique ... “ errors.



Manual Steps Required for Upgrading Custom Automation Plug-insBugDB number: 14794365

If you are upgrading a pre-OSM 7.0.3 cartridge with custom automation plug-ins, you must manually add the following elements to each custom automation entry in the cartridgename/customAutomation /customAutomationMap.xml file:

<cartridgeNamespace>Namespace</cartridgeNamespace> <cartridgeVersion>Version</cartridgeVersion>

where

■ cartridgename is the name of the cartridge.

■ customAutomationMap is the name of the customized automationMap.xml file. The contents of this file get included in the auto-generated cartridgename/cartridgeBuild/automation/automationMap.xml when the cartridge is built.

■ Namespace is the namespace of the cartridge. You can enter the specific cartridge namespace or use the @cartridgeNamespace@ variable to enable the plug-in to automatically detect cartridge namespace changes.

■ Version is the version of the cartridge. You can enter the specific cartridge version or use the @cartridgeVersion@ variable to enable the plug-in to automatically detect cartridge version changes.

For more information about custom automations and the automationMap.xml and customized automationMap.xml files, see OSM Developer’s Guide.

Model Variable Can Be Picked Up From Wrong CartridgeBugDB number: 13516353

If you define the same cartridge management variable on both a composite and a component cartridge with different values for each, and deploy them as a single composite cartridge, the variable is derived from the composite cartridge and not the component cartridge. If you then deploy the component cartridge alone, the variables defined on the component cartridge are used instead.

To work around this problem, ensure that variables defined in both component and composite cartridges have the same value.

Imported Model File Causes Project Upgrade Error MessageBugDB number: 13626413

When importing an OSM model XML file, in some cases, a build is triggered before the project is upgraded. This can cause an error message similar to the following in the problem marker:

Project Upgrade Error - element_name requires an upgrade before it can be used with this version of Design Studio. Please switch to the Studio Design Perspective and restart the application.

On closing Design Studio, the cartridge may not be closed properly. On restarting Design Studio, the error message no longer appears.

There is no workaround for this issue.