The treaty held. The documents delivered. Word spread fast. World Industries is going global — same contracts, same agreements, but now across twelve time zones and eight languages at a volume that breaks any manual process. One-off configurations won't cut it anymore.
To scale without breaking, you'll need to master the two pillars of reusable automation:
Your job is to build the infrastructure behind the empire. Pipelines that run without human hands, at any volume, without breaking a sweat. World Industries didn't grow by doing things twice. Neither will you.
Objective: Build reusable templates for both APIs — configure a multi-locale Document Template, then create an Envelope Template and instantiate an envelope from it.
This mission rebuilds the same pipeline as Mission 1: Command and Conquer Your Document Empire — Data Source, Document Solution, Template upload, Data upload — using a German-locale copy of the data file, with the date reformatted so it parses correctly. See Mission 1 for the full explanation of each step; Step 1 below just runs through them quickly.
Before running the steps, take a look at the two raw materials this mission works with:
Customer.EffectiveDate. It's the same contract data as Mission 1, with the date reformatted for German locale parsing.Open the Doctavian Postman collection and navigate to the Mission 3 — Scale the Empire folder. Run the steps in order.
The same four steps from Mission 1 — Command and Conquer Your Document Empire — just moving faster this time.
mission-3-agreement-de.docx filemission-3-data-de.json fileRun all four in order. Each one saves its own ID automatically, scoped to this collection.
Open Step 2 — Generate for a new locale. The request reuses the template and data uploaded in Step 1 — nothing about the pipeline changes — but document.locale and document.timezone are set to de and Europe/Berlin instead of en and Europe/Dublin. Same contract, same numbers, formatted for a different audience.
Want to try a different market? Change
document.localeanddocument.timezoneto any of the values in the Locales and Timezones before sending — the rest of the request stays exactly the same.
Reusing the same data for a new locale only works cleanly if the underlying date values are unambiguous — as covered in Multi-locale Output,
date()parsing is locale-dependent, so the same string can resolve differently under a new locale. Check the generated output to confirm the date rendered correctly before moving on.
Send the request. A 201 Created response confirms generation, with the new document's URN saved automatically as {{mission3.germanDocumentId}}. Download and open it to confirm the dates and formatting now reflect the German locale — you'll reference this same URN directly in the next step, no re-upload needed.
Open Step 3 — Create the Envelope Template. This defines the reusable signing structure once — document, recipient role, and signature field — using templateRole instead of a real name and email. The document is referenced directly by {{mission3.germanDocumentId}} from Step 2.
Send the request. A 201 Created confirms the template is saved, with its ID saved automatically as {{mission3.envelopeTemplateId}}.
Before sending, set two collection variables — mission3.customerAName and mission3.customerAEmail — to a real name and an email address you have access to. This is the recipient who'll receive the signing invitation.
Open Step 4 — Instantiate for Customer A. This is the payoff — a single call supplies just the recipient's real name and email, matched to the template by templateRole, and Doctavian assembles the full envelope from the template automatically.
Send the request. A 201 Created confirms a new envelope, ready to send.
Run the same request again with a different name and email — Customer B, Customer C, anyone — and you'll get a brand new, independent envelope every time.
The envelope from Step 4 is sitting in Draft until you send it — no notification has gone out yet. Open Step 5 — Send the envelope and send the request. This is the same one-line send call used in Mission 2, regardless of whether the envelope was built by hand or instantiated from a template.
A 200 OK confirms the envelope is sent. Customer A receives an email notification with a personalised signing link — the same experience as any other Doctavian envelope.
The empire runs itself now. Same templates, same pipelines, any language, any customer, any volume — World Industries didn't grow by doing things twice, and neither did you.