Deactivating and Modifying a Workflow Definition

If required, you can deactivate a workflow definition for one business process without affecting the workflows for other processes you have activated.

For example, if you need to bring your Purchase Order Approval process back into SunSystems while continuing to delegate Financials authorizations to ION Workflow, you can deactivate the Purchase Order Approvals workflow only, leaving the other workflows active. If you do bring an approval process back into SunSystems, you must set up the relevant approval or authorization process within SunSystems.

If you need to modify any of the details of a workflow definition for example, to keep the SunSystems representation of the workflow in step with the definition in ION Workflow when its parameters are being changed you must first stop the workflow from sending and receiving data, by deactivating the workflow definition. A workflow definition can be deactivated only if no outstanding approval requests exist.

Uwaga: Deactivating a workflow in SunSystems causes transactions for that business process not to be sent to ION Workflow. For example, deactivating the Purchase Order Approval workflow causes purchase orders not to be sent to ION Workflow for approval. Therefore, before you change any workflow parameters you should ensure that no users are currently entering transactions in SunSystems for the relevant business process.