6 Design Studio for Order and Service Management
This chapter provides release notes for Design Studio for Order and Service Management (OSM).
Known Problems
This section describes existing software problems and any workarounds recommended to avoid the problems or reduce effects:
-
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
-
Behavior Defined for Node Should Not be Editable in Task Editor Composite Data
Order Template Doesn't Inherit "Do Not Rollback" Setting
BugDB: 22203278
Problem: When you set Do not rollback during undo in a component's order template, the main order template does not inherit the setting.
Workaround: Manually set the value for Do not rollback during undo in 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:
-
In Design Studio, select Preferences from the Window menu.
-
In the Preferences navigation tree, select Ant.
-
In the Separate JRE timeout (ms) field, enter 40000.
-
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.
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.