Generating Workflow Status for Migrated Transactions

After you complete your data migration, run the Generate Transaction Workflow process to generate or assign the correct workflow status to migrated transactions.

Mapping Legacy Statuses to Licensing and Permitting Statuses

Before running the process, you need to map your legacy transaction statuses to the correct Licensing and Permitting statuses through your Oracle Integration Cloud (OIC) user tasks. For example, you might map your legacy permit statuses as follows:

Legacy Permit Status	OIC Process Definition User Task	Licensing and Permitting Permit Status
Submitted	Accept Application	INS (Inspection)
Plan Review	Complete Plan Review	PLR (Plan review)
In Process	Issue Permit	SUB (Submitted)
Issued Permit (no inspection)	Complete Permit	CMP (Completed) or COO (Certificate of Occupancy)
Issued Permit (inspection required)	Approve Final Inspection	PTI (Permit issued)

You define this mapping by adding the PSC_MIGRATION_TASK as a custom property to your process definition tasks.

Note: For the first process definition task you must assign a value of SUB to the PSC_MIGRATION_TASK.

For more information on process definitions and custom properties, see Setting Up Process Definitions for Workflow and Using Custom Properties.

Running the Generate Transaction Workflow Process

1. Access the process by selecting Common > Generate Transaction Workflow

   You can also access this process from the Process Monitor. See Using the Process Monitor.

2. Select your process parameters on the Parameters tab.

   Page Element	Description
   All Offerings	Select to run the process for all offerings.
   Specify Offerings	Select to run the process only for the offerings you select in the Specify Offerings field. The available offerings include Permits, Planning Applications and Code Enforcement.
   Include Processed Transactions	Turn this switch on to run only the unprocessed transactions for the selected offerings.
   Reprocess Errors	Turn this switch on to reprocess the transactions, which had previously resulted in error, for the selected offerings.

   Note: Before running the process for all records, it's recommended that you test the process with just a few records to make sure that the process definition mapping is set up correctly.

3. On the Schedule tab, select the As soon as possible option to immediately add the process to the queue.

   Select the Using a schedule option to schedule when you want the process to run.

4. (Optional) Turn on the Notify Me When This Process Ends switch to send yourself a notification when the process finishes.

   Click Add on the Notification tab, and enter the recipient and conditions of the notification.

5. Click Submit.

   For Permits and Planning Applications, the Generate Transaction Workflow process instantiates workflow for migrated transactions, and assigns the correct Licensing and Permitting workflow user task to them. For transactions with statuses not mapped in the process definition, the process instantiates workflow and updates the migration status to undefined (U). These will need to be fixed manually by altering the workflow. See Using Workflow.

   For Code Enforcement, the process instantiates workflow for both incidents and cases based on the Process Definition Group assigned at the issue subtype level. The process will advance the workflow as per the current status of the migrated transaction. For example, if an incident is in the Inspection status, then the workflow activates the Inspection stage and the related tasks, if already configured. The process will not activate the Reported stage. Similarly, if a case is in the Citation status, once the process is run, only the Citation stage is activated and not the Violation stage. For more information, see Linking Process Definitions to Issue Subtypes.

   Note: The Generate Transaction Workflow Process instance gets instantiated only when the Enable Workflow switch is turned on in the Code Enforcement Options page. See Setting Up Agency-Level Options for Code Enforcement.