[
https://issues.apache.org/jira/browse/NIFI-16553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bean updated NIFI-16553:
-----------------------------
Description:
In the UpdateAttribute advanced configuration, rules can be reordered. This is
true only if "Reorder rules" is toggled on. When it is, reordering is
possible, but modifying rules is locked. The "Reorder rules" must be toggled
off to allow modification of rules.
The "Reorder Rules" toggle only appears when "Use original FlowFile for
matching rules" is toggled on.
Consider the case when both "Use original FlowFile for matching rules" and
"Reorder rules" are turned on. Then, "Use original FlowFile for matching rules"
is turned off. The "Reorder rules" is no longer visible and its state cannot be
changed. The user is left in a position of not being able to modify rules.
Whenever "Use original FlowFile for matching rules" is disabled, the "Reorder
rules" should be disabled as well. This prevents the locking of rules, and it
is consistent with expected behavior where the order of rules is irrelevant
when not using the original FlowFile for matching rules.
Alternatively, the "Reorder rules" toggle should be present all the time and
reordering allowed. This gives greater flexibility and allows the user to
implement whichever order they desire, e.g. alphabetical, numerical, etc. even
if the order is not important to the outcome.
was:
In the UpdateAttribute advanced configuration, rules can be reordered. This is
true only if "Reorder rules" is toggled on. When it is, reordering is
possible, but modifying rules is locked. The "Reorder rules" must be toggled
off to allow modification of rules.
The "Reorder Rules" toggle only appears when "Use original FlowFile for
matching rules" is toggled on.
Consider the case when both "Use original FlowFile for matching rules" and
"Reorder rules" are turned on. Then, "Use original FlowFile for matching rules"
is turned off. The "Reorder rules" is no longer visible and its state cannot be
changed. The user is left in a position of not being able to modify rules.
Whenever "Use original FlowFile for matching rules" is disabled, the "Reorder
rules" should be disabled as well. This prevents the locking of rules, and it
is consistent with expected behavior where the order of rules is irrelevant
when not using the original FlowFile for matching rules.
> Improve UX for UpdateAttribute reorder rules option
> ---------------------------------------------------
>
> Key: NIFI-16553
> URL: https://issues.apache.org/jira/browse/NIFI-16553
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mark Bean
> Assignee: Mark Bean
> Priority: Major
>
> In the UpdateAttribute advanced configuration, rules can be reordered. This
> is true only if "Reorder rules" is toggled on. When it is, reordering is
> possible, but modifying rules is locked. The "Reorder rules" must be toggled
> off to allow modification of rules.
> The "Reorder Rules" toggle only appears when "Use original FlowFile for
> matching rules" is toggled on.
> Consider the case when both "Use original FlowFile for matching rules" and
> "Reorder rules" are turned on. Then, "Use original FlowFile for matching
> rules" is turned off. The "Reorder rules" is no longer visible and its state
> cannot be changed. The user is left in a position of not being able to modify
> rules.
> Whenever "Use original FlowFile for matching rules" is disabled, the "Reorder
> rules" should be disabled as well. This prevents the locking of rules, and it
> is consistent with expected behavior where the order of rules is irrelevant
> when not using the original FlowFile for matching rules.
> Alternatively, the "Reorder rules" toggle should be present all the time and
> reordering allowed. This gives greater flexibility and allows the user to
> implement whichever order they desire, e.g. alphabetical, numerical, etc.
> even if the order is not important to the outcome.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
