☰

Populate client custom fields

Jump to Section

In version 1.5.18 a new custom field was introduced at deposit account level which indicates if a current account is marked as being linked with the Currencycloud SWIFT virtual account. If this custom field is set to true then the current account is linked to the SWIFT virtual account.

The Migration processes cover the following actions:

  • Retrieving of all ACTIVE clients with the reference to the Currencycloud SWIFT virtual account (dedicated custom field which stores the Currencycloud sub-account id with value) and with at least one APPROVED, ACTIVE, ACTIVE_IN_ARREARS or DORMANT current account;
  • For each retrieved client all custom fields that store SWIFT virtual account details are checked and if at least one does not have value all of them are patched with the specific values.
    Also for each client a list with one current account per each currency is identified. For all these current accounts the custom field dedicated to the Currencycloud SWIFT virtual account linkage is set to true.

Running the process

  1. Inside the Migration Script folder, open the directory Populate client custom fields.
  2. The Migration Script is dependent on the base Currencycloud connector through the Mambu and Currencycloud configurations.
  3. The main process which should be triggered is Populate client custom fields - Virtual account restructuring [main process].

Note: The input parameter limit from the main process is used when making the API call to Mambu for getting all the clients and is used for retrieving a number of clients equal to the input value of this field. Mambu API for get all clients has a maximum number of clients which it can retrieve, therefore the clients are retrieved in batches of size limit.

Eg.: limit = 100 and call the process.

Running the process for clients which were not updated

  1. Check process Queue - store clients with errors (under Methods folder). In this process are stored the clients which were not updated (if any), due to either a technical error inside the connector, or if any of the Mambu or CCy API calls failed and the error details due to which clients could not be updated.

  2. After checking the error details for each client and after fixing the issues (if any), these clients can be resent to be processed by triggering the process Reprocess clients with errors.