UNILIN-UNIMAT: Uniforms
Uniforms
The old source document described uniforms as the structure used to limit which generic article types a wearer can access. In the current interface that business meaning remains, even though Q-Cloud 2 terminology maps uniforms to customer-scoped credit-limit templates.
Uniform identity is uniform number within the customer scope resolved from the device.
In the current interface, uniforms are implemented as customer-scoped credit-limit templates. Wearer rows may reference a uniform before the A row that creates it appears later in the same file; that reference is resolved once the template exists. If a referenced uniform never exists and is not created in the file, the wearer row is treated as an error.
T.A Add New Uniform
- Purpose
-
Creates or updates a uniform in the resolved customer scope. In Q-Cloud 2 terms, this means creating or updating the matching credit-limit template.
- Valid for
-
All uniforms.
- What happens when the row is read
-
The device resolves the customer scope, and the uniform number is checked in that scope.
- If the uniform already exists
-
The existing uniform is kept or updated so that its name matches the row. If it already matches, the row becomes a no-op.
- If the uniform does not exist
-
A new uniform is created.
- Note
-
This is also the row that satisfies deferred wearer references to the same uniform number from earlier
T.1andT.5rows in the same file.
Fields:
| Field | Length | Format | Explanation |
|---|---|---|---|
Mutation code |
1 |
|
Always |
Wearer number |
15 |
alphanumeric |
Source reference only. |
Administration no |
10 |
numeric |
Virtual wearer reference from the legacy format. |
Unimat number |
3 |
numeric |
Device number used for customer resolution. |
Uniform number |
2 |
numeric |
Uniform identity within customer scope. |
Uniform name |
30 |
alphanumeric |
Uniform display name. |
Customer no. |
6 |
alphanumeric |
Descriptive source value only. |
Not used |
- |
empty |
Empty. |
T.B Delete Uniform
- Purpose
-
Deletes a uniform from the resolved customer scope.
- Valid for
-
Uniforms that should no longer remain in Q-Cloud 2.
- What happens when the row is read
-
The uniform is resolved in customer scope.
- If the uniform exists
-
The uniform is deleted.
- If the uniform does not exist
-
No business change is made.
- Note
-
The sender should only use this mutation when the uniform is no longer wanted in Q-Cloud 2. The current interface treats a missing uniform as a no-op.
Fields:
| Field | Length | Format | Explanation |
|---|---|---|---|
Mutation code |
1 |
|
Always |
Unimat number |
3 |
numeric |
Device number used for customer resolution. |
Uniform number |
2 |
numeric |
Uniform identity. |
T.C Add Article To Uniform
- Purpose
-
Connects an article to a uniform. In Q-Cloud 2 terms, this adds the article to the matching credit-limit template.
- Valid for
-
Articles that exist in the same customer scope as the uniform.
- What happens when the row is read
-
The uniform and article are resolved in the customer scope derived from the device.
- If both exist
-
The article is connected to the uniform. If that link already exists, the row becomes a no-op.
- If either is missing
-
The mutation is invalid.
- Note
-
The article must already exist in the same customer scope. This row does not introduce a new article code on its own.
Fields:
| Field | Length | Format | Explanation |
|---|---|---|---|
Mutation code |
1 |
|
Always |
Article code |
10 |
alphanumeric |
Article identity. |
Unimat number |
3 |
numeric |
Device number used for customer resolution. |
Uniform number |
2 |
numeric |
Uniform identity. |
T.D Delete Article From Uniform
- Purpose
-
Removes an article from a uniform. In Q-Cloud 2 terms, this removes the article from the matching credit-limit template.
- Valid for
-
Articles currently connected to the uniform.
- What happens when the row is read
-
The uniform and article are resolved in the same customer scope.
- If both exist and are connected
-
The article is removed from the uniform.
- If the required link does not exist
-
No business change is made.
- If the uniform or article does not exist
-
The row is invalid.
Fields:
| Field | Length | Format | Explanation |
|---|---|---|---|
Mutation code |
1 |
|
Always |
Article code |
10 |
alphanumeric |
Article identity. |
Unimat number |
3 |
numeric |
Device number used for customer resolution. |
Uniform number |
2 |
numeric |
Uniform identity. |