feat(app-shell): Studio flow start node offers a "Record created or updated" trigger (#3427)#2809
Merged
Conversation
…pdated" trigger (#3427) The record-change trigger now supports record-after-write (create OR update in one flow), so the flow designer's start-node trigger picker offers a "Record created or updated" option. Selecting it shows the Object and Entry-condition fields, and the scope resolver puts both `record` and `previous` in scope for it (`previous == null` is how an author branches the create leg) — mirroring the runtime binding that fires the flow on both insert and update. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018939yJ413zG3irLzcTtqaa
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
os-zhuang
marked this pull request as ready for review
July 24, 2026 15:05
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.
Summary
Companion UI change for objectstack-ai/objectstack#3427 (backend PR: objectstack-ai/objectstack#3446).
The record-change trigger now supports
record-after-write— one flow that fires on create OR update. This surfaces that option in the Studio flow designer so authors can pick it visually instead of hand-editing metadata (the issue noted the single-event constraint "isn't obvious from the start node schema").Changes
All in
packages/app-shell/src/views/metadata-admin/:inspectors/flow-node-config.ts— the start node's triggerselectgains a "Record created or updated" (record-after-write) option, and it's added to theshowWhengates for the Object and Entry condition fields so both render when it's picked. The condition help now notesprevious == nullselects the create path.inspectors/flow-scope.ts—record-after-write/record-before-writeare added toRECORD_TRIGGER_TYPES(sorecord.*is in scope) and toPREVIOUS_TRIGGER_TYPES(a write trigger fires on update too, sopreviousmust be offered — it's how an author branches create vs update).i18n.ts— Chinese label for the new option (记录创建或更新后).Tests
flow-node-config.test.ts— asserts the picker offersrecord-after-writeand shows Object + Entry-condition for it.flow-scope.test.ts— asserts arecord-after-writestart node puts bothrecordandpreviousin scope.All 26 flow-related test files pass (258 tests);
@object-ui/app-shelltypechecks clean (tsc).Changeset
patchbump for@object-ui/app-shell.Generated by Claude Code