Description
Increment a recorded client-contact attempt count when an attempt is flagged.
Support records distinguish a person's stated preferences from eligibility decisions, service delivery and permission to disclose data. A normalized goal weight describes a declared weighting system, while a voucher or referral time margin describes supplied bookkeeping. Labels and display masks do not establish safety, valid consent, appropriate priority or actual entitlement.
Increment a recorded client-contact attempt count when an attempt is flagged.
When to use this tool
Use Client Contact Attempt Count Step when you already have previousAttempts, attemptRecorded and need to increment a recorded client-contact attempt count when an attempt is flagged.
How to use the tool and how it works
- Enter previousAttempts, attemptRecorded. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read updatedAttempts. Use the output convention below.
Require nonnegative safe whole previousAttempts; add zero or one with BigInt and export the updated count as a number.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| previousAttempts | Previous Attempts | Required. Safe integer; minimum 0. |
| attemptRecorded | Attempt Recorded | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| updatedAttempts | Safe integer result; previous maximum plus one is rejected. | Required. Safe integer. |
{
"input": {
"previousAttempts": 3,
"attemptRecorded": true
},
"output": {
"updatedAttempts": 4
}
}Limitations and assumptions
- This does not contact anyone or verify an attempt. Incrementing the maximum safe count is rejected by the output contract.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Review the person's recorded preferences, governing service criteria and actual referral or voucher records. For disclosure, apply the relevant access controls to the underlying data rather than treating a display mask or recorded permission flag as the whole process.
References
Similar or alternative tools
- Health Promotion Attendee Session Count
Count recorded attendances, distinct attendees and distinct sessions.
- Public Service Ticket Duplicate Status
Find matching and conflicting prior statuses for a public-service ticket.