Diagnostic of authorised blocking errors

Prerequisites

This check can be run only if the management of the diagnostic log with authorization of errors is enabled on the process being diagnosed. That is, if the following conditions are met:

• in the process validation rules, the Enable error tracing detected field is different from Do not handle,
• the With authorization of blocking errors option is enabled in the process submission rules

Check description

When the diagnostic checks detect blocking errors, such errors can be authorized by the users responsible for the parent entity of the entity on which the error is detected, namely the same users who can reject the entity.

The authorised blocking error diagnostic checks, for each entity being diagnosed, whether there are any authorised blocking errors on the child entities and if present, it reports an error on that entity . The error will progressively move up the hierarchy, requiring at each step the authorisation of the manager of the parent entity of the entity it is aggregated into.

If...	Then...
the diagnostic check is performed on an entity	its children can only be entity journals, provided that, in the process certification rules, the User enabled for journals rejection information is equal to User of the entity to which the journal belongs.
diagnostic check is performed on a contributor node	its children may be: - entities - contributor nodes - Entity journals belonging to the Child entities of the node, if User enabled for the journals rejection is equal to User on the parent node of the entity to which the journal belongs in the submission rules of the process
diagnostic check is performed on a consolidator node	its children may be: - entities - contributor nodes - consolidator nodes - Entity or Consolidation journals belonging to the node itself, if User enabled for the journals rejection is equal to User on the entity to which the journal belongs in the submission rules of the process - Entity or Consolidation journals belonging to the child consolidator nodes of the node if , in the submission rules of the process, User enabled for the journals rejection is equal to User on the parent node of the entity to which the journal belongs - Entity journals belonging to the Child entities of the node, if User enabled for the journals rejection is equal to User on the parent node of the entity to which the journal belongs in the submission rules of the process

The check is only performed on the original scenarios and reports any unbalanced amounts on the same step on which the errors were authorised.

In the case of consolidator node diagnostic, if the errors of the child entities have been authorized on contributor steps, then the report is done on the first consolidator step or hybrid step after the contributor step.

Validation and diagnostic rules

The following attributes are relevant for the execution of the diagnostic data processing:

Attribute	Description
Validation
Don't propagate the authorized blocking error information	The diagnostic of authorised blocking errors is only performed on processes with a setting other than Do Not Run (See Validation Rules Page)

The check is based on the following logic:

If...	Then...
Don't propagate the authorized blocking error information = Do not run	The check is not run.
Don't propagate the authorized blocking error information = Blocking	the check is performed and the presence of authorised blocking errors is reported with Blocking severity.
Don't propagate the authorized blocking error information = Non-Blocking	the check is performed and the presence of authorised blocking errors is reported with Non-Blocking severity.
Don't propagate the authorized blocking error information = Only Diagnostic	the check is only run if explicitly requested by manually running the diagnostic from the Detail summary (for the contributor) or Overview (for the consolidator) cockpit tabs; in this case it is possible to customise the filters before running the data processing. However, whenever diagnostics are run automatically (from the cockpit/from other data processing), the check is not performed.