The features described will be available in the d.velop Cloud in fall 2025. They are part of Current Q4/2025, which will be released in December.

Resubmission of tasks for later processing

In task management, it is now possible to reschedule tasks so that they can be processed later. When you open a task, a calendar icon is displayed in the task toolbar. You can use the button to schedule a task for later processing.

After clicking on the Edit later button, a dialog box opens in which you can specify the new delivery date for the task. In the dialog box, you can also specify whether you would like to be notified again by email when the task is redelivered.

Once a task has been scheduled for later processing, it will no longer be displayed under My Tasks but under My planned tasks. This allows you to continue accessing the task even though it has been scheduled for later processing.

In the overview of planned tasks, the delivery date of the tasks is displayed in the Delivery column.

A scheduled task cannot be processed until it is delivered. If you want to process the task in advance, you can use the DELIVER NOW button to return the task to the list of tasks to be processed. You can also adjust the delivery date later.

Actions related to postponing tasks are logged in the task history and can be viewed there in detail.

Restricting recipient groups for tasks

Within task management, all groups in the cloud environment are offered as possible task recipients. It is possible that some groups from the identity provider are only used for authorization controls, for example, but should not be offered as task recipients. For this reason, so-called group types, such as Security, Distribution, or Authorization, which are familiar from LDAP, have been provided for some time now as part of group management.

A group type can now be configured in task management to restrict the selectable recipient groups.

You can select a group type under Restrict user lists in the configuration. After saving the configuration, only the selected groups will be offered as possible task recipients.

If no group type is configured, all groups in the environment will continue to be offered as possible task recipients.

Use technical user accounts as service users

You can specify a technical user account group in the user account provider details of a system environment. User accounts that are members of this group are considered purely technical user accounts and cannot, for example, log on directly to the environment via the interface. Such user accounts are usually used as service users for API connections, for example.

You can now also select these technical user accounts when configuring technical roles within task management. This allows you to enable API access for these user accounts.