This chapter provides release notes for Oracle Communications Design Studio Platform.
This section includes information about new features introduced in release 7.4:
Note:
The Design Studio Online Help was not updated for the features delivered in this release.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.
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
To import exchange format data from an external catalog:
Open Design Studio.
Ensure all changes made in workspace are saved.
Run a full build to ensure all model files are up-to-date.
Open Studio Projects or Solution view.
Open the Context menu by right-clicking the page.
Select Import > Import Exchange Format.
Click Browse and select the required exchange format file (.xml file).
(Optional) Select Complete for a complete import.
Click Next.
The Summary Page appears.
Check all the entities and elements that are imported and then click Finish.
A dialog box appears to open the generated import log.
Click Yes to open the log file, or click No to go back to the previous view.
Design Studio 7.4 does not support Log4j for modifying log levels. You can now modify them in WebLogic server using WLST commands.
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.
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. |
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.