This chapter provides release notes for Oracle Communications Design Studio for Oracle Communications Order and Service Management (OSM) release 7.3.5.
This section includes information about new features introduced in release 7.3.5.
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.
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. |
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
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.
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:
In Design Studio, from the Window menu, select Preferences.
In the Preferences navigation tree, select Ant.
In the Separate JRE timeout (ms) field, enter 40000.
Click OK.
The following feature is removed in release 7.3.5.
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.