<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System Data on Manage.ID Documentation</title><link>/system-data/</link><description>Recent content in System Data on Manage.ID Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="/system-data/index.xml" rel="self" type="application/rss+xml"/><item><title>FIFO</title><link>/system-data/fifo/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/system-data/fifo/</guid><description>&lt;h3 id="about-this-task"&gt;About this task&lt;a class="td-heading-self-link" href="#about-this-task" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A FIFO queue is a named, ordered buffer that a coding scenario can push records into and later get back out in arrival order. Use it to decouple two parts of a process — for example, buffer items scanned at one station and process them, in order, at a downstream station whenever it has capacity. The queue itself only holds a reference to each item; a coding scenario reads or writes it using the &lt;strong&gt;FIFO push item&lt;/strong&gt;, &lt;strong&gt;FIFO get item&lt;/strong&gt;, and &lt;strong&gt;FIFO delete item&lt;/strong&gt; steps (see Coding Scenarios).&lt;/p&gt;</description></item><item><title>Statuses</title><link>/system-data/statuses/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/system-data/statuses/</guid><description>&lt;p&gt;&lt;em&gt;Available only when the Statuses feature is enabled.&lt;/em&gt;&lt;/p&gt;&#10;&lt;h3 id="about-this-task"&gt;About this task&lt;a class="td-heading-self-link" href="#about-this-task" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A status is a user-defined label — for example Draft, Active, Suspended, or Archived — that tracks the state of a product, production order, or logistic unit as it moves through the production process. A coding scenario&amp;rsquo;s &amp;ldquo;Set status to&amp;hellip;&amp;rdquo; steps assign it, and other steps can gate on it (for example &lt;strong&gt;Check logistic unit status&lt;/strong&gt;) — see Coding Scenarios.&lt;/p&gt;</description></item><item><title>Counter</title><link>/system-data/counter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/system-data/counter/</guid><description>&lt;h3 id="about-this-task"&gt;About this task&lt;a class="td-heading-self-link" href="#about-this-task" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A counter is a named, persistent numeric value — for example a serial or batch number — that a coding scenario can read, and that can increment automatically on every print. Coding-scenario steps can also increment, decrement, reset, or evaluate a counter explicitly (see Coding Scenarios).&lt;/p&gt;&#10;&lt;h3 id="procedure"&gt;Procedure&lt;a class="td-heading-self-link" href="#procedure" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;ol&gt;&#10;&lt;li&gt;In the side bar, select &lt;strong&gt;System Data&lt;/strong&gt; and click &lt;strong&gt;Counter&lt;/strong&gt;.&lt;/li&gt;&#10;&lt;li&gt;Click the add icon to create a new counter.&lt;/li&gt;&#10;&lt;li&gt;Enter a &lt;strong&gt;name&lt;/strong&gt; for the counter.&lt;/li&gt;&#10;&lt;li&gt;Select the counter&amp;rsquo;s &lt;strong&gt;type&lt;/strong&gt;:&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Global&lt;/strong&gt; — one shared value used everywhere.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Per Line&lt;/strong&gt; — a separate value for each production line. Only available when &lt;strong&gt;Increment on every print&lt;/strong&gt; is off.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Per Printer&lt;/strong&gt; — a separate value for each printer. Only available when &lt;strong&gt;Increment on every print&lt;/strong&gt; is on.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;Enter the &lt;strong&gt;start&lt;/strong&gt;, &lt;strong&gt;current&lt;/strong&gt;, and &lt;strong&gt;end value&lt;/strong&gt; (current must fall between start and end), and the counter&amp;rsquo;s &lt;strong&gt;length&lt;/strong&gt;.&lt;/li&gt;&#10;&lt;li&gt;Optionally enable &lt;strong&gt;Daily reset&lt;/strong&gt; (resets the value once a day), &lt;strong&gt;Increment on every print&lt;/strong&gt;, and &lt;strong&gt;Calculate check digit at the end&lt;/strong&gt;.&lt;/li&gt;&#10;&lt;li&gt;For a &lt;strong&gt;Per Line&lt;/strong&gt; or &lt;strong&gt;Per Printer&lt;/strong&gt; counter, set the start/current/end values for each line or printer individually.&lt;/li&gt;&#10;&lt;li&gt;Save the counter.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h3 id="results"&gt;Results&lt;a class="td-heading-self-link" href="#results" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;The counter is available for use in a coding scenario and, if configured, increments automatically on every print.&lt;/p&gt;</description></item><item><title>Defining Tags</title><link>/system-data/tags/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/system-data/tags/</guid><description>&lt;h3 id="before-you-begin"&gt;Before you begin&lt;a class="td-heading-self-link" href="#before-you-begin" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;ul&gt;&#10;&lt;li&gt;You are assigned to a user group that at least has the permission Change production data.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="about-this-task"&gt;About this task&lt;a class="td-heading-self-link" href="#about-this-task" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h3&gt;&lt;p&gt;A tag is a simple, reusable label used to match things together — most commonly a label layout to a printer, so a coding scenario can pick the right layout for a given printer without hard-coding names. Beyond layouts and printers, a resource file or an import task can also carry a tag. A tag is only defined here; it&amp;rsquo;s assigned to a device, layout, resource, or import task on that item&amp;rsquo;s own configuration page.&lt;/p&gt;</description></item></channel></rss>