5 Design Studio for Order and Service Management

UI Customizability for Automated Tasks to Improve Fallout Management

With this release, automated task definition has been enhanced with the ability to include the specification of behaviors for fallout purposes. You can now define behaviors for automated tasks as well. Behaviors provide a way to extend the functionality and appearance of task data. Each behavior type performs an action; for example, calculating or validating data, or displaying fields in read-only or read-write modes.

When defining behaviors at the task level, you can use the Task editor Task Data tab to create the behavior, the Properties view for the behavior to refine the behavior information, and the Task editor Behaviors tab to view all of the behaviors defined for a task.

To define a behavior at the task level:

1. From the Studio menu, select Show Design Perspective.

2. Use the Studio Projects view.

3. Double-click the automated task entity for which you are defining the behavior.

   Design Studio displays the task in the Automated Task editor.

4. In the Task Data area, select the data node upon which to model the behavior.

5. Right-click in the Behaviors area and select Add Behavior.

6. Select a behavior from the list.

   Note:

   The Calculation, Event, and Lookup behavior types cannot be defined for structured data elements. These behaviors are not relevant because structured data elements do not represent actual data and cannot be acted upon in this way.

   Design Studio adds the behavior to the Behaviors area. Each behavior type enables you to dynamically control a specific aspect of your order data model.

7. In the Behaviors area, click the behavior to open the Properties view.

   The Properties view is displayed with the set of properties that you must define for the corresponding behavior type.

8. Click Save.

The "Do not rollback during undo" Setting is Not Being Contributed

BugDB: 22203278

Problem: 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.

Workaround: Manually set the value of the data element's "Do not rollback during undo" property on 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:

1. In Design Studio, select Preferences from the Window menu.

2. In the Preferences navigation tree, select Ant.

3. In the Separate JRE timeout (ms) field, enter 40000.

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

Getting Project Upgrade Error for Newly Imported CommonDDProject

BugDB: 28706381

Problem: While importing common data dictionary, the Project Upgrade wizard is not loaded. Instead, errors such as "Project Upgrade Error" are received at the end of import.

Workaround: Close the project and reopen it.

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.