Preparing the Process Definition for Use

This topic describes how to publish and activate the process definition so that it can be referenced and used for intake forms.

Preparing process definitions for use involves:

• Publishing

• Activation

Publishing Process Definitions

While you can save your changes as you make them when updating or creating a process definition, to finalize your changes and begin to prepare the process to be tested and referenced by intake forms, you need to publish the form.

To publish a process definition:

1. Click Publish in the header of the process definition.

2. On the Publish Application dialog box, enter a comment to describe the most recent changes.

3. Click Publish.

Activating Process Definitions

Activating an application makes any new or modified process definitions within that application available to associate with an intake form for a transaction type definition.

For more details on activating applications, also see Activate Applications in the Oracle Integration Cloud documentation.

To activate a process definition:

1. Click Activate in the header of the process definition, and follow the train stops on the Activate Application to My Server dialog box.

2. On the Select Version page, select Last Published Version.

3. On the Customize page, review the base URL and security credentials.

4. On the Validation Result page, review any warnings and make any required changes in the definition, with the ultimate result being application successfully validated.

5. On the Activation Options page, enter a unique value for Version.

   The version value should be incremented with a unique value for each new activated version. For example, begin with 1 or 1.0, for example, then 2 or 2.0 for the next version, and so on.

   Note: Version numbers are a very important element of the activation process. Review the considerations below related to version numbers as you activate and incorporate process definitions into your transactions.

6. Click Activate.

7. Update the associated transaction type definition to reference the new version in the Workflow Setup section of the transaction type definition page, such as the Permit Type page.

When adding version numbers, consider the following items:

• Do not reuse the same version number used on a previous version of the process definition. If you reuse the same version number when you activate the application, all open process instances using that version will be terminated and sent to a status of complete regardless of where they actually are in the workflow. To prevent this, make sure to use a new version number for each newly activated version.

• When you activate and associate a new version number to a transaction type definition, such as a permit, only the transactions submitted after the new version of the workflow process definition has been applied can take advantage of the changes made in the newest version of the process definition. All in-process transactions continue to use the workflow process definition version number in place when those applications were submitted. For example, if you make a change to the role or user ID assigned to a swimlane in version 2 of a process definition, only the intake forms submitted after version 2 has been associated with the transaction type can take advantage of the swimlane assignment change. All intake forms currently being processed continue to use swimlane assignments defined in version 1 of that workflow process definition.

• Do not deactivate a previous version of a process definition because in-process transactions may still be using it.