• Added a new "After Task" trigger that runs a task after a selected task has finished. The trigger can be configured to run always or only after successful completion of the task.
• Added Groups to the Task Planner for powerful organization of tasks. Any task can optionally be added to a group, and group visibilities can be turned on and off in the task list on the left. Groups can be folded and unfolded.
• Added a component search when adding a trigger, series, job, or action to a task. Simply start typing the name of a component to filter down the available components.

Fixed Bugs

• If there were validation warnings in a task component and the view was scrolled down, the warning messages were hidden above the visible content.

• Importing tasks without a name using the WebAPI generates a custom name for these tasks.
• Saving a file with the "Save File" action will no longer save the file with a doubled file extension such as ".pdf.pdf" in case the extension was entered as the file name.
• Email addresses for the Email action now allow placeholders from jobs (such as "{Email}") without giving validation messages that the addresses is not valid.
• Tasks can now be created and marked as "system tasks" which means they are not owned by a specific user and can only be seen and edited by users with configuration and task planner administration privileges. When these tasks run, they run with full privileges.
• The Task Planner action "Email" now allows for rich text entry for the editing step.
• Enable Server Maintenance Mode to stop all internal operations before performing a backup or shutdown. This mode cannot be disabled within the application and requires restarting the server.

Fixed Bugs

• When updating the server to a new version, some result actions would have their conditional execution setting be reset.

• The Email Result Action allows for adding CC and BCC email addresses.

• The file change trigger supports now the integration of other sources, such as the Drive plugin.
• The Next Task trigger provides the option to pass any placeholders from the current task on to the next task along with a prefix which can be prepended to the placeholder key names.
• Tasks in the list can now be filtered down by their name - quickly find your tasks this way.
• When deactivating users who have tasks, a notification will be generated for administrators in the notification group "Task Planner Warning (Admin)".
• Result actions can be moved forwards and backwards in the result action order with the options "Execute earlier/later". This is helpful for cases in which the order of these actions matters.
• The e-mail action has an optional setting for the sender.
• With the Hosting plugin installed, tasks of the Master user account are not visible to other users anymore.
• When in maintenance mode, any triggered tasks are paused, queued, and run once the maintenance mode is deactivated.
• With the Hosting plugin installed, tasks of the Master user account are not visible to other users anymore.
• The task information contains an additional field status if it is retrieved via the WebAPI.

Fixed Bugs

• When deactivating users who have tasks, the generated notification for administrators could not be removed.
• The documentation for the Task Planner Action page was accidentally missing.

Security Fixes

• Additional verification of user permissions before accessing target location during execution of Task Planner's action "Save File"

• The file system action has been converted into a completely new "Save file" action, which now supports the integration of other sources, such as the Drive plugin.
• The Move Ownership page in Maintenance now supports resetting the chosen settings on the page.

Fixed Bugs

• In rare cases, the server could hang during setup when there were many different complex tasks.

• Adds the {initiator} placeholder to the server stop trigger, which contains the display name of the user who restarted the server.
• Tasks executed using the /api/taskplanner/execute endpoint are temporarily stored for the user, allowing them to access them later. If the tasks are not accessed again via the WebAPI within 60 seconds, they will be automatically removed.

Fixed Bugs

• In the task planner maintenance section, it was not possible to move tasks away from deactivated users.

• The parallel execution of one and the same task is now in general allowed
• Manually starting a task while it is running is now possible
• PUBLIC-API: To distinguish between multiple executions the TaskEvent and HistoryEntry now contains executionID, a unique ID for the execution.
• PUBLIC-API: TaskPlanner's execute-method now return a CompletableFuture to allow more control over actions after the execution.
• PUBLIC-API: New method cancelTaskExecution(GUID,GUID,boolean) to cancel a single running execution of a task instead of all running executions.
• Added Low Memory Trigger to notify administrators of this critical situation.
• PUBLIC-API: TimeTriggerFactory's generic type is now Trigger as it can return different types of trigger: TimeTrigger and TimeTriggerForCustomSettings

Fixed Bugs

• Fixed loading of large lists of tasks in the UI
• Fixed bug endlessly showing task as running with 0% or 100% progress although there was no execution.
• The license check of the Reporting Plus license for the Task Planning application was incorrect.
• The option custom in time triggers works correctly.

• Placeholders are grouped if they start with the same prefix
• Added the option custom in time triggers.
• A maintenance module is provided for batch moving Task Planner tasks from one user to another.

Fixed Bugs

• Fixed visibility of Task Planner triggers, jobs, and actions (based on a user's permissions) to be in sync with the visibility of help sections for these triggers, jobs, and actions.

Fixed Bugs

• Long running tasks were sometimes displayed as 'INCOMPLETE'
• Correction of identical file names in the file actions for multiple identical jobs with parameter placeholders in one task.

• New Task Planner Job added to determine the free disk space in the working directory, cache and persistence directories. A threshold for minimum available disk space can be defined to trigger actions when there is not enough disk space left

Fixed Bugs

• Triggering of time-trigger interval 'Two Weeks' was in wrong week at the beginning of a new year.