For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

16.11.2023

· 5 min read

We have introduced a Webhook step, added detailed step views in Mint Journeys and supported downloading submitted form files.

What's new?
  • Webhook step: Trigger HTTP webhooks with custom JSON payloads.
  • Journey insights: Visual step details for Form, eID and PEP/Sanctions in the manager.
  • Pre-filling: Added Journey ID as a selectable variable for data pre-filling.

Form component

New features

  • Submitted files download. This new feature in Form allows the recipient of a submission to download the files that have been uploaded when a form was completed. They can either be downloaded individually or all at once in one archive.

Improved

  • Allow non pre-selected radio lists. Before this improvement, when a radio list had no specific default value, the first value in the list was selected as default. Now, all items in the list remain unselected until the end-user makes a selection themselves or the creator of the form designates a default selection.
  • Design improvements on disabled inputs. We updated the design for disabled inputs to ensure better readability while making sure it's easy to understand that those inputs can't be edited by the end-user.
  • Extended and added backend validation. To harden and protect data integrity, we added more backend validation for form submissions to the product.

Resolved issues

  • Fixed: Wrong spacing between non-collapsible sections. With this fix, the spacing between non-collapsible sections aligns with the rest of the form designs.
  • Fixed: Text area character count does not update. In the prior release, the character count shown below the text area did not update on typing or pasting text. This is now fixed and updates automatically on new input.
  • Fixed: Using the theming primary colour for submit buttons. With this fix, the submit button for forms uses the primary colour setup in the Dashboard theming and shows it as a background colour.

Mint Journeys

New features

  • Added step details for Form, Identify with eID (formerly Authentication) and PEP/Sanction lookups. We enabled a new way of looking into steps completed and verifying the information received with the step detail pages. Those views not only make it easier to see all the provided input but also highlight important insights, like the certainty and strength of a PEP and Sanction match.

Mint Steps: Connections

New features

  • New step: Webhook. This new step allows you to call a webhook at any point of the workflow. It supports the GET, POST, PUT, PATCH, DELETE methods, as well as sending a JSON payload when triggered.

Mint Steps: Data Verification

Resolved issues

  • Fixed: PEP and Sanction fail with empty list of countries. Before fixing this issue, when setting up a PEP and Sanction step and leaving the list of countries empty, the step would fail. With this fix, an empty list is treated as a valid option and does not limit the countries of the lookup.

Mint API

New features

  • Allowing the execution of internal workflows. This added functionality allows Signicat teams to build workflows on all layers of Mint, even directly in the engine, and execute them properly.

Improved

{/_ vale off _/}

  • Added "stepsDone" and "stepsFaulted" as counter to the execution-log response. To quickly know how many steps in a given journey were completed or have failed, we implemented a counter in the response from the Mint API for the execution-log endpoint. {/_ vale on _/}

Visual Builder

New features

  • Journey ID can be used as pre-filling variable. Using the journey ID as a reference can be useful, especially with the new Webhook step, but also on other occasions like storing the reference in DEM or redirecting to a customer system. This journey ID is now available in the visual builder and can be used in any input that allows data pre-filling.

Improved

  • Disable "Continue on error" for Engine steps. When workflows were supposed to be continued no matter a specific step outcome, the option "Continue on error" could be enabled. This was also possible for Engine native steps, that don't support that kind of behaviour and would ignore it. To improve the UX, this has been disabled for these steps.
  • Improve performance when showing steps. Improving the performance by querying the available steps for the visual builder to avoid lags and longer loading times.

Resolved issues

  • Fixed: Can't select pre-filling value in advanced mode. On some occasions, it was not possible to select any of the suggested values for pre-filling, when the input had advanced mode enabled. After the fix, values can be selected in both modes and appear in the input field accordingly.
  • Fixed: Steps with outcome error should halt the workflow. After this fix, when a step is not set to continue on error, the workflow should fail and halt when the current steps fail. Before this was fixed, the workflow occasionally showed that it was completed successfully.