Flow Path – Changing the filter of a Field Link deletes the existing Answer Field Link configuration and more
Fixed an issue where updating only the filter value in a Question’s Field Link configuration caused the associated Answer Field Link configuration to be removed, even though the Target Table and Target Field remained unchanged. The Answer Field Link now persists correctly when changes do not…
Fixed and improved
Description: Fixed an issue where updating only the filter value in a Question’s Field Link configuration caused the associated Answer Field Link configuration to be removed, even though the Target Table and Target Field remained unchanged. The Answer Field Link now persists correctly when changes do not invalidate its mapping.
Impact: Users no longer need to recreate Answer Field Link configurations after adjusting filter values on Question Field Links. This resolves unintended data loss in configuration, improves workflow efficiency, and ensures that valid Answer Field Link mappings remain intact when filters are modified.
Description: Resolved an issue where the Filter Value lookup in Field Link configuration did not display any selectable values, even when a valid Table and Filter Field were set. The lookup now correctly opens and shows available values for the configured Filter Field.
Impact: Users can now reliably select a Filter Value when configuring Field Links, ensuring that questions using Field Link answer types function as intended and improving the accuracy and usability of filter-based configurations.
Description: Resolved an issue where deleting a Task from a Flow Path Task Catalog did not remove its related Subtasks and Template references, leaving orphaned records that still pointed to the deleted Task. The deletion logic has been updated to consistently remove or update all directly dependent definition data when a Task is deleted.
Impact: Users can now safely delete Tasks from the Task Catalog without leaving inconsistent or orphaned Subtasks and Template Lines. This improves data integrity, prevents references to non-existent Tasks, and reduces the risk of errors or confusion when managing Flow Path definitions and templates.