Description
Preserve an explicit agreement party-role record.
Quality assurance links actions, evidence, document versions, responsible roles and controlled dates. A recorded closed or approved label differs from verified completion and effectiveness. Due-date margins and missing-training flags organize supplied records while substantive review, competence and applicable quality obligations remain separate questions.
Preserve an explicit agreement party-role record.
When to use this tool
Use Quality Agreement Party Role when you already have agreementId, partyId, roleWording and need to preserve an explicit agreement party-role record.
How to use the tool and how it works
- Enter agreementId, partyId, roleWording. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter agreementId, partyId, roleWording using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| agreementId | Agreement Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| partyId | Party Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| roleWording | Role Wording | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"agreementId": "AGR17",
"partyId": "ORG2",
"roleWording": "supplier"
},
"output": {
"token": "[\"AGR17\",\"ORG2\",\"supplier\"]"
}
}Limitations and assumptions
- The result records supplied values without assigning legal responsibilities. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Review the controlled action, training, agreement and evidence records for actual completion and effectiveness. Reconcile versions, named responsibility and approval history rather than inferring a verified quality status from one marker or calendar gap.
References
Similar or alternative tools
- Quality Complaint Batch Reference
Qualify an explicit complaint by product and batch identifiers.
- Quality Evidence Record Version
Qualify an explicit quality-evidence reference by version.