fix(analytics/Pipelines): drop the derived outputs from the variables section - #4550
Merged
dearsimanovich-epam merged 3 commits intoSep 15, 2026
Conversation
… section Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dearsimanovich-epam
requested review from
Gimir,
NastassiaKryshtal,
PolinaGurinovich97,
denys-kolomiitsev and
ya092
as code owners
September 15, 2026 07:57
dearsimanovich-epam
enabled auto-merge (squash)
September 15, 2026 07:58
ya092
approved these changes
Sep 15, 2026
dearsimanovich-epam
deleted the
fix/analytics-pipeline-variables-drop-derived-outputs
branch
September 15, 2026 08:48
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
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.
Description:
The enrichment pipeline's variables section presented the pipeline's derived outputs — where the evaluator's answer lands — as disabled rows of the same list, on the reasoning that one list should state everything passing between a pipeline and its evaluator. On screen that reads as something the operator chose and may change; greying a row out says "not now", not "not yours". The outputs are never a member of the request: the service derives them from the evaluator's outputs matched to the target's columns. They also did not fit the shape — an output carries a target column and sometimes a transform, two facts against the one value cell a variable has, so the list either hid the transform or grew a cell that stood empty on nearly every row.
This change drops them from the form entirely. They remain readable in the JSON editor, which already presents the pipeline whole, including every member the service assigns or resolves.
Key Changes:
outputsprop, the disabled output rows and the derived-outputs note; the grid comment now states why the shared grid exists on its own termsform.outputsoutputsfrom the stored pipelineOutputsDerivedNotekey and copyopenspec/changes/archive/2026-09-15-drop-derived-outputs-from-pipeline-variables/— archived change carrying the rationaleChecklist:
(Issue #<ticket>)(comma-separated list of issues)🤖 Generated with Claude Code