In T7930#215278, @isfs wrote:

Something that would be useful to us would be the ability to create, or probably better, assign a task, as it nears a due date. E.g. we may set up a task due in a year's time, and anticipate working on it two months before it is due. It would be great to be able to schedule the task to be assigned on a particular date, and perhaps moved on a workboard. I don't think this would need to be any more complicated than a Herald action that runs at a particular date/time rather than in response to some other action. I'm not familiar with what Calendar can already do, as we don't have prototype applications turned on for our install, so apologies if this is already possible. I just thought I would mention this use case here for future reference.

The recurring and due date use cases in the previous comment would also be useful to us. I would prefer something more natural for the formulation, though, e.g. for tasks:

• when [Father Time] [reaches] value in [Due Date] (or other selected field), [Assign to] [ben].
• when [Father Time] [is one week before] value in [Due Date] AND [Status] is [any open status], [Set priority] to [High].
• when [Father Time] is [one month after] value in [Creation Date] AND [Status] is [any open status], [Send email notification] to [manager].

It would be great if task Due Dates (or other date fields, conceivably creation date could also be useful) could (optionally) appear on a calendar.

I'm going to merge this into T11357. We can provide a "Delete File Data" transaction type when we implement a third-generation file.edit API.

Wow, thanks for your fast and precise answers!! Using the file