> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/admin/8.7/mergeform-workflow-application.md).
# MERGEFORM Workflow Application
## Overview
The **MERGEFORM** workflow application takes multiple form data files and merges them into one file. It can also merge form archives into a target form archive by merging the HTML sections from both files.
## How it works
All parameters are optional, and parameter names can be set by the process designer. To copy a data from one to another, the only action required is to set the default value as the data to copy and set the data into which you want to retrieve it. The parameters’ directions must be INOUT. There is no limit to the number of parameters.
## Parameters
### Required parameters
| **Parameter** | **Type** | **Direction** | **Description** |
| -------------------- | -------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `FORM_DATA` | File | INOUT | The merge target `FORM_DATA`. All `FORM_DATA_SOURCE` parameters will merge into this parameter’s default value (IN) and will update the specified data (OUT) with the result. |
| `FORM_DATA_SOURCE1` | File | IN | Specific form data to merge into the target form data. |
| `FORM_FIELDS_MERGE1` | Text | IN | The fields to merge from FORM\_DATA\_SOURCE1 to FORM\_DATA, separated by commas. It supports the asterisk (\*) wildcard character to select all fields starting with the prefix.
✏️ Note: If you don’t specify a FORM\_FIELDS\_MERGE\[N] parameter, all of the fields in FORM\_DATA\_SOURCE\[N] will be merged.
|
### Optional parameters
| **Parameter** | **Type** | **Direction** | **Description** |
| --------------------------- | -------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `FORM_DATA_SOURCE[2..N]` | File | IN | Specific form data to merge into the target form data. |
| `FORM_FIELDS_MERGE[2..N]` | Text | IN | The fields to merge from `FORM_DATA_SOURCE[2..N]` to `FORM_DATA`. It also supports the wildcard character. |
| `FORM_ARCHIVE` | File | INOUT | The merge target `FORM_ARCHIVE`. All `FORM_ARCHIVE_SOURCE` parameters will merge into this parameter’s default value (IN) and will update the specified data (OUT) with the result. |
| `FORM_ARCHIVE_SOURCE[1..N]` | File | IN | Specific form archive to merge into the target form archive. |
| `FORM_FIELDS_ARCHIVE[1..N]` | Text | IN | Section IDs to merge from `FORM_ARCHIVE_SOURCE[1..N]` to `FORM_ARCHIVE`, separated by commas. It does not support the asterisk wildcard parameter; instead, you must specify the exact IDs of each section to merge. |
### Examples of parameters
| **Parameter** | **Type** | **Direction** | **Description** |
| ---------------------- | -------- | ------------- | ------------------------------------------------------------------------------------------------ |
| `FORM_DATA` | File | INOUT | Send value of FORM\_DATA
Receive value of FORM\_DATA
|
| `FORM_DATA_SOURCE1` | File | IN | Send value of `FORM_DATA_VALIDATES_ACCOUNTING` |
| `FORM_FIELDS_MERGE1` | Text | IN | Send value of `ACCOUNT_*` |
| `FORM_DATA_SOURCE2` | File | IN | Send value of `FORM_DATA_VALIDATES_SALES` |
| `FORM_FIELDS_MERGE2` | Text | IN | Send value of `SALES_DECISION,SALES_COMMENT` |
| `FORM_ARCHIVE` | File | INOUT | Send value of FORM\_ARCHIVE
Receive value into FORM\_ARCHIVE
|
| `FORM_ARCHIVE_SOURCE1` | File | IN | Send value of `FORM_DATA_VALIDATES_ACCOUNTING` |
| `FORM_FIELDS_ARCHIVE1` | Text | IN | Send value of `ACCOUNT` |
| `FORM_ARCHIVE_SOURCE2` | File | IN | Send value of `FORM_ARCHIVE_VALIDATES_SALES` |
| `FORM_FIELDS_ARCHIVE2` | File | IN | Send value of `SALES` |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.workflowgen.com/admin/8.7/mergeform-workflow-application.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.