<turbo-stream action="update" target="wiki_card"><template>

<h1>Schedule Tags</h1>
<div class="trix-content"><p>Tags make it possible to run the same set of Transfers for multiple companies without any duplication. The key is understanding how three things connect: <strong>Tag Values</strong>, <strong>Schedules</strong>, and the resulting <strong>named Schedule</strong> that gets created.<br><br></p><h2>Step 1 : Define your Tag Values</h2><p>The Tag Values table is where you define what each Tag resolves to for each company. Each row represents one company, and each column is a Tag — such as the connection, currency, or link storage reference.</p><p>In the example below, two companies are configured:</p><p></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>CONN</td><td>COMP</td><td>CURR</td><td>LSCUST</td></tr></thead><tbody><tr><td>NAVODATA001</td><td>Cronus DK</td><td>DKK</td><td>CUST_DK</td></tr><tr><td>NAVODATA002</td><td>Cronus ES</td><td>EUR</td><td>CUST_ES</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><p>When a Transfer runs for Cronus DK, every Tag in that Transfer - %%CONN%, %%COMP%, %%CURR%, %%LSCUST%, etc. - is automatically replaced with the values from that row.<br><br></p><h2>Step 2 : Create a Schedule and select a company</h2><p>When setting up a Schedule, the <strong>Select Tags</strong> dropdown lists one entry per row in your Tag Values table. Simply select the company you want this Schedule to run for ( for example <em>COMPANY - NAVODATA001: Cronus DK</em>.) This tells the Schedule which set of Tag Values to use every time it fires.<br><br><br></p><h2>Step 3 : The Schedule is created and named automatically</h2><p>Once saved, the Schedule is automatically given a name that reflects exactly what it does : for example <em>G_CUST_NAVODATA001_CRONUS_DK</em>. The name is derived from the Tag Values, so it is always clear which Transfer group is running, against which connection, and for which company.</p></div>
</template></turbo-stream>

