Skip Headers
Oracle® Communications Order and Service Management System Administrator's Guide
Release 7.2.2

E35414-02
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Changing GUI Application Appearance and Functionality

This chapter describes how to change the appearance and functionality of Oracle Communications Order and Service Management (OSM) GUI applications.

About Configuring the User Experience

OSM supports the customization of the information presented to and collected from Web Client users to match a wide variety of user roles and tasks. This makes it easy to customize the user experience for edits and data validation without having to code Java Server Pages (JSPs).

The Web Client user experience can be customized in various ways:

About Behaviors

Behaviors provide the mechanism to exercise greater control over validation and presentation of order data to Task, and Order Management Web Client users. (In earlier versions of OSM, this capability was called the View Framework.) Behaviors are used mainly in the context of manual tasks that you manage with the Task Web Client.

There are nine behavior types that enable you to dynamically control a specific aspect of the order data model. (You can also add new behavior types using Oracle Communications Design Studio). The included behavior types are:

  • Calculation: Computes the value of a field value based on a formula that references order data.

  • Constraint: Specifies a condition that must be met for the data to be considered valid.

  • Data Instance: Declares an instance that can be used by other behaviors.

  • Event: Specifies an action that is performed when data is modified.

  • Information: Specifies the label, hint, and help information for the element instance.

  • Lookup: Specifies a set of dynamically generated choices from which you can select.

  • Read Only: Dynamically determines whether a value can be modified or not.

  • Relevant: Dynamically determines whether data is visible or hidden.

  • Style: Specifies the visual appearance of fields.

Behaviors can be created only for manual tasks. They can be created at the data element level (most general), order level (more specific), or task level (most specific). After the behavior is created in Design Studio, you can model the actions you want it to perform through its properties settings.

See OSM Developer's Guide and Design Studio Modeling OSM Processes Help for more information about behaviors.

You can use Design Studio to define additional behaviors.