Management of submission and notifications

Introduction

To manage the submission of the process, you need to define and/or customise the following rules:

• Analytical Workspace Checking rules
• submission rules of the specific process

On submission, CCH Tagetik checks the validation of the checking rules set for each step (see ). Thus, only the steps where the rule has been validated, or respected, are submitted.

For the submission of each process, the rules defined as general submission rules are applied. However, you can override these rules for a specific process.

For details on the submission data processing, see The processes cockpit.

To facilitate the management of submission activities, CCH Tagetik a notification system is also provided.

Operation of notifications

In order for notifications to operate correctly, the following information must be specified:

• email templates to be used for notifications
• due dates of the submission events and approval that triggers the sending of the notification
• scheduling automatic reminders for submission
• scheduling daily summaries of the submission status

To send notification emails, the rules defined as general are applied. However, you can override these rules for a specific process.

Sending configurable emails

For processes with dimension by step, the following email templates are provided:

• Entity submission: when an entity is submitted, an email is sent to the recipients in the template
• Entity Approval: when an entity is submitted and an approval task is defined, an email is sent to the recipients in the template
• Submitted entity rejection: when an entity is rejected, an email is sent to the recipients in the template

• Reminder Before Task Deadline: once a day, the submission or approval task managers receive an email for any tasks not completed.

• Completion: process task workflows: each time a submission or approval task is completed on a lowest level element, all managers of the subsequent tasks receive an email.

• Rejection of submitted elements: each time a certified element is rejected, all the task managers of the submission and approval of the lowest level element receive an email.

• Send Summary Email on Task Completion: once a day, for each lowest level element not yet submitted, all the managers of the subsequent task receive an email for each submission or approval task completed.

• Send Summary Email for Rejected Elements: once a day , for each lowest level rejected, all the task managers of the submission and approval of the lowest level element receive an email.

Note: A user is only considered to be 'responsible for the task' if he/she is explicitly restricted on the reference entity/task.

Examples of notification configuration

To send the email ...	Then...
once a day with tasks falling due	set Email event type = Reminder Before Task Deadline and activate the reminder email
when the submission task has been completed	set Email event type = Completion: Process task workflows
when an element is rejected	set Email event type = Reject Submitted Analytical Dimensions
once a day with the summary of completed tasks	set Email event type = Send Summary Email on Task Completion and activate the summary email
once a day with the summary of rejected lowest level elements	set Email event type = Send Summary Email for Rejected elements and activate the summary email

Deadline dates

You can set the following dates by business cycle, step and element:

• for operational tasks: the dates by which the task must be finished

• for submission tasks:

• the submission deadlines, namely the dates by which the lowest level element must be submitted

• send reminder email, namely the dates from which the reminder emails to submit an element are sent

Managers

Only for list steps.

It is possible to assign the managers of the task for each business cycle, step, element, and task. Task managers are those authorized to run tasks, mark them as completed, and revoke that status.