feat(workflow-executor): deterministic source record for Update Data steps (PRD-777)#1761
Merged
Conversation
3 new issues
|
![macroscopeapp[bot]](https://avatars.githubusercontent.com/in/900172?s=60&v=4){kind=small}
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
EnkiP
force-pushed
the
workflow/deterministic-update-data
branch
from
July 16, 2026 07:54
7fa69b5 to
2a2dbdd
Compare
|
Coverage Impact ⬆️ Merging this pull request will increase total coverage on Modified Files with Diff Coverage (2)
🛟 Help
|
…I-resolved value The build-time config lets the Editor pin the field while leaving the value to the runtime prompt. The 'fieldName and value must both be provided or both omitted' guard wrongly rejected that, throwing InvalidPreRecordedArgsError. Now a value-less fieldName pins the field and the AI resolves only the value. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
EnkiP
force-pushed
the
workflow/deterministic-update-data
branch
from
July 16, 2026 15:19
6a1f30f to
8dad337
Compare
added 2 commits
July 17, 2026 13:00
forest-bot
added a commit
that referenced
this pull request
Jul 21, 2026
# @forestadmin/workflow-executor [1.20.0](https://github.com/ForestAdmin/agent-nodejs/compare/@forestadmin/workflow-executor@1.19.0...@forestadmin/workflow-executor@1.20.0) (2026-07-21) ### Features * **workflow-executor:** deterministic source record for Update Data steps (PRD-777) ([#1761](#1761)) ([2589956](2589956))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of the deterministic Update Data step work.
fixes PRD-777
What
The
update-record(Update Data) step can now resolve its source record deterministically from a build-time-configured stable BPMN step id (selectedRecordStepId), mirroringread-record(Get Data) andtrigger-action— instead of always asking the AI to pick among the available records.Changes
UpdateRecordStepDefinitionSchema.preRecordedArgsgainsselectedRecordStepId(legacyselectedRecordStepIndexkept for back-compat;fieldName/valueunchanged).update-record-step-executor(handleFirstCall): whenselectedRecordStepIdis set, resolve viaresolveSourceRecordRef(revise-safe;WORKFLOW_START_STEP_ID→ base record). Falls back to legacy index / AI selection when unset.ServerWorkflowTaskUpdateData) + mapper forwardpreRecordedArgsforupdate-data.Tests
WORKFLOW_START_STEP_ID→ base record; unresolvable id → error.preRecordedArgs(selectedRecordStepId + fieldName + value).Companion PRs: forestadmin-server (orchestrator), forestadmin (editor UI).
🤖 Generated with Claude Code
Note
Add deterministic source record resolution and preRecordedArgs support to Update Data workflow steps
selectedRecordStepIdtopreRecordedArgsin UpdateRecordStepDefinitionSchema and the server task interface, allowing callers to pin the source record by BPMN step ID instead of index.UpdateRecordStepExecutor.handleFirstCallto support three tiers: (1)fieldName+valueuses both as-is, (2)fieldNamealone pins the field and asks the AI for the value via the newselectValueForFieldmethod, (3) neither defers fully to the AI.selectValueForField, a new method that builds a value-only AI tool (set-record-field-value) for pinned-field flows and coerces the returned value to the field's native type.forAiToolflag tobuildZodSchemaForPrimitive, using plainz.boolean()instead of az.preprocesstransform to avoid JSON Schema conversion errors.valueprovided withoutfieldNameinpreRecordedArgsnow throws an error; previously this combination was not validated.Macroscope summarized 7c2eb74.