| Previous | Next |  | Contents | Index | Glossary

## Workflow Monitor Access

You can control a user's access to the Workflow Monitor in one of two ways. You can either depend on the workflow-enabled application to control access to the Workflow Monitor or provide direct access to the Find Processes web page.

#### Application-controlled Access to the Workflow Monitor

Identify within the logic of your application code, the workflow process instance(s) that a user is allowed to view, and whether to run the monitor in 'ADMIN' or 'USER' mode for that user. You must also provide a means in your application's user interface to call a web browser application that supports Java 1.1.4 and AWT and pass it the Workflow Monitor URL that gets returned from the function WF_MONITOR.GetDiagramURL( ). The returned URL will have a hidden password attached that provides the user access to the Workflow Monitor in either 'ADMIN' or 'USER' mode. See: GetDiagramUrl.

#### Provide Access to the Find Processes Web Page

Another way to access the Workflow Monitor is to pass the Find Processes URL to a web browser that supports Java 1.1.4 and AWT. The Find Processes page requires user authentication before access. Depending on whether Oracle Workflow is configured to use Oracle Self-Service Web Applications or Oracle Internet Application Server security, the user must log in using the appropriate username and password if he or she has not done so for the current browser session. If the user has workflow administrator privileges, the Find Processes web page that appears lets the user search for any workflow process instance. If the user does not have workflow administrator privileges, the Find Processes web page lets the user search for only processes that the user owns, as set by a call to the Workflow Engine SetProcessOwner API. The user can then display the notifications or the process diagram for any of those process instances in the Workflow Monitor. See: Using the Find Processes Web Page.

The Find Processes URL looks similar to the following:

    <webagent>/wf_monitor.find_instance

`<webagent>` is the web agent string that you can retrieve from the WF_WEB_AGENT token in the WF_RESOURCES table by calling WF_CORE.TRANSLATE( ). See: TRANSLATE.

> Note: You can also access the Find Processes web page from the Oracle Workflow home page. See: Accessing the Oracle Workflow Home Page.

#### Access to the Workflow Monitor from Oracle Applications

For Oracle Applications only, you can add access to the Workflow Monitor to your application by using the Oracle Applications function FND_FNDWFIAS. This function calls the web page wf_monitor.show.

You can add this function to the Navigate menu of a user's responsibility or call the function from an Oracle Applications form. See: Menus Window, Oracle Applications Developer's Guide and Overview of Form Development Steps, Oracle Applications Developer's Guide.

If you call FND_FNDWFIAS without passing any parameters in the call, then wf_monitor.show displays the Find Processes web page.

If you want to specify a process instance to display, you must pass the function the following parameters:

- `ITEM_TYPE`--A valid item type.

- `ITEM_KEY`--A string derived from the application object's primary key. The string uniquely identifies the item within an item type. The item type and key together identify the process.

- `ADMIN_MODE`--`YES` to run the monitor in 'ADMIN' mode, or `NO` to run the monitor in 'USER' mode.

- `ACCESS_KEY`--The access key password to run the monitor in the selected mode. Use the Workflow Monitor API GetAccessKey() to retrieve the appropriate access key. See: GetAccessKey.

When you pass these parameters, wf_monitor.show displays the Workflow Monitor Notifications List web page for the specified process instance.

You can call the function FND_FUNCTION.EXECUTE to execute FND_FNDWFIAS specifying your parameters. See: FND_FUNCTION.EXECUTE, Oracle Applications Developer's Guide. Use the following syntax:

    fnd_function.execute(

      FUNCTION_NAME=>'FND_FNDWFIAS',

      OTHER_PARAMS=>'ITEM_TYPE='||<item_type>||

      ' ITEM_KEY='||<item_key>||' ADMIN_MODE='||<admin_mode>||

      ' ACCESS_KEY='||(wf_monitor.GetAccessKey('<item_type>',

      '<item_key>', '<admin_mode>' )));

The function FND_FNDWFIAS uses Oracle Applications function security to control user access. See: Overview of Function Security, Oracle Applications System Administrator's Guide and Overview of Menus and Function Security, Oracle Applications Developer's Guide.

> Note: In Oracle Applications, you can also call the function FND_UTILITIES.OPEN_URL to open a web browser and have it connect to a specified URL, such as the Find Processes URL or a Workflow Monitor diagram URL. However, this function does not use Oracle Applications function security. See: FND_UTILITIES:Utility Routine, Oracle Applications Developer's Guide.

| Previous | Next |  | Contents | Index | Glossary