1. Use a Clear Title Keep it short but specific.<ul class="accent-bullets"><li>Bad: Form Builder Performance Improvement Request</li><li>Good: Form Builder – Form needs multiple saves before submitting</li></ul><hr>2. Fill Out These Three Sections<ul class="accent-bullets"><li>What is the problem or request?<blockquote>Example: When I add data into the Dynamic Table, I have to save multiple times before it sticks.</blockquote></li><li>Why does it matter?<blockquote>Example: This slows down form completion and causes mistakes if someone forgets to save twice.</blockquote></li><li>What do you expect instead?<blockquote>Example: Saving once should capture all the table data.</blockquote></li></ul><hr>3. Add Supporting Evidence<ul class="accent-bullets"><li>Screenshots: Take a screenshot and highlight the issue.</li><li>Short video (30s max): Record your screen while reproducing the bug or showing the workflow step.</li><li>Links: Add any relevant dashboard, doc, or workflow link.</li></ul><hr><h3>🟥 Example: Bad Practice </h3><pre class="relative language-plaintext" onmouseenter="initCodeBlockCopy()"><button class="absolute right-2 top-2 flex cursor-pointer items-center gap-1 rounded-lg bg-white px-1.5 py-1.5 text-xs font-medium text-gray-700 shadow-sm dark:bg-gray-800 dark:text-gray-200" onclick="copyCodeBlock(this)"><svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-copy-icon lucide-copy h-3.5 w-3.5 transition-transform duration-200 ease-in-out hover:scale-110"><rect width="14" height="14" x="8" y="8" rx="2" ry="2"></rect><path d="M4 16c-1.1 0-2-.9-2-2V4c0-1.1.9-2 2-2h10c1.1 0 2 .9 2 2"></path></svg></button><code class="language-plaintext relative">Form Builder Performance Enhancement
- Forms requiring multiple saves before submission
- Dynamic Table (Search from dropdown functionality)</code></pre>Too vague, missing why it matters, no screenshot or video.<hr><h3>Example: Good Practice </h3>Title: Form Builder – Multiple saves needed for Dynamic TableProblem or Request: I need to save 2–3 times before the Dynamic Table data is captured.Why it Matters: This slows down my work and risks losing data if I forget to save multiple times.What I Expect: One save should capture all the data.Evidence:<ul class="accent-bullets"><li>Screenshot attached: dynamic-table-save.png</li><li>Quick video: loom.com/share/12345</li></ul><hr><h3>Key Notes</h3><ul class="accent-bullets"><li>Always attach at least one screenshot or video — words alone are not enough.</li><li>Be clear about the impact on your work (time wasted, errors, blockers).</li><li>Use plain language. No need for technical details like “steps to reproduce” unless you know them.</li></ul>

Contact Us

How to Submit a Feedback (Bug, Feature, or Enhancement)

Invoice Data Extraction

Proforma Invoice Association

Outlook → Salesforce Email & Note Capture Workflow

Use Cases & Solutions

Form Studio

Getting Started

Task List Panel

Assigning Tasks 

All Tasks in One Dynamic, Smart Table

Approve / Reject Tasks

Human-in-the-Loop

Layout Components

Button Components

Input Components

Select Components

Data Table Component

Build Any UI

Triggers 101

Manual Trigger

Scheduled Trigger

Triggers

Google Sheets Writer

PDF OCR Reader

Web Search

Nodes

Step Output

Data

Chat

Info Access

Chat best practices 

Mergepoint Chat

Creating Knowledge

Collections Management

Data Sources & Sync

AI Optimization

Enrichment Tool

Advanced Features

Mergebase

Roles & Permissions

Administration

Docs

Mergepoint