EDI File - Bundle

Specifies the X12 loop identifier that determines what constitutes a single transaction when splitting the EDI file. This value should match the loop code used in your EDI schema (for example, 2300 or 2100).

Usage Guidance

• Enter the loop ID that corresponds to the transaction set you wish to use for splitting.
• The command will extract each matching loop as a separate transaction for bundling.

> Tip: Consult your EDI schema documentation to determine the correct loop ID for your transaction type.

Sets the maximum number of transactions to include in each output EDI file. When the specified number is reached, a new file is created for subsequent transactions.

Usage Guidance

• Enter a positive integer to control the size of each output file.
• For example, setting this value to 10 will create files with up to 10 transactions each.

> Note: The last file may contain fewer transactions if the total is not evenly divisible.

Provides schema-to-content type mappings that enable automatic classification of output documents based on the EDI schema detected in each transaction set. This ensures that each new file or folder is assigned the correct Content Type for downstream extraction and validation.

Usage Guidance

• Add one or more mappings to associate EDI schema names with Grooper Content Types.
• If your input documents are already classified, you may leave this list empty.

Example Scenario

• Map the schema name 837P to a Content Type called "Professional Claim" to ensure correct classification.

> Tip: Proper mapping is essential for automated extraction and validation workflows.

Controls whether the original Batch Folders and their attachments are retained after bundling. When enabled, the command creates new folders for the output files and leaves the original documents intact. When disabled, the original folders are removed and replaced by the new output.

Usage Guidance

• Set to true to keep the original documents for audit or review purposes.
• Set to false to replace the originals with the newly bundled files.

> Note: Preserving existing documents may increase storage requirements.

Can be one of the following values:

Determines the naming convention for the attachments created for each output EDI file. This affects how files are identified and managed in the batch structure.

Options

• Auto: Generates a name based on the envelope date and folder ID.
• ID: Uses the GUID of the host folder as the filename.
• First: Uses the name of the first merged attachment as the filename.

> Tip: Choose a naming method that aligns with your downstream processing or integration requirements.