Process cockpit

Introduction

The process cockpit shows the progress of the submission for each step visible to the user. For processes with cycles by scenario/period, you can select the scenario/period of interest. If the scenario/period is locked and not stored offline, or if the process has a "Single" number of cycles and all the scenarios/periods are locked and not stored offline, the cockpit opens in read-only. The only activity you can carry out is opening forms. You cannot consult archived processes.

On initial access, the cockpit opens on the root of the hierarchy of the first step and the tree is expanded to the first level.

Submission and approval mechanisms

You can work on tasks irrespective of their order, but you cannot declare a task complete unless the previous mandatory tasks have also been declared complete. You cannot submit a step until all the mandatory tasks have been completed. In order for a node to be submitted, all of its children must first be submitted (lowest level elements and nodes relevant for the process).

Note: once an element has been submitted and/or approved, the declaration of task completed cannot be removed and single tasks can no longer be run. However, you can still open forms. If the element has been submitted and/or approved, the form is read-only.

The submission data processing locks the data collected or calculated for individual elements, both lowest level elements and nodes. These data can no longer be modified.

An element may be submitted only by the managers of the element, called submission users. Submission is carried out only on the original scenarios/periods of the process that the user has the right to edit.

During the submission processing, CCH Tagetik verify that any checking rules for submission have been satisfied. If they haven't, the submission will not be carried out, and an error message will be displayed with the details of the invalid rule.

If the step requires approval tasks following submission, the data are locked after the submission, but the submission is not considered complete until the approval tasks are also completed. If provided for, after submission, users that have to carry out approval receive a notification email. See Send email events.

Note: the users running the approval tasks must be different from those running the submission tasks.

If the steps of the process are sequential, the submission checks are run based on the Business Workflow settings (Configure Step window).

Specific characteristics of submission of steps by Entity

For steps by Entity, if the diagnostic validation rules have not been defined in the process, the execution of those rules may generate blocking errors at the time of submission. In these cases, the elements are not submitted.

The element is also submitted in the presence of blocking errors, but only if both of the following conditions occur:

• In the process submission rules, the “Override submission - Per user” option is active.
• Users carrying out the submission have the “Submit even with blocking errors” option active in their user rights.

Rejection of process steps

The action of rejection removes the submission previously run and, for example, allows you to modify the data entered or calculated for an individual element. This is possible only on the original scenarios/periods of the process that the user has the right to edit.

It can be run on a single lowest level element or on an entire node. To reject a lowest level element, the node that contains it has to have been rejected. In turn, to reject a node, its parent node, if any, has to have been rejected.

IMPORTANTonly for steps with "Entity" dimension : the rejection can only be run by the submission users of the lowest level element to reject and by those of the related parent nodes. Instead, if a node is to be rejected, only submission users of the node and those of the related parent nodes can reject it. If a task workflow to approve after the submission task is related to the element and some tasks have not yet been approved, the managers of those tasks can also reject it.

If the steps of the process are sequential, the rejection checks are run based on the Business Workflow settings (Configure Step Window).

If, in the process submission rules, the Mandatory reason option is active, to reject an element you must indicate the reason for rejection ().