Workflow optimizes the collection of planning data by restricting report write access to certain time frames. End users can enter and modify planning data within workflow activities, but not outside of them. Key users thus control modification and ensure data integrity.
The workflow feature is implemented in multiple models. The major workflow principles apply to all models.
Workflow collects data sets, which appear as workflow tasks in the Workflow Administration report. Each workflow task is defined by its business process, version, and time frame (a single year, in most cases). Examples could be:
- Cost Center Mid-Term Planning 2017 – 2019
- Cost Center Budget 2017
- Cost Center Forecast 3+9 2016
Note: The tasks must be created in advance when the workflow is used to collect data packages for specific versions or years.
Workflow tasks are broken down further by the workflow step dimension and workflow activities. The workflow step dimension breaks down workflow tasks into elements. The step dimension
Cost Center may break down into the elements
Support, for example. You can use any dimension you like, and there are no restrictions to names. The aggregation weight in the workflow step dimension, however, must be 1. Parts of the workflow will not work with other weights (such as 0 or -1). Workflow activities mark the progression through various workflow stages (data entry, review, revise, etc.).
Within the workflow task, administrators can schedule when particular workflow activities should be completed with the Workflow Task report. They can determine which user groups are assigned to execute said activity within the Workflow Assignment report. Once an activity becomes active, e-mail notifications are sent to the users in groups assigned to the activity. E-mail notifications are editable within the E-Mail Notification report.