Workflow Basics

You define your transaction workflow using the Process Builder in Oracle Integration Cloud (OIC). This topic provides a general introduction how OIC is used and some important OIC terms.

Workflow is supported for all Public Sector Compliance and Regulation offerings, but this chapter applies specifically to these offerings:

  • Permits

  • Planning and Zoning

  • Business Licenses

Code Enforcement implements workflow using a different process definition type, which is covered in a separate chapter. See Code Enforcement Workflow Basics for more information on Code Enforcement workflow.

Before you begin implementing workflow it is imperative that you become familiar with the Processes feature in OIC.

For more information on the OIC Processes feature, see Using Processes in Oracle Integration.

For Permits, Planning and Zoning, and Business Licenses, you define structured processes to run your workflow. For more information on structured processes, see Develop Structured Processes.

Note: Oracle provides a Solution Package with sample workflow configurations. It is highly recommended that you clone these samples and use them as starting points to create your own workflow.
Note: Currently, in the context of data object parameters, data association parameters, and REST resource attributes, the terms record, transaction, and permit are interchangeable.

Important OIC Terms

The OIC object where you set up your workflow tasks is called a process definition.

The following table describes the hierarchy of objects for a process definition. When you set up a type and you choose the appropriate process definition, you need to specify each of these hierarchical objects.

Object

Description

Space

Spaces are an organizational tool similar to a folder.

Your agency chooses the spaces that make sense for your organization. For example, you can create separate spaces for different categories of s.

Application

Applications are functional areas within Spaces.

Within an application, you can access a variety of features, including processes (workflow) and integrations.

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.

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.

Process Definition

A process definition is a specific workflow process.

When different 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.