Configure Bulk Workflow Types

The Bulk Process feature allows you to perform actions on multiple policies simultaneously, such as changing start dates, updating cards, or cancelling policies. In addition to the predefined operations, you can also configure custom bulk workflow types to support specific business processes.

Default Bulk Workflow Types

When running a bulk process, you must select either a default or a custom workflow type. Each workflow type provides an Excel (.xlsx) template that must be downloaded, completed with the required data, and uploaded for processing.

For all bulk workflows, policies are identified by their policy number, which is always the first column in the template.

FintechOS provides the following default bulk workflow types:

Change Policy Start Date

Allows bulk updates of policy start dates for policies in Proposal and Issued status (not applicable to InForce policies). The required template columns are:

  • policy number: unique identifier of the policy (mandatory);

  • new start date: new start date in YYYY-MM-DD format; must be later than the system date (mandatory);

  • effective date: new effective date in YYYY-MM-DD format; must be later than the system date (mandatory);

Change Card

Updates the card associated with policy coverages. This is a value from Product Factory, configured on Offers. This operation applies only to policies that support alterations and are in Proposal, Issued, or InForce status. The required template columns are:

  • policy number: unique identifier of the policy (mandatory);

  • card name: the name of the new card, configured in Product Factory (mandatory);

  • optional coverages: comma-separated list of optional coverages (optional);

  • optional subcoverages: comma-separated list of optional sub-coverages (optional).

Cancel Policy

Cancels multiple policies in a single operation. The required template columns are:

  • policy number: unique identifier of the policy (mandatory);

  • reason type: cancellation reason, as configured in Cancellation Reason Types (mandatory);

  • requested end date: requested cancellation end date in YYYY-MM-DD format (mandatory);

  • payment beneficiary type: beneficiary of the refund payment (mandatory);

  • payment details: payment information in the format {bankCode, paymentBeneficiary, paymentIBAN};

  • comments: additional cancellation details (optional);

  • resolution reason: reason for cancellation resolution; valid values include Product reasons, Other reasons, Company reason, and Withdraw (mandatory) as mentioned in the Cancel a Policy page.

Configure a Custom Bulk Workflow Type

  1. In FintechOS Portal, navigate to the main menu > Contract Management > Contract Management Settings > Insurance Settings > Bulk Processes Types Settings.

  2. Click the Insert button and the Add Bulk Workflow Type form opens.

  3. Fill in the fields:

    • Name: the display name of the bulk workflow type;

    • Solution: the solution where it applies;

    • Unicity Column Names: optional. When filled in, ensures that the data file is validated to prevent duplicate rows based on the specified columns. For example, if I have a template with a header consisting of seven columns, where the first two are "name" and "date," and I set Unicity Column Names to "name,date," the system verifies that the file contains the same header and that no more than one row exists with the same name and date. Essentially, this guarantees that within the excess data, uniqueness is maintained according to the configured pair.

    • Template: Excel template file used for this workflow;

    • Security Roles: select the security roles that have access to performing this bulk operation;

    • Business Service Component: the name of the business service component with the logic of this process;

    • Route For Validations: validation logic route within the service component;

    • Route For Template: template generation logic route within the service component;

    • Custom Flow: optional custom flow associated with this workflow;

    • Async Flow Name: the name of the asynchronous flow used for processing;

    • Active: tick the box to enable this bulk workflow type;

    • Generate Error File: generate a result file showing the status of each processed record;

    • Partial Import Allowed: allow processing to continue even if some rows fail (for example, if a policy is not found).

  4. The Bulk Workflows tab displays the processes with this workflow type.

  5. After configuration, click Save and close.