Setting Up Workflow and Decision Applications in OCI Process Automation

This topic describes accessing OCI Process Automation from Oracle Permitting and Licensing and provides a brief overview of the user interface.

Accessing OCI Process Automation

You access OCI Process Automation through Functional Setup Manager.

To access Process Automation:

1. Select the Setup and Maintenance tile from the agency springboard.

2. Make sure Functional Setup Manager is displaying the appropriate setup template for your offering, such as Public Sector Permits.

3. Select the appropriate functional area for your offering.

   Offering	Functional Area
   Permits	Permit Types
   Planning and Zoning	Planning Application Types
   Business Licenses	Business License Types
   Code Enforcement	Incidents and Cases

4. In the task list, select Manage Workflow and Decision Applications in OCI Process Automation.

   This takes you to OCI Process Automation with the Applications node selected, where you can view, create, and modify Process Applications (for workflow) and Decision Applications (for fees).

   Note: The Applications node displays all applications, both workflow and fee applications, or you can select Process to show workflow or Decisions to show fee decision models.

Working with Workflow Applications

When you first access a process application, you'll notice the landing page displays the collection of all the elements that can comprise a process application.

The following table describes the key elements and concepts that make up a workflow application. When you set up a type and you choose the appropriate process definition, you need to specify each of these hierarchical objects.

Object	Description
Application	Applications are functional groups of process definitions containing one or more process definitions. Within an application, you can access a variety of features, including processes (workflow) and decisions (fees). Certain configurations, including integrations and roles, are defined at the application level and shared by all of the application’s process definitions. Therefore, you can simplify the setup process by grouping related process definitions into a single application.
Process Definition	A process definition is a specific workflow process. When different transaction types have the same workflow, they can use the same process definition. See Reviewing a Sample Process Definition to walk through an example of a process definition for workflow.
UIs	UIs are forms or user interfaces that you can include to display at various points in your workflow if user input is required.
Decisions	Decisions are decision models. Typically in Permitting and Licensing you'll use decisions for calculating fees, but they can be included within workflow processes as well.
Version	When you activate a modified application to make it available for use, you choose a version number to assign. New and modified process definitions can’t be associated with a transaction type until you activate a version of the application that includes your changes. For more information on versions, see Preparing the Process Definition for Use.
Connectors	There are a collection of integrations called connectors that enable the process definition to share data with the Permitting and Licensing system.
Roles	Roles map to security roles, or groups, in the Permitting and Licensing system, which you assign to swimlanes in your process models. For instance, only certain tasks would be added to the swimlane for the permit technician role, where as others would be added to the permit supervisor role swimlane.

Another concept to keep in mind when working with process definitions is the version. When you activate a modified application to make it available for use, you choose a version number to assign.

New and modified process definitions can’t be associated with a transaction type until you activate a version of the application that includes your changes.

When a transaction type is assigned a process application version, new transactions are assigned that version of the application for its life cycle.

For more information on versions, see Preparing the Process Definition for Use.

For information on working with workflow for Oracle Permitting and Licensing see Structured Workflow Overview and Dynamic Workflow Overview.

Working with Decision Applications

When working with fee decision models you:

• Define your input data.

• Configure your decisions.

• Activate the model.