Questionnaire Configuration
A step-by-step guide to building, customizing, and publishing questionnaire forms on the AdvanGuard platform — for Mode 1 (API Form) and Mode 2 (Form Link) KYB Application submissions.
Questionnaire configuration is done entirely in the AdvanGuard Dashboard: Configuration → Questionnaire. No API calls are required to set up the questionnaire template itself — only to interact with it once published.
Questionnaire Capabilities
The AdvanGuard Questionnaire builder supports a rich set of question types and form behaviors:
15+ Question Types
Text, number, date, advanced dropdowns (single/multi-select), country selector, file upload, compliance consent checkboxes, international phone, email, and structured address fields.
Conditional Branch Logic
Show or hide specific question cards or entire sections dynamically based on a respondent's previous answers.
Repeatable Sections
Allow applicants to add multiple Directors, Shareholders, or UBOs within a single form by clicking "+ Add" to loop through the section.
Static Embeddable Link
A permanent dedicated URL is auto-generated on publish. Embed it in your website or send directly to merchants — no API integration needed.
Navigate to Questionnaire List
In the AdvanGuard Dashboard, go to Configuration → Questionnaire. The list shows all previously created questionnaires including their name, Questionnaire ID, and publish status.
Click "+ Create"
Click the + Create button in the top-right corner to enter the questionnaire configuration flow.
The first step configures the questionnaire's metadata, front-end display style, and permission controls. The preview panel on the right refreshes in real time as you make changes.
Internal Identifiers
| Field | Required | Description |
|---|---|---|
Questionnaire Name | Required | Internal identifier (e.g. APAC Merchant Standard KYC Form) |
Description | Optional | Internal notes on the questionnaire's compliance purpose |
Form Display Controls
Toggle the following display elements on or off via the Form Display section:
| Toggle | Effect |
|---|---|
| Title | Show or hide the main form title (e.g. "Enterprise Account Application") visible to end users |
| Subtitle | Show or hide the form subtitle |
| Brand Logo | Show or hide your company logo at the top of the form |
Permissions In Development
| Permission | Description |
|---|---|
| Allow editing form | Controls whether the customer can modify submitted form data in the AdvanGuard Dashboard after submission |
| Allow enabling Create Questionnaire entry | Whether customers can manually create and submit a questionnaire entry directly from the AdvanGuard platform |
The structure editor shows the drag-and-configure panel on the left, with a live end-user H5/Web preview on the right.
The platform pre-configures two questionnaire sets: Company Details (enterprise questionnaire) and Associated Profiles (questionnaire for related profiles). You can use these out of the box without any input.
Adding Custom Sections
Add a Custom Section
Click "+ Add Custom Section" to define a new compliance chapter (e.g. Enterprise Information, Shareholder Information, Director Information).
In Section Settings, configure the section's title, description, and display settings.
Set Conditional Display Logic
Click the edit icon next to any question card or section's Display Condition to configure trigger rules. For example:
Add Questions
Scroll to the Questions section and choose one of two options:
| Option | Description |
|---|---|
| Create Custom Question | Creates a question with no system-defined logic or field mapping. Used purely for custom data collection. |
| Add Question from Dictionary | Imports a pre-built dictionary item. Its underlying field parameters (API key, validation rules) are preset and auto-synced. |
Configure Each Question
For custom questions, configure: Title, Description, Placeholder, and toggle Required. For question types like Single Selection, you can edit each specific input item and its key-value pairs.
Referencing Dictionary Items
When adding a question from the dictionary, use the search modal:
| Search Method | Description |
|---|---|
| Keyword search | Enter at least 4 characters in the left input box to trigger fuzzy search by Display Name |
| Type filter | Filter by dictionary type: Address, Attachment, Short Text, etc. |
Before confirming, check these key attributes in the list:
| Attribute | What to verify |
|---|---|
| DisplayName / AliasName | Confirm the customer-facing name and the unique backend alias match what you expect |
| Class | Standard = system built-in high-frequency compliance field; Custom = team-defined field |
| Category | 👤 Individual (person) vs 🏢 Company — ensure the field type matches your section |
After confirming, the dictionary item is automatically converted into a standard question card in the questionnaire. Its underlying rules (character limits, API key values, etc.) stay in real-time sync with the dictionary item.
Save Draft
Click Save at any time to save the current configuration as a draft without affecting any active submissions.
Publish
When ready, click Publish in the top-right corner. After publishing, the system automatically generates a Static Embeddable Link (permanent URL). Copy this URL to deploy in your merchant portal or send directly to target customers — no API integration required.
qnreIdentifierVersion. This value is required for Mode 1 (API Form Submit) API calls.Customize the visual appearance of your questionnaire form to match your brand. Go to Configuration → Customization.
If a theme currently being referenced by a questionnaire is deleted, the associated form will automatically revert to the system default visual template.
Managing Themes
From the Customization list you can:
Enter a theme name (left-prefix fuzzy search)
Clone an existing theme and rename it for further editing
Permanently remove a theme (affects linked questionnaires)
Theme Configuration Tabs
When creating or editing a theme, five configuration tabs are available:
Data Dictionary
The Data Dictionary is the core module for configuring compliance questionnaires and ScoreCards. By abstracting common fields (checkboxes, dropdowns, text inputs, file uploads) into "dictionary items," you maximize field reuse across multiple questionnaires and ensure the backend consistently receives data via standardized API Field Keys or Alias Names.
System Dictionary
System-preset high-frequency compliance fields (e.g. company name, registration number, company email). Available for direct use or as templates for derivation.
Custom Dictionary
Fully custom-built dictionary items created by your team from scratch to meet specific business scenarios.
Managing Dictionary Items
Go to Configuration → Dictionary. The list has two tabs:
| Tab | Contents |
|---|---|
| Active | All dictionaries in Draft, Published, or Published (Modified) states |
| Archived | Deactivated dictionaries only (no Status filter available) |
Search and filter options:
- Enter at least 4 characters of the Display Name for fuzzy search
- Filter by Class (Standard / Custom) and Status (Draft / Published)
Creating Dictionary Items
Click + Create in the Dictionary list. Two creation paths are available:
Path A: From System Dictionary
- Click From System Dictionary in the modal.
- Select a preset standard item (e.g. Company Role Type) and click Confirm — only one item can be selected at a time.
-
The
API Field Keyis inherited and non-editable, but you can freely modify the Display Name, description, and add/remove option values. - The item Class is labeled System.
Path B: Custom Dictionary
- Click Custom Dictionary in the modal to open a blank form.
- Fill in: Display Name → Type (e.g. Short Text, Dropdown) → Category (Individual / Company) → Description → Save.
- Alias Name auto-generates from the Display Name (lowercase, spaces → dots, special chars removed).
- Once first published, the Alias Name is permanently locked and cannot be changed.
For custom Short/Long Text dictionary items, use the Configuration section to set character length limits (min 0 / max 255), input mode (digits only, all uppercase, all lowercase, or mixed), and allowed character sets. A real-time validation test tool is available to verify your rules before publishing.
Questionnaire Group
In AdvanGuard questionnaires, a Group is a structured, reusable container that bundles a set of related questions together. Groups are the fundamental building block for collecting information about multi-entity KYB applications — they allow you to capture data for the subject company, multiple associated individuals, and multiple associated companies in a single questionnaire.
What is a Group?
🗂️ Regular Group
A single, fixed instance of a set of questions. Used for the main subject
company section — the applicant fills it once. Example:
Company Details.
🔁 Repeatable Group
A group that can be added multiple times by the applicant. Used for
associated individuals or companies — the applicant clicks
+ Add to create additional instances. Example:
Director 1, Director 2...
Group Hierarchy
Groups can be nested to mirror a company's real-world structure. The AdvanGuard questionnaire supports up to two levels of nesting:
📋 Questionnaire├── Section 1: Company Details (regular group — filled once) │ ├── Company Name │ ├── Registration Number │ └── Business Address │ └── Section 2: Associated Profiles ├── Individual Profile Group [repeatable]— one instance per person │ ├── Full Name │ ├── Role (Director / Shareholder / UBO) │ └── Passport / ID Upload │ └── Company Profile Group [repeatable]— one instance per related entity ├── Company Name ├── Shareholding % └── Registration Documents
Key Group Properties
| Property | Description | Configuration |
|---|---|---|
| Group Name | Internal label used to identify the group in the Dashboard and in API responses. | Set during group creation. Cannot be changed after publish. |
| Repeatable | Whether the applicant can add multiple instances of this group (e.g. multiple directors). | Toggle in group settings. Default: off (single instance). |
| Min / Max Instances | For repeatable groups — the minimum number of instances required and the maximum allowed. | Only available when Repeatable is enabled. |
| Conditional Display | The entire group can be shown or hidden based on the value of a question in a parent group. | Set via the Display Conditions panel on the group. |
| Group Identifier | A system-generated unique key used in API payloads to reference this group when submitting via Structured Payload (Mode 3). | Auto-generated. Visible in the API Payload Preview in the questionnaire builder. |
Groups in API Submission Modes
The Group concept manifests differently depending on which submission mode you use:
| Submission Mode | How Groups Are Handled |
|---|---|
| Mode 1 — Form API | The server automatically maps flat key-value pairs to their respective groups using the questionnaire template identified by qnreIdentifierVersion. You do not need to manually construct group objects. |
| Mode 2 — Form Link | The end-user sees each group as a visual section or repeatable block in the browser form. Clicking + Add appends a new instance of a repeatable group. |
| Mode 3 — Structured Payload | Groups are represented as nested JSON arrays in the request body. Each repeatable group instance is an element in the array. The Group Identifier is the JSON key used to scope each group's fields. |
Keep each group focused on a single entity type (company, individual, document set). Avoid mixing unrelated questions in the same group — this makes it easier to apply conditional logic and keeps the API payload structure clean and predictable.
Form Structure Reference
The questionnaire form is composed of two core sections:
Section 1: Company Details
Collects core enterprise registration and contact information for the applicant entity.
Section 2: Associated Profiles
Contains two repeatable sub-groups:
| Sub-Group | Description |
|---|---|
| Individual Profile Group | A repeatable section where applicants can click + Add Individual to enter one or more associated natural persons (Directors, Shareholders, Beneficiaries, etc.). |
| Company Profile Group | When a shareholder or parent entity is another legal entity, applicants click + Add Company to drill down and record multi-level associated entities — facilitating corporate structure mapping. |
qnreIdentifierVersion is confirmed,proceed to KYB Application → to integrate the submission API.Updated 1 day ago