Code Enforcement Workflow Basics

Code Enforcement Workflow Overview

Adding workflow to Code Enforcement transactions enables you to automate the progression through the stages and activities and incident or case process flow. Public Sector Compliance and Regulation offerings use the Oracle Integration Cloud (OIC) for designing workflow process definitions and running the workflow engine that drives transaction automation. Before you begin implementing workflow for Code Enforcement, 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.

How Code Enforcement implements workflow is a little different than the way other Oracle Permitting and Licensing offerings do. Permits, Planning and Zoning and Business Licenses use a structured process design, which is suitable for more linear, sequential transaction flows. The Code Enforcement transaction flows can contain stages and activities that don't necessarily occur in a set order, with some may occurring at the same time, while others may not occur at all.

Because of the non-sequential nature of a typical Code Enforcement transaction flow, you will create a dynamic process design. The dynamic process design is a departure from the structured "step 1, step 2, step 3" approach to process design. With a dynamic process definition, you define the stages and activities of the process flow, but you don't define any particular order. You define conditions that drive when or if a particular stage or activity becomes activated, providing the flexibility the Code Enforcement offering requires.

For more information on dynamic 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.

Important OIC Terms

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.

General Topics Related to Workflow

The topics in this chapter are specific to the Code Enforcement workflow implementation. However, the following workflow topics apply to all Oracle Permitting and Licensing offerings. Make sure to be familiar with these topics and complete any setup tasks as needed.