Create Group and Group Workflows

How to use this docs page

This page is meant to answer one operational stage of the DullyPDF workflow well enough that you can run a controlled test without guessing. Read the sections below, validate the behavior against one representative document, and only then move to the next linked page.

That order matters because most setup failures come from mixing detection, mapping, fill validation, and sharing into one unstructured pass. A narrower review loop keeps troubleshooting faster and makes the template easier to trust once you save it for reuse.

What a group is

• A group is a named collection of saved templates that belong to one packet or workflow.
• Opening a group loads the alphabetically first template first, then lets you switch between member templates from the header.
• Groups are best for packets that share respondents, schema expectations, or repeat end-to-end processing steps.

Create and open groups

1. Create a group from the upload screen or while organizing saved templates.
2. Add the templates that belong together in one workflow.
3. Open the group to work inside a packet context instead of reopening templates one at a time.
4. Use the header selector to move between member templates while keeping the group context active.

Search and fill full groups

• When a group is open, Search & Fill can apply one selected record across the packet instead of just one template.
• This is the fastest way to populate full document sets that share a respondent or client record.
• Group workflows keep the current template snapshots aligned so you can switch documents without losing the packet context.

Rename and remap entire groups

• `Rename + Map Group` runs batch Rename + Map across every saved template in the open group.
• Use this when a full packet needs standardized field names and schema alignment together.
• The run overwrites each saved template on success, so test the packet once before using it in production.

Packet design rules

• Keep one canonical template per recurring document type instead of several near-duplicates.
• Use a group when the documents truly belong to one packet or respondent journey, not just because they are all PDFs.
• Validate one representative record across the whole packet before publishing a group link or running batch Rename + Map.

Group Fill By Link and packet publishing

• Open a group to publish one merged Fill By Link that asks for every distinct respondent-facing field across the packet.
• Owners can still review stored responses in the workspace and generate the final PDFs only when needed.
• If group membership changes, republish the group link so the public form matches the new packet schema.