Description
Increment an action-item reopen count when a reopen event is recorded.
Project records separate planned effort, recorded time, forecast assumptions, resource buffers and role authority. A probability-weighted impact is one scenario term, and a calendar-day shift is not a business-calendar calculation. Local progress and workload shares need consistent scope and periods before broader interpretation.
Increment an action-item reopen count when a reopen event is recorded.
When to use this tool
Use Action Item Reopen Count Step when you already have previousReopenCount, eventIsReopen and need to increment an action-item reopen count when a reopen event is recorded.
How to use the tool and how it works
- Enter previousReopenCount, eventIsReopen. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read updatedReopenCount. Use the output convention below.
Require nonnegative safe whole previousReopenCount; add one or zero with BigInt and export a safe integer.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| previousReopenCount | Previous Reopen Count | Required. Safe integer; minimum 0. |
| eventIsReopen | Event Is Reopen | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| updatedReopenCount | Adds one only for a reopen event; an unsafe integer output is rejected. | Required. Safe integer. |
{
"input": {
"previousReopenCount": 3,
"eventIsReopen": true
},
"output": {
"updatedReopenCount": 4
}
}Limitations and assumptions
- Incrementing the maximum safe count is rejected; the tool does not verify an event or update an external action log.
- 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
Reconcile the complete plan, resource calendar, costs and action history for an operational question. Use the actual business calendar or delegated-role documentation when required, rather than treating one supplied offset or Boolean as that full workflow.
References
Similar or alternative tools
- Approval Substitute Role Date Flag
Check a recorded substitute role within a closed date interval.
- Business Day Target Calendar Offset
Shift a reference date by supplied calendar days.