[
https://issues.apache.org/jira/browse/NIFI-16240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Fellows reassigned NIFI-16240:
----------------------------------
Assignee: Rob Fellows
> Navigate directly to the referenced Parameter when following a Parameter
> reference from a component property
> ------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-16240
> URL: https://issues.apache.org/jira/browse/NIFI-16240
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Reporter: Rob Fellows
> Assignee: Rob Fellows
> Priority: Major
>
> When a Processor, Controller Service, Reporting Task, or Parameter Provider
> property value contains a Parameter reference
> {noformat}
> #{param}{noformat}
> the property table offers a link to the Parameter Context. Following that
> link opens the bound
> Parameter Context edit dialog on the full parameter list - it does not select
> or scroll to the parameter that was actually referenced. In a Parameter
> Context
> with many parameters the user still has to locate the parameter manually,
> which
> removes most of the value of the link.
> PropertyTable.canGoToParameter records this limitation in a TODO:
> {code:java}
> // TODO - currently parameter context route does not support navigating
> // directly to a specific parameter so the parameter context link
> // is not item specific.
> {code}
> Once the Parameter Context edit dialog accepts a target parameter via the
> highlightedParameterName navigation state (NIFI-16217), which selects the
> parameter and scrolls it into view. That capability was added for navigating
> to an inherited
> Parameter from within the Parameter Context editor, so the limitation above
> can
> now be lifted.
> Scope:
> * Extract the referenced parameter name from the property value.
> PropertyTable.PARAM_REF_REGEX already matches the reference.
> * Pass the parameter name through the goToParameter callback, which currently
> receives the raw property value rather than the parameter name.
> * Update the hosts that wire goToParameter for the property table
> (flow.effects.ts, controller-services.effects.ts,
> connector-canvas.effects.ts,
> connector-controller-services.effects.ts) to supply highlightedParameterName
> in the navigation state.
> * When the bound Parameter Context inherits from other contexts, resolve the
> reference to the context that actually defines the parameter so the
> highlight
> lands in the correct dialog.
> * Decide and implement the behavior for property values containing multiple
> parameter references.
> * Remove the TODO and add coverage in property-table.component.spec.ts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
