This chapter provides release notes for Oracle Communications Design Studio Platform.
This section includes information about new features introduced in release 7.4.1:
Note:
The Design Studio Online Help was not updated for the features delivered in this release.Design Studio 7.4.1 is compatible with Oracle Enterprise for Eclipse version 12.2.1.9 (or later), based on Eclipse Photon 4.8.0. Design Studio leverages the new features and capabilities of Eclipse version 4.8.0 to provide a better environment for solution designers and software developers.
Design Studio (7.4 and later) no longer supports Automation Builds for Solaris environment because, Eclipse Oxygen 4.7.0 (and later) no longer provides Solaris SDK files.
Design Studio 7.4.1 enhances the import of conceptual model entities from external catalogs. These enhancements allow the conceptual model changes to synchronize directly with Design Studio, thus reducing the occurrence of any misalignments, while renaming or deleting the existing entities, or elements.
The enhancements in Partial import are:
Renames the existing entities or elements if their names are changed and the IDs are not changed, in the input file
Renames the manually created entities if new names are provided in the input file and the IDs in input file are same as the IDs in .studioModel exchange format export file
The enhancements in Complete import are:
Renames the existing entities or elements if their names are changed and the IDs are not changed, in the input file
Renames the manually created entities if new names are provided in the input file and the IDs in input file are same as the IDs in .studioModel exchange format export file
Deletes the existing elements that are created manually or through import, if their information is missing in the input file
Deletes the existing entity references (such as components to CFS/RFS/Resource, other reference relations to CFS/RFS/Resource) that are created manually or through import, if their information is missing in the input file
This enhancement improves the presentation and overall functionality of design patterns used for developing conceptual models for Service and Network Orchestration (SNO) solutions, enabling you to create complete conceptual models more quickly.
Beginning with 7.4.1, these design patterns are packaged with Design Studio. The revised packaging simplifies the configuration of Design Studio for developing SNO solutions, and ensures consistency of the environment.
Design Studio 7.4.1 installation no longer includes default Unified Inventory Management (UIM) and Network Integrity (NI) SDKs. You can install and configure the latest UIM and NI SDKs separately from the respective application packages. This enables you to add the versions of UIM and NI SDKs that are appropriate to your Design Studio environment and identify the corresponding application versions while building the cartridges.
Using action parameter bindings within a conceptual model, you can now configure technical action parameters with attributes from a current, or before, service configuration in addition to a planned, or after, service configuration.
The ability to provide current configuration values enables technical action signatures to contain both before and after information, allowing downstream systems to directly deal with the change in parameter values, or to support a rollback operation to the original values if required.
Table 1-1 lists the Design Studio Platform release 7.4.1 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 |
29244543 |
While referencing a data dictionary root element as child parameter under a structured parameter, sometimes the values of multiplicity in the child parameter are not inherited from the root element. This was fixed by modifying the logic to consider the inherited multiplicity values of child parameter from its parent data element. |
This section describes existing software and documentation problems and any workarounds recommended to avoid the problems or reduce effects:
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.
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.
BugDB: 28648349
Problem: Clicking (?) from the Import XF wizard does not display the Help page.
BugDB: 29917205
Problem: Technical Action Generation design pattern may not work in end to end scenario because of naming and action codes discrepancies.
Workaround: Name of the Technical action can be changed in the design pattern by giving an appropriate name. The Specialized action codes that are not needed can be removed from the Action Codes tab and mapping can be done for the elements in the technical action Data Map for the Specialized Action codes.