4.13. Repository node

Icon:

• Number of inputs: 1.

• Number of outputs: 0.

Definition

Sink repository nodes let you create repositories from flows. In other words, they let you create a repository from the result of a flow.

The repository can be re-used in other flows (via the preparation function) to reconcile or enrich data.

Configuration

The configurator of a repository node lets you:

• Specify search fields .

• Specify search groups (= simultaneous search across multiple fields).

• Specify automatic replacement lists (= rewriting of requests) to make repository searches more efficient .

Visual example

See section Tale of Data repositories for details on repositories.

Practical Examples

Note

Example 1: Creating a Simple Repository for Customer Data Reconciliation

Before Operation:

CustomerID	FullName	Address
101	John Doe	123 Elm Street
102	Jane Smith	456 Oak Avenue

Node Configuration:

• Repository Name: “ContactRepo”

• Visibility: Shared within organization

• Search Fields: FullName (Full text enabled, Fuzzy matching enabled, Phonetics set to English)

• Replacement List: No replacements defined

• Deprecation: Not deprecated

After Operation:

A repository named “CustomerDataRepo” is created, allowing other flows to use this repository to reconcile customer names even with slight typos or variations in spelling (e.g., “Jon Doe” would match “John Doe”).

Note

Example 2: Using Search Groups for Complex Reconciliation

Before Operation:

CustomerID	FirstName	LastName	Email
201	Alice	Johnson	alice@example.com
202	Bob	Williams	bob.williams@example.com

Node Configuration:

• Repository Name: “ContactRepo”

• Visibility: Private

• Search Fields: Name, Surname (Phonetics enabled for both)

• Search Groups: “Full Name Group” (combines Name and Surname fields)

• Replacement List: Replace “Bob” with “Robert”

• Deprecation: Not deprecated

After Operation:

A private repository “ContactRepo” is created that allows searching with combined fields, making it possible to reconcile entries where a user’s full name is stored in separate fields. For example, searching “Alice Johnson” would match records even if the full name was split across Name and Surname fields.