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.
Description: Resolved an issue in the Flow Path – Absences page where users were unable to close the page after creating an incomplete absence mapping. The validation behavior was adjusted so that users can now cancel and exit the page without being forced to complete the mapping.
Impact: Users can now safely abandon incomplete absence mappings and close the Flow Path – Absences page without repeated validation prompts, improving usability and preventing unnecessary lock-in on the page.
Description: Resolved an issue where templates referencing deleted catalogs were not properly cleaned up and continued to appear in the Template selection within the Entry Wizard.
Impact: Templates that no longer contain valid catalog entries are now correctly removed from the Entry Wizard, preventing selection of obsolete templates and ensuring catalog and template data remain consistent.
Description: Resolved an issue in the Flow Path Question Entry creation process where selecting a single question from a catalog resulted in all catalog questions being added to the entry. The logic has been corrected so that only the questions explicitly selected by the user are included in the created Question Entry.
Impact: Users can now reliably create Question Entries that contain only their chosen questions, ensuring accurate data capture and preventing unintended questions from appearing. This improves usability, reduces confusion, and aligns the system behavior with user expectations.
**Description:** Corrected the task text editor header in the Sales Invoice module so that it consistently displays "Task" instead of "Question" when opening and editing task content. This aligns the interface terminology with the underlying task functionality.
**Impact:** Users now see accurate and consistent task-related labels and headers, reducing confusion and improving usability when creating and editing tasks in the Sales Invoice workflow. No functional side effects are expected.