Flow Path – Absences page cannot be closed when an incomplete absence mapping exists and more
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.
Fixed and improved
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.