Previous Next JavaScript must be enabled to correctly display this content

## 8 Workflow Setup

This topic describes the workflow setup for Oracle Banking Virtual Account Management Installation.

Conductor and Plato-Orchestrator Setup

For conductor and plato-orch-service setup, refer to the Setup Conductor & Plato-Orchestrator section in Oracle Banking Microservices Platform Foundation Installation Guide.

Configuring Account Closure Workflows

The account closure workflows require manual configuration, which is a one-time activity. Two factory-shipped workflows are available for account closure: VirtualAccountClosure and VirtualAccountClosureSWF. These workflows must be created using the Tasks > Business Process Maintenance menu. For more information, refer to the OBMA Guide.

Workflow Overview

VirtualAccountClosure: :VirtualAccountclosure mainworkflow.JSON

This primary workflow is triggered upon batch execution. Each instance of this workflow is assigned a unique workflow ID, allowing for tracking and monitoring.

VirtualAccountClosureSWF:VirtualAccountClosure Subworkflow.JSON

This sub-workflow is initiated by the main workflow and primarily contains tasks related to internal and external integrations. Review this workflow according to available integrations, as it is also assigned a unique workflow ID for tracking purposes.

Key Points

- Manual configuration of workflows is required.
- Two factory-shipped workflows are:
  - VirtualAccountClosure
  - VirtualAccountClosureSWF
- Workflows can be created using the Tasks > Business Process Maintenance menu.
- Unique workflow IDs are assigned to each instance for tracking and monitoring.
- Review and configure the VirtualAccountClosureSWF sub-workflow according to available integrations.

Configuring Batch Jobs

Executing and Scheduling Jobs with Plato-Batch-Server

All jobs utilize the plato-batch-server for execution. Detailed guide can be accessed from Oracle Banking Microservices Platform Foundation Installation Guide. Pre-shipped jobs can be accessed and triggered on-demand through the Task Management > Trigger Tasks screen. However, certain jobs require scheduling from the Task Management > Configure Tasks screen. However, some jobs must be scheduled from the Task Management > Configure Tasks screen.

Follow the provided instructions to schedule jobs and ensure timely execution.

Configuration Requirements

1. CRON Expression: Users must configure the CRON expression, which determines the frequency of job execution. For example, 0 */10 * * * * indicates that the job will run every 10 minutes, every day.
2. Task Trigger Name: The task trigger name defaults as soon the Task Name is selected. However, it is recommended to assign a descriptive name, especially when providing extra trigger parameters for specific branches.
3. Additional Trigger Parameters: To enable branch-specific account closure, extra parameters must be provided in the Additional Trigger Parameters field. The supported format is key:::value. For instance, branchCode:::000;userId:::ADMINUSER1.
4. Priority of Parameters: The branchCode and userId in the Additional Trigger Parameters take precedence over default values.
   - Default Values: If branchCode and userId are not supplied in the Additional Trigger Parameters, default values from the PROPERTIES are used. Ensure that the following entries have valid user and branch code values, along with applicable roles to run the job:
     1. APPLICATION = "plato-batch-server", KEY = "batchServer.userId", VALUE = "<user-id>"
     2. APPLICATION = "plato-batch-server", KEY = "batchServer.branchCode", VALUE = "<branch-code>"
5. Saving the Configuration: Save the configuration, and the job will be scheduled according to the provided CRON expression.

Job Details

1. Account Closure

   Task Name : virtualAccountCloseJob

2. Turn Over Balance

   Task Name : turnOverBalanceUpdateJob

3. Value Date Update

   Task Name : valueDateUpdateJob

4. Entity Positions Update

   Task Name : entityPositionsUpdateJob

Note:

Postings on virtual accounts for which closure request is in progress is controlled through a non-mandatory header parameter “allowPosting” in Balance Transfer stage. The values to this can either be

- Y – This indicates transaction postings are allowed.
- N - This indicates transaction postings are not allowed.

Once the latest subworkflow is registered, on triggering the "virtualAccountCloseJob", the workflow ID gets generated and the table VAM_TB_VA_CLOSURE_STATUS will be updated for the picked up virtual accounts (VA's with closure status as 'P') with the value (Y/N) that is defined in the subworkflow.

External Validation

External validation is done using Oracle Banking Payments. This has to be configured using Oracle Banking Routing Hub configuration files that are factory shipped.

EOD Workflow

EOD has two workflows that are factory shipped.

Refer to the EOD Configuration Guide and perform the setup.