Business Workflow Deployment

Operation

When deployment is executed only for the Entity dimension, if a significant workflow has been associated with a node in the entity hierarchy that is not significant in the data collection process, it is replaced by the empty system workflow ($$). The same thing happens to nodes that are not significant in the consolidation process in the entity hierarchy.

If a lowest level element and/or a node in a hierarchy are later moved and associated with a different task, the following results can occur:

If...	Then...
the modified element is in "submitted" or "pending submission/approval” status.	it is reset as "submitted".
the modified element is in the "in progress” status.	it is set as "not started".

Note: this behaviour applies to all scenarios/periods in the process, including those that are locked.

List steps

For each phase, workflow element/task e-nuples are automatically generated based on the mapping, to facilitate entering due dates and assigning managers.

If the task has defined working days and the step has a start date, the due date is automatically calculated by adding the working days to the start date.

If in the ‘Reminder and Summary Emails’ management window the option ‘Send submission memo starting from’ has been defined, the reminder start date is automatically calculated by subtracting the specified number of days from the due date, and the time is set according to what is defined in the window.