Flow Builder and Flow Manager

This guide is written for the people who design, build, and operate flows on the Digital Experience Platform (DXP). The four areas covered are flow building, webhooks, data sources, and the settings that drive how flows behave. A flow is an end to end journey built in the Flow Builder. Each client submission that travels through a flow is called an interaction.

1. Open the DXP URL provided by your administrator.
2. Enter your work email, then press Sign In.
3. Enter your password, then press Login.
4. If two factor authentication is on, enter the 6 digit code from your authenticator app.

You can sign in only with a work email that ends in your tenant domain. Once signed in, the left side menu shows Dashboard, Documents, Flow Builder, Flow Manager, Developers, and Settings. As a flow designer you mostly use Flow Builder, Flow Manager, and Documents.

Every flow is built from three block types. You can chain them as many times as the journey needs.

Each block on hover shows four controls: the red X deletes it, the magnifying glass opens its data viewer, the pencil edits its steps, and the green plus adds the next block.

The canvas draws each block as a distinct shape so you can read the chain at a glance. An Engagement Block renders as a rounded pill, a Connector Block as a diamond, and a Backend Block as a pentagon. The green plus sets each new block's type automatically by sequence: Engagement first, then Connector, then Backend, then Connector, then Backend, alternating. So you click the plus once per block and never pick a type yourself. Double-click any block to open a Block Name input and rename it. Two canvas toggles sit at the top right: Allow Support (on by default), which lets support agents assist during the engagement, and Teller Mode (off by default), covered under Branch Assisted Mode.

Inside an Engagement Block you build a sequence that starts with Block Loader and ends with Wrap Up. The green plus between steps opens the step picker. Every step shares Title, Subtitle, Next Button, Logo, and a Normal Click toggle.

The names below are exactly as they appear in the step picker on the platform.

Every Engagement Block step shares five base controls: Title, Subtitle, Next Button text, a Logo upload, and a Normal Click toggle. The type-specific settings for each step are listed below, using the exact platform names. After you set them, change the defaults to real values so Save turns on.

Informative Onboarding

A multi-page welcome that sets expectations before capture begins.

Service Selection

Lets the client choose a service or path, which a later Split step can branch on.

Identification Document Capture

Captures an ID with AI auto-capture, then reads it with OCR and MRZ. This is the richest capture step, so its full control set is below.

Face Image Acquisition

Captures a selfie with AI face detection and liveness, then enrolls, matches, or authenticates it.

Assisted Data Entry

A form built from sections and fields. Fields pre-fill from the OCR and MRZ of the ID step, so the client mostly confirms rather than types.

The fourteen input types are: Text, Text Area, Date, Drop Down, Email, Radio Button Group, Checkbox, Checkbox Group, Nationality, Phone Number With OTP, Email With OTP, Phone Number, Upload Document, and Informative Display. Choice types (Drop Down, Radio Button Group, Checkbox Group) take an option list; the OTP types verify the email or phone inline; Nationality is a country picker; Informative Display shows read-only text.

Each field has its own settings. Beyond the input type, every field carries the controls below. This is where a form becomes smart: fields pre-fill from earlier steps, validate the entry, and normalize scripts and languages.

Questionnaire

Asks a set of questions to tier KYC or build a risk profile.

Location Selection

Captures and validates an address or location.

Document Capture

Collects one or more supporting documents from the client.

Terms & Conditions

Presents terms the client must accept, including GDPR consent.

Payment Processing

Takes a payment as part of the flow.

Context Aware Signing

Issues a generated document for the client to sign in real time.

Split

Branches the flow based on data captured by earlier steps.

The Connector Block is the platform's data relay. After the client finishes the engagement, it screens and manages the entity, notifies on status change, creates or updates the client record, and pushes data to external systems. Open the connector with its pencil and add steps.

Sample: notify your core system when a client is created

A common pattern in the eKYC sample is to push the new client to your own systems the moment the record is created, so an ERP, a CRM, a core banking, or a core insurance system receives the data in real time. You do this by pairing Create / Update Client with a Webhook in the final Connector Block.

1. In the final Connector Block, add a Create / Update Client step so the client record is written to the Clients section.
2. Add a Webhook step after it. Point it at the Data Source for your core system, or configure it inline.
3. Pick the endpoint (a Push Data Request), set the method and headers, and map the client data points into the body.
4. Press Test on the Data Source endpoint to confirm the call reaches your system, then Save.

