Appendix A: Configuration Reference

Reference documentation for all workbook configuration editors.

The Configuration tab holds everything that defines how a workbook behaves — the status codes that govern mapping progression, the notation types that capture transformation logic, the rules that automate repetitive mapping work, and the templates that drive reports and imports. Changes made here apply across all projects in the workbook.

The first tab in the Configuration editor is General. It has two fields: Template Name and Template Description. These identify the configuration itself — not the workbook, but the configuration package within it. A well-labeled configuration makes it easy for someone inheriting the workbook, or evaluating it as a starting point for a new engagement, to understand what conventions are in place and whether they suit the work at hand. For example: Acme Ltd. Standard Conversion Configuration — established in early 2026 to support all standard conversions, incorporating the transformation standards, notation conventions, and validation practices adopted at that time.

The remaining tabs each correspond to a configuration editor. The tabs appear in the order they are most naturally filled out when building a configuration from scratch:

Start with Special Tables — establishing what to do with unmappable fields is the foundation everything else builds on. Status Codes, Notation Types, and Indicators come next; these three define the vocabulary used to communicate mapping decisions to stakeholders and are fundamental to the whole project. Once those are in place, Logic Templates, Common Functions, Exception Codes, and Auto-Mapping Rules layer on top — they streamline the work and maintain standards, and they draw on what was defined in the earlier editors. Report Templates come last because they can reference everything: statuses, notation types, indicators, source paths, and the full project structure.

• Special Tables — the five built-in table types for exclusions, defaults, and stored values
• Status Codes — mapping lifecycle states, approval locking, and color coding
• Notation Types — the structured text fields attached to mappings, tables, and columns
• Indicators — scoped yes/no or enumerated flags for tables and columns
• Logic Templates — reusable transformation logic snippets
• Common Functions — shared SQL function definitions for use in transformation logic
• Exception Codes — short codes for documenting mapping exceptions
• Auto-Mapping Rules — condition-based rules for automated mapping creation
• Report Templates — sheet-based templates for export, reporting, and spreadsheet import