Bug ID 1680361: Expression of the first branch missed after a Rule node was moved and saved

Last Modified: Feb 11, 2025

Affected Product(s):
BIG_IP_NEXT(CM) TMOS(all modules)

Known Affected Versions:
20.3.0

Opened: Sep 26, 2024

Severity: 1-Blocking

Symptoms

After moving a rule node within the same flow and saving the policy, when it was reopened, the moved nodes did not have accurate branch expressions.

Impact

This may cause errors during policy deployment, and incorrect branch expressions could also impact traffic flow.

Conditions

Move a Rule node from one point to another inside a Flow.

Workaround

This enhancement is designed to help users rearrange the policy without deleting the nodes. Even if an error occurs while moving the nodes, users can still be able to create the policy using the traditional method of dropping nodes from the sidebar.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips