Support recurring plans and tasks including Data Scope updates

Dear team,
Summary

Plans and tasks that repeat every month, quarter or other defined period currently have to be duplicated and adjusted manually. There is no built-in mechanism to define a plan or task as recurring and automatically create the next cycle, including the corresponding Data Scope.

Current situation

Typical planning processes such as month-end close, forecasting or budgeting are recurring by nature and often follow the same workflow structure in every cycle.

For example, a monthly process may contain several tasks such as input, review and approval. While the workflow structure remains largely unchanged, the relevant dates and Data Scope need to move to the new period.

Today, users have to duplicate the tasks or plan, manually adjust dates and Data Scope, verify assignments and dependencies, and activate the new cycle again.

This creates significant administrative effort and introduces the risk of configuration errors between planning cycles.

Workspace REST API coverage for Plans is also not currently available, so this process cannot be reliably automated externally from TM1.

Requested enhancement

Support recurring / periodic plans and tasks so that a defined workflow structure can be reused automatically for subsequent planning cycles.

Users should be able to:

• define a plan or task as recurring, for example monthly, quarterly or based on another defined interval

• define the recurrence period and, where applicable, an end date or number of occurrences

• automatically create the next cycle based on the existing plan/task definition

• automatically roll dates and Data Scope to the corresponding next period

• retain assignments, assets, dependencies and workflow-process configuration

• retain the overall task and plan structure without requiring manual recreation

• optionally create the next cycle on demand rather than automatically

• review and adjust the generated cycle before activation, where required

The recurrence mechanism should distinguish between the static workflow definition and the period-dependent elements such as dates and Data Scope.

Business benefit

Many planning processes are inherently periodic. Supporting recurring plans would remove a significant amount of recurring plan administration in live customer environments and reduce the risk of inconsistencies between planning cycles.

It would make Plans more suitable as an operational planning calendar, rather than primarily as a one-off workflow definition.

This is particularly relevant for monthly close, rolling forecasts, quarterly forecasts and other recurring planning processes.

Expected result

A plan owner or co-owner can define a plan as recurring and create the next planning cycle with a single action.

The new cycle inherits the existing workflow structure, assignments, assets, dependencies and configuration, while dates and Data Scope are automatically updated for the new period.

Users no longer need to manually duplicate and reconfigure every task for each planning cycle.

Out of scope

This request does not define the REST API implementation.

An API that provides the same recurring-plan or next-cycle functionality programmatically, for example from TM1, would be complementary to this enhancement.

With best regards,
Vitalij