docs(engagements): explain the locked Asset field and its copy button - #15873
Merged
Maffooch merged 1 commit intoSep 3, 2026
Merged
Conversation
The Create Engagements section told the reader they would have to select the Asset when completing the New Engagement form, but not that arriving from an Asset fills the field in and locks it. A locked field cannot be opened or text-selected, so without the note the locked state reads like a bug and the copy button on its right-hand edge has no explanation. Covers both, and points at the other place the same thing happens: the Engagement and Scan Type fields when adding a Test.
blakeaowens
approved these changes
Sep 3, 2026
Maffooch
approved these changes
Sep 3, 2026
devGregA
approved these changes
Sep 3, 2026
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
4 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.
[sc-15114]
Description
Documentation for a Pro change that ships on the same release line: fields on the Vue create
forms that arrive pre-filled from context are locked, and a locked field now carries a
copy-to-clipboard button on its right-hand edge.
The Engagements page already told the reader they would "have to select the Asset to which to
attribute the Engagement when completing the New Engagement form", but never mentioned that
arriving from an Asset fills that field in and locks it. A locked field also cannot be opened
or text-selected, so without the note the copy button is the only visible clue about how to
read the value, and the locked state itself reads like a bug.
Adds a short paragraph to the "Create Engagements" section of
docs/content/asset_modelling/engagements_tests/PRO__engagements.mdcovering both: why thefield is locked, and that the copy button is how you get the value out. It also points at the
other place the same thing happens, the Engagement and Scan Type fields when adding a Test.
Docs only — no code change.