Flow Path
Duplicate task creation after back Navigation in Subtask Wizard
Description: When creating a task from the Flow Path Factbox on a posted sales invoice, enabling the Subtask option and navigating back and forth in the wizard can result in multiple task entries being created upon finishing, even if no subtask is created. The number of duplicate task entries depends on how many times the user moved between steps in the wizard.
Impact: Users may experience unintended duplication of task entries, leading to inaccurate task records and potential confusion in task tracking and management.
Created: July 14, 2026
Priority: Medium
Flow Path allows Question creation on Pages without a selected Record
Description: When opening a page with no entries (for example, Purchase Quotes) and using the Flow Path Factbox to create a new question/task/information, a success message (“Your question was successfully created.”) is displayed even though no Flow Path question is actually created when no record is selected.
Impact: Users may believe that their Flow Path questions have been created and sent, while in reality no entries are generated, potentially leading to missed communications and process gaps.
Created: August 3, 2026
Priority: Medium
Flow Path allows creation of questions with Non-Existent Recipients
Description: When creating a Flow Path question from the Sales Invoice Flow Path Factbox, the system allows users to enter and save a recipient that does not exist. No validation message is displayed, and the question is created and assigned to a non-existent recipient.
Impact: Invalid or non-existent recipients can be stored on Flow Path questions, leading to misrouted or unassigned entries, reduced traceability, and potential confusion or delays in handling questions.
Created: August 3, 2026
Priority: Medium
Preselected template recipient is not Replaced by Representative User
Description: When creating question entries from a template that contains questions with a preselected recipient who is marked as absent and replaced by a representative, confirming the prompt to use the representative updates only the answer entries to the representative user. The question entries that had the absent user preselected remain assigned to the absent user, while questions without a preselected recipient are assigned to the representative. This results in a mismatch between the recipient shown on the question and the recipient shown on the corresponding answer entry.
Impact: Users see inconsistent recipient assignments between questions and answers, which can cause confusion about who is actually responsible for responding, complicate follow-up actions, and potentially lead to misrouted or missed communications in approval or review processes.
Created: August 4, 2026
Priority: Medium
Email Templates page cannot be opened due to missing Reminder.html resource
Description: When opening Email Templates in Flow Path as a Flow Path Admin, the page fails to load and an error is shown indicating that the resource Templates/Reminder.html cannot be found in the app “Flow Path by Simova GmbH 28.0.210312.0”. This prevents the Email Templates list from being displayed.
Impact: Flow Path Admins are unable to view or manage Email Templates, which may block configuration or maintenance of email notifications that rely on these templates.
Created: August 4, 2026
Priority: Medium
Substitute User cannot answer question after absence deletion
Description: When a question is created from a template for a user who is absent, the defined substitute is correctly assigned as the recipient and can initially answer the question. However, after the absence is removed, the substitute user loses the permission to answer the already created question, even though they remain listed as the recipient in the question entry.
Impact: Existing question entries created during an absence may become unanswerable by the substitute recipient once the original user’s absence is removed, potentially blocking the processing and completion of affected questions.
Created: August 4, 2026
Priority: Medium
HTML Tags are displayed in task entry instead of rendered Text
Description: When Flow Path users create a task from a Posted Sales Invoice or Sales Invoice and add formatted text in the text editor, reopening the task displays the description with raw HTML markup instead of the rendered formatting (for example, “Prüfen” appears as <div>Prüfen</div>).
Impact: Users see unrendered HTML tags in task descriptions, which reduces readability and may cause confusion when reviewing or editing task details.
Created: August 4, 2026
Priority: Medium
Task dialog uses "Question" header instead of "Task" header
Description: When opening and editing a task in Sales Invoice as a Flow Path Admin, the text editor header incorrectly displays "Question" instead of "Task", while all other captions, labels, and headers correctly refer to a task.
Impact: Users may be confused by the inconsistent terminology in the task editor, which can reduce clarity and trust in the interface, especially in scenarios where both questions and tasks are used.
Created: August 4, 2026
Priority: Medium
HTML Tags Visible in Created Subtasks
Description: When creating a Flow Path task with “SubTask” enabled and applying text color formatting in the editor, the generated subtasks display raw HTML markup instead of formatted text. In the Tasks section, the Task column shows HTML tags rather than the expected styled and readable subtask descriptions.
Impact: Users see unrendered HTML in subtask descriptions, which reduces readability and may cause confusion when reviewing or managing tasks and subtasks created via the Flow Path Factbox.
Created: August 4, 2026
Priority: Low
Flow Path Entry Is Not Marked as Critical When Containing Critical Tasks
Description: When a task or subtask within a Flow Path Entry is marked as Critical, the corresponding Flow Path Entry is not automatically marked as Critical as expected.
Impact: Users cannot reliably identify Critical Flow Path Entries based on their tasks, which may lead to missed prioritization of critical work and reduced visibility into high-risk or time-sensitive activities.
Created: August 5, 2026
Priority: Low
Task Is Created Without Corresponding Task Entry
Description: When a Flow Path User creates a task from the Flow Path Factbox on a Sales Invoice, the task is created but does not appear in the Tasks section of the Task Entry. The corresponding task record is missing, and the task cannot be opened or managed from this section.
Impact: Responsible users cannot access the required task actions from the Task Entry, preventing them from processing and completing the task through the standard workflow.
Created: August 5, 2026
Priority: Medium
Block Print Setting Does Not Prevent Printing When Critical Question Exists
Description: When Block Print is enabled in Module Setup and a critical Flow Path question remains unanswered for a document (for example, a posted sales invoice), printing is not blocked as indicated by the tooltip. Users can still print the document without any warning or restriction, despite the presence of unanswered critical questions.
Impact: This behavior allows documents to be printed before required critical questions are completed, potentially leading to incomplete or non-compliant documentation and reducing the effectiveness of the Block Print control.
Created: August 5, 2026
Priority: Medium
Tooltip for "Block Duplicate Entry Creation" Describes Opposite Behavior
Description: The “Block Duplicate Entry Creation” option in Flow Path Module Setup has inconsistent labeling. The caption indicates that duplicate entries will be blocked, while the tooltip states that it allows creation of entries that already exist. This contradiction makes it unclear whether the setting prevents or allows duplicate entries.
Impact: Flow Path Admins and end users may misconfigure the setting due to the conflicting caption and tooltip, leading to unintended allowance or blocking of duplicate entries and potential data integrity issues.
Created: August 5, 2026
Priority: Medium
Incorrect Catalog Filtering for Question and Reminder Types
Description: In the Catalog Creation Wizard (Checklist, Step 5), catalog type filtering does not work correctly for Question and Reminder catalogs. When Question is selected, both Question and Reminder catalogs are shown. When Reminder is selected, catalogs of all types (Information, Question, Task, and Reminder) are displayed. Filtering behaves as expected for Information and Task selections.
Impact: Users may see incorrect catalog lists when working with Question and Reminder types, which can lead to confusion, selection of unintended catalogs, and reduced efficiency when configuring or reviewing catalog content.
Created: August 6, 2026
Priority: Low
Ribbon Does Not Provide Access to Reminder Catalogs and Templates
Description: When opening Flow Path and selecting Catalogs & Templates in the ribbon, the options for Reminder Catalog and Reminder Template are not displayed. Only the existing Question, Information, and Task options are available, preventing users from working with reminder-related items through the ribbon.
Impact: Users are unable to create, access, or edit reminder catalogs and reminder templates from the Flow Path ribbon, which may disrupt workflows that rely on reminder configurations and maintenance.
Created: August 6, 2026
Priority: Low
Absent Users Can Be Assigned as Representatives for Each Other
Description: The system does not validate overlapping absences when assigning user representatives. It is currently possible to assign a representative who is already marked as absent for the same period, and no error message or warning is displayed to indicate that the selected representative is unavailable.
Impact: Two users can be configured as representatives for each other during overlapping absence periods. This can result in information, questions, or tasks being routed to absent representatives, potentially causing delays, missed communications, and incomplete task handling.
Created: August 6, 2026
Priority: Low
Created Subtasks Are Not Displayed Correctly
Description: When creating a Flow Path task with the SubTask option enabled from a Sales Invoice or other Flow Path-supported page, the main task is created successfully but the associated subtask is not displayed when the task is opened. Instead, multiple unrelated or default subtasks appear, and the subtask that was actually created for the selected main task is missing.
Impact: Users cannot reliably view or manage the correct subtasks associated with a main Flow Path task, which may lead to confusion, misassignment of work, and incomplete tracking of task-related activities.
Created: August 10, 2026
Priority: Low
Subtasks from a Previous Unrelated Task Are Displayed When Creating a New Task
Description: When creating a new Flow Path task entry from the Flow Path FactBox, previously created subtasks from an unrelated main task are pre-populated in the subtask table instead of starting empty. This occurs after enabling the SubTask option for a new task and results in the subtask list carrying over entries from earlier tasks.
Impact: Users may be confused by unrelated subtasks appearing in new tasks and must manually remove these entries to ensure that only subtasks relevant to the current main task are retained, increasing the risk of incorrect task-subtask associations and additional manual cleanup effort.
Created: August 10, 2026
Priority: Low