Common Functions

Appendix A — Configuration Reference

Common functions are shared SQL function definitions that analysts can reference across transformation logic. Where logic templates capture full transformation patterns, common functions capture the reusable building blocks within them — a date conversion wrapper, a string cleanup function, a lookup pattern that appears in multiple mappings.

Fields

Name — The function name as referenced in transformation logic and available from the notation context menu.

Description — What the function does and what it returns.

Usage Guidance — Optional notes on how to call the function, parameter details, and examples.

Notes

Common functions are documentation, not executable code. Bridger does not parse or validate SQL — the function definitions serve two purposes: they give analysts a consistent vocabulary for referencing shared logic in transformation notes, and they give developers a spec to implement. A conversion architect or team lead can define the function's name, expected behavior, and parameters here; a developer picks that up and implements it as a stored procedure or reusable code snippet. They are also embedded in the AI modelfile so the model is aware of available functions when generating mapping suggestions.

The default logic templates include a Common Routines category whose templates are pre-written to reference the built-in common functions. If you rename or replace those functions, update the corresponding templates to match.