UNILIN-UNIMAT: Changes From The Legacy Document

Purpose

This page explains how the current documentation relates to UNILIN-UNIMAT interface 6b.doc.

The old source document is still the stylistic reference for this section. The pages in this documentation have therefore been rewritten to follow the same kind of explanations:

  • Purpose

  • Valid for

  • what happens when a row is read

  • explicit notes and warnings

  • field tables using Field, Length, Format, and Explanation

What Stayed The Same

The following legacy concepts are intentionally preserved:

  • mutation-code based records

  • ordered delta semantics

  • control records as block boundaries

  • separate descriptions for wearers, garments, uniforms, messages, and rules

  • explicit warnings for serious error conditions

What Changed In Business Interpretation

The current interface still differs from the old environment in a few important ways:

  • device identity is authoritative for customer scope

  • customer values in the source row are descriptive only

  • wearer identity is administration no inside device-derived customer scope

  • generic garments are handled through item pools in Q-Cloud 2

  • some legacy mutations are recognised and logged, but they do not apply business changes in the current release

What Is More Explicit In This Version

The updated documentation also makes a few processing guarantees clearer than the old text did:

  • the interface is still an ordered delta interface and not a full replacement import

  • customer scope is determined from the device on each row

  • earlier valid rows in the same payload affect how later rows are interpreted

  • recognised unsupported mutations remain distinct from malformed input

  • technical optimisation must not change business order