6.1 Conductor Processes
In conductor, workflows are defined using a JSON based DSL and includes a set of tasks that are executed as part of the workflows. The tasks are either system tasks or simple tasks (aka worker tasks). These simple/worker tasks are implemented by application(s) and run in a separate environment from Conductor. These tasks communicate with Conductor server via REST client.
In Oracle Banking Supply Chain Finance, for every workflow, a workflow definition JSON will be maintained.
Deploy the following list of conductor processes for Oracle Banking Supply Chain Finance. The deployable units are available in the obscfcm-workflow-management-services folder in the OSDC.
OBSCF_OSDC_{release}\OBSCF_SERVICES\obscfcm-workflow-management-services-{version}.war\WEB-INF\classes\dsl\Note:
For the exact version and release numbers, refer to the OSDC file available as a part of the release.Table 6-1 Conductor Process List
| S. No | Process Name |
|---|---|
| 1 | AMENDMENT_REVERSAL |
| 2 | ANOMALY_DETECTION |
| 3 | DATE_FLIP_WORKFLOW |
| 4 | DISBURSEMENT_INITIATION |
| 5 | DISCOUNTING |
| 6 | FCIMSG |
| 7 | FINANCE |
| 8 | FINANCE_AUTODEBIT |
| 9 | FINANCE_REVERSAL |
| 10 | FinanceDedupCheckWorkflow |
| 11 | FinanceDedupeCancellationWorkflow |
| 12 | INSTRUMENT |
| 13 | INSTRUMENT_AUTODEBIT |
| 14 | MANUALRECON |
| 15 | MGR |
| 16 | OBSCFCM_EOD |
| 17 | REFUND |
Parent topic: Conductor Process Installation