Skip Headers
Oracle® Communications Order and Service Management Concepts
Release 7.2.2

E35415-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

8 About OSM Roles

This chapter describes how to model roles in Oracle Communications Order and Service Management (OSM).

Note:

Roles are also known as workgroups in the OSM Web clients and in the OSM Administrator application.

See OSM Administrator Application User's Guide for information about assigning users to workgroups.

About Roles

You create roles to define who can perform OSM order management functions. To use roles, you do the following:

  1. Create roles in Oracle Communications Design Studio. When you create roles, you define permissions; for example, you can specify who can display reports in the Task Web client or who can change the priority of a task during order processing.

  2. Assign users to workgroups by using the Administrator application.

  3. Assign tasks to workgroups by using the Task Web client.

For example, you might create roles based on what a user can do in the Task Web client. You can assign the same tasks to multiple workgroups, but users in each workgroup can work with it differently; for example, you might have a workgroup specifically for fallout management.

Roles are also used by the automation framework. For example, automations use OSM roles to restrict who can receive a notification. If a notification is sent to an external system by using an automation plug-in, ensure that you include the role whose credentials are used when running the automation plug-in.

Figure 8-1 shows a role defined in Design Studio. In this example, members of workgroups assigned to this role can generate online reports, search for orders, and access the Task Web client Worklist display.

Figure 8-1 Role Defined in Design Studio

Shows a role defined in Design Studio.

Roles are defined globally in OSM. Using the example shown above, any user assigned to the OrderDisplay workgroup can generate reports. You can also assign permissions to specific order types and tasks. For example, you can specify which roles can create each type of order. This gives you more control over how orders are processed; for example, a fallout role can be allowed to create only fallout-related orders.

Table 8-1 shows the functions that can be assigned to roles in Design Studio.

Table 8-1 Functions Assigned to Roles

Function Description

Create Versioned Orders

Enables users to create orders for different versions of cartridges. If not granted this permission, users can create orders only for the default version of the cartridge.

Exception Processing

Enables users to alter the flow of a process by applying exception statuses at any time throughout the process.

Online Reports

Enables users to view summarized reports on all orders and tasks on the system.

Order Priority Modification

Enables users to modify the priority of a task in an order.

Reference Number Modification

Enables users to modify the reference number of an order.

Search View

Enables users to access the order Query function. See "Specifying Which Data to Display in the OSM Web Clients" for more information.

Task Assignment

Enables users to assign tasks to others.

Worklist Viewer

Enables users to display the worklist in the Task Web client.


About Modeling Permissions in Design Studio

Roles are used in the following OSM entities:

When you model orders, you can specify the orders that roles can display in the Web clients and the data in the order that can be displayed. See "About Setting Permissions for Orders" for more information.

Figure 8-2 shows roles defined in an order specification. In this example, members of BillingUpdateRole are allowed to display orders for customers in the 408 and 510 area codes.

Figure 8-2 Roles Defined in an Order Specification

Shows roles defined in an order specification.

When you model tasks, you can specify which roles can perform which task execution modes (Do, Redo, and Undo). See "About Task Execution Modes" for more information.

Figure 8-3 shows roles used in a task specification.

Figure 8-3 Task Permissions

Shows roles used in a task specification.

When modeling order components and order item specifications, you can define permissions to allow specific roles access to order component search queries and order item search queries in the Order Management Web client. You can also define the data set that their queries return.

Figure 8-4 shows roles used in an order component. In this example, members of ProvisionRole can perform queries based on ProvisioningFunctionTask and display the data in both the summary and detail views in the Order Management Web client. The method for applying roles in an order item specification is identical.

Figure 8-4 Roles Used in an Order Component Specification

Shows roles used in an order component