Skip to content

Commit 487ad8d

Browse files
committed
docs(skills): say which door judges a bare field name in a flow condition
A bare `budget` in a record-triggered flow's condition is judged by `os validate` (where the flow's bound names are provable); the runtime publish gate judges the written flow alone and resolves no bare name. The skill callout, the flows page item and eval #9 now say `os validate` where they said "the gate" or "refused the same way", measured against the lint source at both doors. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WGufzfSZ55f7xwAfpfkPgY
1 parent 931f02a commit 487ad8d

3 files changed

Lines changed: 3 additions & 3 deletions

File tree

‎content/docs/automation/flows.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2453,7 +2453,7 @@ and is read as `vars["current_user"]` / `vars["vars"]`.
24532453
`== null` / `!isBlank()` in the same branch: the run binds every declared
24542454
field, `null` when empty, CEL has no `>` for null, and the run fails there
24552455
while the write that fired it still lands. A bare `budget` is `record.budget`,
2456-
judged alike; a start-condition guard holds at every edge and branch — spell
2456+
and `os validate` judges it too; a start guard holds at every edge and branch — spell
24572457
it `record.budget != null`, which both doors accept, and `has()` is no guard.
24582458
</Callout>
24592459

‎skills/objectstack-formula/SKILL.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -389,7 +389,7 @@ When migrating Salesforce-flavor metadata, apply these rules in order:
389389
> ⚠️ **Flow conditions are the exception to row 1.** The engine spreads the
390390
> trigger record's fields, nulls included, to top level wherever no flow variable
391391
> or node id holds the name, so in a start, edge or `decision` condition a bare
392-
> `budget` IS `record.budget`: the null-guard gate judges either spelling (bare
392+
> `budget` IS `record.budget`: `os validate` judges either spelling (bare
393393
> names only while every node's bindings are declared), a guard on one spelling
394394
> guards both, and what the start condition proves non-null is presumed at every
395395
> edge and branch. Spell that start guard `record.budget != null`: the runtime

‎skills/objectstack-formula/evals/cel-predicates-formulas.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@
8484
{
8585
"id": 9,
8686
"prompt": "A record-change flow on `project` (start `triggerType: 'record-after-update'`, `objectName: 'project'`) escalates when the budget passes 200000. `budget` is a currency field with no `required` and no `defaultValue`. Write the edge condition from the decision node to the escalation branch.",
87-
"expected_output": "`record.budget != null && record.budget > 200000`. The run binds every declared field of the trigger record, `null` when empty, and CEL has no `>` overload for null, so `os validate` and the runtime publish gate refuse the unguarded edge; at runtime the run would fail at that edge while the write that fired it still lands. A bare `budget > 200000` is the same field and is refused the same way, and `has(record.budget)` is not a guard: a declared field holding null is still present.",
87+
"expected_output": "`record.budget != null && record.budget > 200000`. The run binds every declared field of the trigger record, `null` when empty, and CEL has no `>` overload for null, so `os validate` and the runtime publish gate refuse the unguarded edge; at runtime the run would fail at that edge while the write that fired it still lands. A bare `budget > 200000` is the same field, and `os validate` refuses it too; and `has(record.budget)` is not a guard: a declared field holding null is still present.",
8888
"files": [],
8989
"assertions": {
9090
"must_contain": ["record.budget != null", "record.budget > 200000"],

0 commit comments

Comments
 (0)