In the Backend Block your team reviews collected interaction data and records a decision. Open the Application Command to configure the queue your team works from.

1. Open the Flow Builder.
2. Press the pencil on a Backend Block. The screen shows the steps list on the left, with Application Command by default, and the step palette on the right.
3. Press the pencil on Application Command. The configuration opens with five collapsible sections.

Expand Automated Processing. Below the AML and PEP screening toggles and the Filter by section sits Automated Decisions.

1. Press the plus icon to add a rule.
2. Set the Rule Name, a label for the audit trail.
3. Set the Condition, the data point or screening signal to evaluate.
4. Set the Decision to fire: Approve, Decline, or any custom decision you define, such as one that starts a supporting eKYC flow.
5. Set the Check Value, the value to compare against.
6. Press Save.

The system auto-decides the interaction the moment it arrives if it matches the rule. Operators only see interactions that do not match any auto-decide rule.

Start with a single Engagement Block, then add the client facing steps below in order. Turn Skip Ability on while you test and off in production.

1. Drag an Engagement Block onto the canvas. A new flow is created and named automatically.
2. Click the block's pencil to open its step sequence.
3. Click the green plus above Wrap Up and choose a step type.
4. Fill the step's fields with real values, then press Save.

After the Engagement Block finishes, chain the operations side. A common pattern runs a Customer Service Backend Block first, then a Compliance Backend Block.

1. Add a Connector Block: set Status Change to Submitted, add a Notification email to the applicant, and an optional Webhook into your CRM.
2. Add a Customer Service Backend Block: an Application Command with Automated Decisions for clean cases and a manual queue for the rest.
3. Add a Compliance Backend Block: an Application Command with AML and PEP screening on, and inline review for matches.
4. Add a Final Connector Block: Create or Update Client, send the approval email, and push to the core system over a webhook.

Flow Manager is the publish and distribution surface. The page title is Engagements, Administer Engagement. Tiles on the left show one per flow. The right panel holds the actions for the selected tile.

Define data sources in Settings > Data Source. Cards on the page represent every source. A Data Source is a named connection the Webhook step can call.

1. Press the plus icon and name the source.
2. Pick the type: API or SOAP.
3. If the source needs auth, choose API Key or Basic Auth.
4. Fill in the URL and credentials. Press Test, then Save.
5. Open the source and add endpoints: Pull Data Request, Push Data Request, or JSON File.
6. Add headers, body, and XSLT if you need to transform inbound payloads.

Once a source exists, the Webhook step inside the Connector Block can call any of its endpoints. The Webhook can also be configured inline without going through the data sources screen.

The Document Template Builder is at Side menu > Documents. It turns a Word file into a template the Context Aware Signing step fills and signs.

1. Upload a .docx as a starter template.
2. Right click in the builder to insert flow inputs (text, date, image, signature) as tokens wrapped in double brackets.
3. Map each token in the Context Aware Signing step.

The Email Template Builder is reached from the Notification step in the Connector Block. Build the layout with blocks. Use Merge Tags to pull flow data points into the body. A token is a placeholder inside a document or email template, replaced by a data point at runtime.

The Theme Builder is reachable from the profile menu, top right. It brands the client facing screens.

1. Set the text color.
2. Set the accent color and accent text color.
3. Set the background body color and background card color.
4. Upload the icon and primary logo.
5. Pick the stepper style: None, Webview, or Circular.

Branch Assisted Mode lets an agent, teller, relationship manager, or counter operator run a flow's Engagement Block on behalf of a client, from a branch. The client no longer has to complete it on their own device. You enable it per flow, then optimize how the block looks for the agent.

1. Open the flow and turn on the Teller Mode toggle on the flow canvas.
2. A new layout manager icon now appears on the Engagement Block. Open it to arrange and optimize how the block is presented to the agent for over-the-counter use.
3. Arrange the layout in the layout manager, then save. Publish the flow.
4. Agents run the flow for clients at the counter through the published flow's Digital Engagement Link, https://platform.assentify.com/?interaction=<hex>.

The DXP supports custom roles built from claims dragged into a role definition. The recommended starting roles for this audience are listed below. Your administrator can adjust the claims to match your operating model.