Why a save must not change a workflow step this way, or null when it may.
A workflow step (a task with a parent and a StepType) feeds what it produced into the steps after it,
runs what its definition names, waits on whom it is assigned to, and its name and description become the
question its Human step's request asks. The submitter's own code (an agent run calling Update Record, which
runs as the submitter) could otherwise rewrite the output of a step that ran clean, the input or the action
of a step waiting to run, the answer a Human step will carry before its person approves it, or who that
person is; or rerun, skip or settle a step by its status. The graph would treat the result as trusted. So
outside the dispatcher's scope those cannot change on a saved step, except that the person a Human step is
assigned to may complete or reject it and give its output, their answer, in their own client request.
Parameters
changedFields: readonlystring[]
the owned columns this save changes
personCompletesOwnHumanStep: boolean
this save is the assignee completing their Human step, as their own client request
Why a save must not change a workflow step this way, or null when it may.
A workflow step (a task with a parent and a
StepType) feeds what it produced into the steps after it, runs what its definition names, waits on whom it is assigned to, and its name and description become the question its Human step's request asks. The submitter's own code (an agent run calling Update Record, which runs as the submitter) could otherwise rewrite the output of a step that ran clean, the input or the action of a step waiting to run, the answer a Human step will carry before its person approves it, or who that person is; or rerun, skip or settle a step by its status. The graph would treat the result as trusted. So outside the dispatcher's scope those cannot change on a saved step, except that the person a Human step is assigned to may complete or reject it and give its output, their answer, in their own client request.