PR#1497 — Merge main into staging - #1498
Merged
Merged
Conversation
The Create Artifact step's Title and Description now accept the same variables the Broadcast step's Subject and Message accept, so an artifact raised by a workflow can name the record it runs against — and, on a breach-triggered workflow, the metric that breached. - Workflow step types: a footnote on Title covering both fields, following the pattern the Broadcast rows use. It notes that variables which cannot be filled in for this step are not offered, and that Title is stored as plain text while Description keeps its formatting. - Trigger workflows on threshold breach: the breach-details section covered broadcasts only, so it is widened to both steps and retitled. The trigger-change warning now says the rejection names the step as well as the variable, and the "what a breach sends" note records that one artifact is raised per breach rather than per failing reading. The retitled section changes its anchor, so the Broadcast footnote's link to it is repointed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The Monitoring Breach table was retitled from "broadcast variables" to "variables" and moved under a section covering both the Broadcast and Create Artifact steps, but it still lists Monitoring Document URL without qualification. That variable is withheld from Create Artifact, along with Record URL, so a reader following this page opens the picker and cannot find the row the table promised. Mark the row, and say why once: a link is written differently for each reader, so it suits a step that writes its text once per recipient and not one that writes once and stores the result for everyone. The step types footnote gave two reasons for a variable being absent -- no recipient, and no artifact yet -- and neither covers a link, so it gains the same sentence. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011uw61mH5X2xvAG6XQobTVh
…s-in-create-artifact-step [SC-18126] Insert variables in the Create Artifact step's title and description
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
1 participant
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.
Automatically merge main into staging branch.