Running a submission and rejection (with Entity dimension)

Introduction

Submissions and rejections can be run from various points, depending on the role of the user running them (contributor or consolidator), the object on which action is being taken (entity or journal), and the desired result.

Submission and rejection of entities and nodes.

Only submission/rejection of entities and contributor nodes can be managed from the contributor cockpit, while the submission/rejection of consolidator nodes can also be managed from the consolidator cockpit.

There are two run modes:

• from the detail summary. In this case, a specific window is opened where the user can customise the run filters
• from the step tab. In this case, the value of the parameters required for the submission is set automatically and the process is run directly. For a rejection, a window is opened where you can specify any notes and reasons for the rejection

Journal submission and rejection.

Journal submission/rejection is run from the journal data entry by entity and consolidation journals.

Action	Description
Submit the selected journals	Opens a window where you must specify a journal submission step, and run the submission of the selected journals.
Submit the selected journal via workflow	View the journal workflow, where you can individually run the submission task and any approval tasks.
Submit all automatic journals	Opens a window where you must specify an original scenario/period (among those active, not blocked and not stored offline, connected with the selected process and visible for the user), and a journal submission step. Runs the submission of all the automatic journals, or those for which rows with manual origin are not present (INPUT_WEB, INPUT_DEFORM, BREAK_BACK, QDL or MAP_%).
Reject the selected journals	Opens a window where you must specify a journal submission step, and run the rejection of the selected journals.