Description
Require nonempty taskId and mark vacant when ownerId contains only whitespace or is empty.
Capacity accounting compares available supply with commitments, reservations, or demand. Negative residuals can expose overload while zero capacity requires a distinct undefined utilization state.
Require nonempty taskId and mark vacant when ownerId contains only whitespace or is empty.
When to use this tool
Use Task Owner Vacancy Flag when you need a transparent resource or workload capacity term.
How to use the tool and how it works
- Enter taskId, ownerId. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read vacant. Inspect vacant before interpreting the associated values.
Require nonempty taskId and mark vacant when ownerId contains only whitespace or is empty.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| taskId | Task Id | Required. Text; maximum UTF-16 length 8192. |
| ownerId | Owner Id | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| vacant | Vacant | Required. Boolean. |
{
"input": {
"taskId": "T17",
"ownerId": ""
},
"output": {
"vacant": true
}
}Limitations and assumptions
- An owner string is not normalized or authenticated; nonvacant does not prove authority, availability, or accepted responsibility.
- 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
Validate calendars, skill constraints, and concurrent demand with the actual resource plan.
References
Similar or alternative tools
- Security Control Owner Vacancy
Count distinct exact owner strings and mark vacant for zero owners.
- Professional Role Recusal Label
Require nonempty role and append recused or not recorded as recused according to the Boolean flag.