Skip to main content
Version: 18

Step-by-step guide to a new set-up

This page will guide you through the set-up of a new organization. It will give you insight in the priorities and will link you to specific config pages to help you configure the environment. Because of the high configurability, no one set-up is equal to the other. Be aware that there is no right or wrong way to go about it. This guide is meant to provide high-level guidelines, but is not considered a hard truth.

General tips​

  1. When setting up a new organization, we always suggest you start by defining a visual work flow, e.g. swimming lane flowchart. This helps to convey how you understand the customer's requirements visually and makes it easier for the customer to provide feedback. This also raises questions for you, as you're creating the flowchart.
  2. Define clearly with the customer and project manager which elements are critical to the delivery and which are not. This avoids losing time on unnecessary discussions and/or config.
  3. Be aware of the elements that require a custom code change and are thus not configurable. You can find more information on the Interfaces page.

The environment​

Deduce whether the customer requires a new organization, new white label and how many FSP's.

  • Should I create a new organization?
  • Does the customer require a new white label?
    • gather specific branding requirements
    • request the uri to the DevOps team.
  • Does the customer require one or multiple FSP's? (Less blocking to start configuration)

⚠️ Configuration should only be initiated in the correct organization, so the above needs to be clarified from the start.

More on configuring the organization here. More on configuring the white label here.

Libraries​

The way the Harmoney configuration is built, you can start by configuring multiple elements under Libraries without this impacting the environment. There are several elements that probably require configuration, obviously depending on the requirements from the customer.

  1. Status transitions Based on your workflow, configure the dossier status transitions.

  2. Form definitions Does your customer require a form aka questionnaire? Who is the counterparty? Internal or external? Make sure it's clear what questions the customer wants to ask and to which parties, as this will need to be specified. Within Harmoney we support re-usability of data. This means data will be stored on a specific party or dossier. Therefore, it is important this is properly defined. Keep in mind in which cases you want the information to be reused or not reused. For example:

  • Do you need the identity information from the counterparty, who can be any individual in the company, or do you need this information from the UBO only? Or maybe you don't need it at all?
  • You want to ask questions on DOSSIER level if, for example, you want the customer to answer these questions differently depending on the contract type.

More on configuring form definitions here. More on configuring dossier information exchanges for internal counterparties here.

  1. Flow definitions The flow definition covers all elements of the flow aka information exchange, meaning more than only questions, which is covered in the form definition. Make sure it's clear what information the customer wants to gather in the flow and from which parties.

More on configuring flow definitions here.

  1. Dossier definitions Dossier definitions are reflected in the UI as a specific dossier type and service that can be selected by the user. Every party type that can be used for the client of a dossier requires a different dossier definition.

Link the respective state diagram, flow definition, form definition and flow options.

More on configuring dossier definitions here. More on configuring flow options here.

Optionally, task list definitions are also linked here. More on configuring task lists here.

FSP definition​

Add your dossier definition to the FSP definition in the Dossier Configurations tab.

No FSP definition exists without modules. Make sure you have a visual on the required modules. More on the FSP modules here.

Once you have a visual on the necessary modules, you'll have more visibility on the required providers.

Providers​

  • Does your customer require the RBA and DUE DILIGENCE module?
    • We recommend documenting the risk model requirements to avoid confusion in the future (once the risk model is in production).
    • More on configuring RBA module settings here.
    • More on due diligence providers here.
  • Does your customer require external (identity, party, document,...) providers?
    • More on providers here.
  • Most likely, your customer will require a custom field definition.
    • Make sure you have a visual on the field definition requirements and provide those using the template via our service desk.

Actions & Validations​

The actions and validations you've defined during the workflow requirements need to be configured.

  • Actions need to be configured on FSP definition level under Dossier lifecycle. More on actions here.
  • Validations can be configured in several places. If applicable, we suggest adding them in the dossier status diagram to enable an easy overview of the customer workflow. If you need a validation in the flow, it should be configured in the flow definition. More on validations here.

Enabling the configuration​

To finally assess the configuration, an FSP with linked FSP definition is required. Create your FSP('s) and link the definition. Add yourself as a user on the FSP to access it.

Final touch​

White label settings​

A final touch to your environment can be provided by adjusting the white label settings. More on white label config here.

Gateway user​

A gateway user needs to be created on FSP level. Be aware that actions triggered by the gateway need to be configured separately using e.g. ENUM GATEWAY_DOSSIER_CREATED vs UI_DOSSIER_CREATED.