Templates

 A Template is the blueprint for an integration between two systems.

Every Template Interface you use is built from a Template.

At BrynQ we work out how two systems should connect up front, the result is a Template. It defines the structure and rules that make sure data flows correctly from a source system to a target system, before any interface is ever created.

You could think of a Template as the master plan: it's the proven starting point.

What's inside a Template?

A Template bundles everything an integration needs to work correctly, the most important one is;

• Apps : What source and target apps are supported in the intergratino?
  
• Scenarios : the building blocks of a Template. Each scenario covers a specific type of data exchanged between the systems, such as personal details, addresses, contracts, or salary information.
• Logic & mapping : the precise rules inside each scenario for how fields and values are translated from the source system to the target system, so data always arrives in the format the target system expects.
  

Because the structure of the data needs to match the structure of the target payroll system, scenarios are often set up in sections you recognize from the payroll system

Why Templates matter

• A proven standard. Every Template is designed and tested by BrynQ, so each interface built from it follows the same reliable integration standard from day one.
• Predictable behavior. Because the logic and mapping are defined centrally in the Template, interfaces built from it behave consistently.
• Continuously improved. Templates are versioned. When BrynQ improves a Template, a new version is released ; so integrations stay up to date.'
  

Template examples

Templates vs. Template Interfaces

A Template never runs on its own. When you create a new connection in BrynQ, you pick the Template that matches your source and target apps, and a Template Interfaceis created from it — the live version that connects your systems and does the actual work of moving data.

In short: the Template is the blueprint, and the Template Interface is the building constructed from it.

→ Read more in the Template Interfaces article.

Templates are in continuous development, so some details may change over time.