Workflow in Custom Applications


Return to Workflow Building Block Overview

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.

You can integrate workflow into any custom application with the necessary criteria, namely three dimensions to fulfill these respective roles: the Version dimension, the Time dimension, and the Workflow Step dimension.

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:

  • Inventory Actual  2019
  • Inventory Budget 2015
  • Inventory Forecast 3+9 2017-2018

Note: workflow tasks must be created in advance when workflow is used to collect data sets 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 Region may break down into the elements USA, Germany, France, 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.).

Key users can create and maintain workflow tasks with the Workflow Wizard, including assigning the activities to user groups, scheduling due dates, and setting up e-mail templates. Once an activity becomes active, e-mail notifications are sent to all end users within user groups.