Description
Find matching and conflicting prior statuses for a public-service ticket.
Administrative records connect requests, forms, permits, delegated roles, assets and payment bases. A retained amount or supplied authority limit describes one accounting convention, while matching and conflicting statuses can coexist in duplicate records. Such local checks do not establish authorization, legal validity, actual service delivery or compliance.
Find matching and conflicting prior statuses for a public-service ticket.
When to use this tool
Use Public Service Ticket Duplicate Status when you already have ticketId, knownTicketIds, knownStatuses, suppliedStatus and need to find matching and conflicting prior statuses for a public-service ticket.
How to use the tool and how it works
- Enter ticketId, knownTicketIds, knownStatuses, suppliedStatus. Follow any array-alignment requirements below. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read priorIdFound, sameStatusFound, conflictingStatusFound. Inspect priorIdFound, sameStatusFound, conflictingStatusFound before interpreting the associated values.
Require ticketId/status nonempty and aligned known ID/status arrays. Check any prior ID match, any same-status match and any differing-status match separately.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| ticketId | Ticket Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| knownTicketIds | Known Ticket Ids | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| knownStatuses | Known Statuses | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| suppliedStatus | Supplied Status | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| priorIdFound | Prior Id Found | Required. Boolean. |
| sameStatusFound | At least one matching prior ID/status pair; may coexist with conflictingStatusFound. | Required. Boolean. |
| conflictingStatusFound | Conflicting Status Found | Required. Boolean. |
{
"input": {
"ticketId": "T17",
"knownTicketIds": [
"T17",
"T18"
],
"knownStatuses": [
"open",
"closed"
],
"suppliedStatus": "closed"
},
"output": {
"priorIdFound": true,
"sameStatusFound": false,
"conflictingStatusFound": true
}
}Limitations and assumptions
- Both sameStatusFound and conflictingStatusFound can be true; no record is changed, deduplicated or 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
Reconcile the original case, permit, asset and payment records with the applicable authority and fee rules. For duplicate statuses, inspect the full history and timestamps before choosing a current record; this helper reports matches without resolving them.
References
Similar or alternative tools
- Quality Complaint Batch Reference
Qualify an explicit complaint by product and batch identifiers.
- Administrative Review Stage Handoff
Qualify an explicit administrative review-stage handoff.