Document Bundling is a feature which enables you to take documents that have been uploaded or created in the system and bundle them together into a single templated, indexed document.
Bundles are defined by Bundle Templates, which define the overall style of the generated document together with any required sections. Documents can then be dragged into the required section and when you are ready a fully styled, indexed and paginated document can be generated all without leaving the application.
Document Bundling Feature
Access this global feature at Launchpad > Modeller > Global Features. Search for bundling. This global feature sets up the base configuration for document bundling. When the overall feature is enabled, document bundling will be available in the system for users with the required permissions.
The detailed configuration allows defaults to be set for templates (although more templates can be set up for bundles).
| Feature Element | Description |
|---|---|
| Default Output Folder | Indicates where outputs should be placed / will be placed in the current directory. |
| Default Title Page | Allows selection of a template for the title page. Bundle templates can be configured in d > Admin > Documents > Bundle Templates See below for more details |
| Default Section Header | The template that should be used by default for a section header |
| Default Document Separator | The template that should be used by default for a section header |
| Page Text - Header | This allows you to configure the default text that appears in the header, including font and colour. This could, for example, include a page count |
| Page Text - Footer | This allows you to configure the default text that appears in the footer, including font and colour. This could, for example, include a page count |
| Index |
Controls the clickable index and PDF outline in a generated bundle.
Selecting an index entry or an outline bookmark scrolls to the start of the referenced document, including when the Table of Contents spans more than one page. Existing saved settings are preserved on upgrade. The "Experimental features" banner previously shown above these settings has been removed. For more information, see the Document Bundling article. |
Bundle Document Templates
When bundling a set of documents, a template is used to determine the structure and number of sections, etc., in the document. Bundle templates can be configured in Launchpad > Documents Admin > Bundles > Bundle Templates
Data in bundle separator templates
Bundle separator templates, the title page, section headers and document separators, now read their data from Data Composer rather than the legacy bundling tag library. When you author a separator template, the bundle fields are available in the tag browser.
- The bundle name, reference and template name are available on all separator types.
- The current section name is available on section headers.
- The previous and next document names are available on document separators.
- The page range and page count are available on the title page.
Separator templates now resolve matter details, such as the matter title, reference, participants and custom or calculated fields, from the matter itself. Previously these had to be reached through workaround navigation paths. Those paths no longer resolve and return a blank value.
Bundle details, including the bundle name and its sections and documents, are also available in Data Composer on the bundle work item, so you can use them in business rules and phase guards.
A bundle that contains an empty section now generates without error.
Bundle separator templates can be selected in the Word Add-in, with the bundle fields available in the tag browser.
The Document Bundling feature also has a File Naming Rule setting, which controls how the generated file is named. See the File naming rules article.
Legacy bundling tags are retired in release 7.12. Run the Bundle Template Migration job in Modeller Assistant to update existing separator templates. The job scans templates for legacy tag names and context workarounds and can apply the changes in one action. Until a template is migrated, its affected tags will not populate.