Configure Bulk Workflow Types

The bulk process feature allows you to perform operations such as change the start date, change the card, cancel policies, on multiple policies at the same time. Aside from these operations, you can also configure your own type of bulk process.

Default Bulk Workflow Types

The process requires you to select either a default workflow type or configure a custom one. You will then need to export its template in .xlsx format and populate it with the required data, which varies depending on the bulk workflow type. For all bulk workflow types, the system identifies policies by their policy numbers, which is why the policy number appears as the first column in the templates.

FintechOS comes with the following default bulk workflow types:

  • Change Policy Start Date: bulk change the start date of policies in Proposal and Issued statuses, but not InForce. In the template file, you need to specify:
    • policy number: the number of the policy. This column is mandatory.

    • new start date: the new start date in the format YYYY-MM-DD. The date must be greater than the system date. This column is mandatory.

    • effective date: the new effective date in the format YYYY-MM-DD. The date must be greater than the system date. This column is mandatory.

  • Change Card: sets a new card for the policy coverages. This is a value from Product Factory, configured on Offers. This is only for policies that support alterations, thus policies with statuses Issued, InForce, or Proposal. In the template file, you need to specify:

    • policy number: the number of the policy. This column is mandatory.

    • card name: the new card for the policy coverages. This is a value from Product Factory, configured on Offers. This column is mandatory.

    • optional coverages: list of optional coverages, comma separated.

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

  • Cancel Policy: bulk cancel several policies. In the template, you need to specify:

    • policy number: the number of the policy. This field is mandatory.

    • reason type: the reason type for the cancellation. It is mandatory and it is one of the values configured in Cancellation Reason Types.

    • requested end date: the requested end date. The date must in this format: "YYYY-MM-DD". This column is mandatory.

    • payment beneficiary type: The payment beneficiary for the cancellation. This column is mandatory.

    • payment details: the details regarding the payment in the following form: {bankCode, paymentBeneficiary, paymentIBAN}.

    • comments: a section with any additional information regarding the cancellation.

    • resolution reason: the resolution reason for the cancellation. as detailed in the Cancel a Policy page of this guide, the values of the option set are: Product reasons, Other reasons, Company reason, Withdraw. This column is mandatory.

Configure a Bulk Type

  1. In FintechOS Portal, navigate to the main menu and expand Bulk Process.

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

  3. Fill in the fields:

    • Name: add a name for the bulk workflow types.

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

    • 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.

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

    • GenerateErrorFile: if ticked, a file with the status of all records is generated.

    • Partial Import Allowed: tick this option to allow for the process to complete even if not all rows in the template file have been processed, for example if a policy was not found.

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

    • Route For Validations: the name of the route with the logic for validations, part of the above business service component.

    • Route For Template: the name of the route with the logic for template, part of the above business service component.

    • Custom Flow: the custom flow for this workflow type.

    • Async Flow Name: the name of the async flow for this workflow type.

    • Template: the template file to be used for the bulk operation.

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

  5. After configuration, click Save and close.