Process Definitions require a unique label within the application and an optional name.

Specify the Period Unit on which the Process based on the Process Definition will be repeated. In the above example of "Annual Budget Preparation," the execution cycle is "Year," while in "Monthly Consolidated Data Collection," the execution cycle is "Month."

Each Process Definition can include one or more Submission Package Definitions. Detailed explanation of Submission Package Definitions is provided below.

If this option is unchecked, the Finalizer unit of responsibility for the Process will use "Common Workspace/WORKSPACE" as their workspace without being assigned a workspace for each Process like other units of responsibility.

Generally, the Finalizer unit of responsibility is the main department for the task and updates a wide range of data. If a workspace is assigned to the Finalizer unit of responsibility for each Process, it is necessary to execute the Data Publishing Process to transfer that data to the shared workspace before publishing. However, defining submission packages for all data ranges that may be changed by the Finalizer unit of responsibility can be cumbersome.

Therefore, by providing this option and leaving it unchecked, the Finalizer unit of responsibility for the Process can use "Common Workspace/WORKSPACE" as their workspace, making the Data Publishing Process unnecessary.

Checking this option allows data to be written to the ledger as if all scenarios for all fiscal years and all relative periods are open, ignoring the Ledger Open/Close status during the reflection of Submission Package data (both Reception and Reflection).

⚠ This item was added in version 4.1. In versions before 4.0, the same processing as when this item is checked was always performed, so when transitioning an application created in a version before 4.0 to version 4.1, this item will be checked. Please also refer to Process Management Functions and Access Control.

Checking this option prevents the unit of responsibility that submitted the Submission Package from withdrawing it if it has been manually approved after submission (instead of withdrawal, the unit of responsibility currently holding the package should return it).

The basic characteristic of a Submission Package Definition is that each represents a unit of data submission.

If "Sales Budget" and "Expense Budget" are separate Submission Package Definitions, each department (unit of responsibility) participating in the Process can submit and approve the Sales Budget and Expense Budget as separate data at different times. On the other hand, if the Sales Budget and Expense Budget are combined into a single Submission Package Definition "Sales and Expense Budget," it is not possible to submit or approve them separately.

The main components of a Submission Package Definition are the specification of the Form List and the Submission Route Definition.

In addition to the above, the following items can be specified in the Submission Package Definition:

You can specify one or more dimension members as additional keys for each Submission Package.

The additional key mechanism is provided for using a single Form List in multiple Submission Package Definitions. For example, in sales planning tasks, if you want to prepare different Submission Package Definitions for each product group but the input screens are exactly the same except for the target product group, you can prepare a common Form List for all product groups, design each form to allow specifying the target product group parameter values, and then create Submission Package Definitions for each product group, applying the same Form List with different product groups specified as additional keys.

When entering or submitting data within a Process using the forms specified in the Submission Package Definition, parameter values (members of dimensions specified as parameters during form design) are automatically set. These are called "Parameter Values of the Submission Package." The source information for these settings, in order of priority, is as follows:

The parameters of each form used in the Submission Package Definition must be related to dimensions that can be set by any of the above 1 to 3.

In forms of the Main Form List, calculation results can be reflected in the ledger like regular forms (by specifying formulas in the cell specification and turning on "Reflect calculation results in ledger").

Unlike data entry in [Browser], when data is entered using forms on the workspace screen of [Contributor], not only are the calculation results of that form reflected in the ledger, but all calculations defined in the forms of the Main Form List are executed in sequence, and the results are reflected in the ledger. In addition to or instead of the Main Form List, you can also specify another Form List (Form List for server-side calculation processing).

The calculation results are also saved during the data check of the package^[2]. When data in the workspace is entered/changed via [Excel-Link], recalculation is not executed unlike during form entry, but pressing the check button allows recalculation.

The above automatic calculation processing is executed in the order of the forms in the Form List applied to the calculation process (i.e., in ascending order of form labels). When both the Main Form List and the Form List for server-side calculation processing are applied to the server-side calculation processing, the calculations of the former are executed first.

You need to consider the order of the forms and dependencies in the calculation process. For example, if forms A, B, and C are in that order, calculations in form B can use the results of form A, but calculations in form A should not use the results of form B. Similarly, form C can use the results of forms A and B, but forms A and B should not use the results of form C.

Even if these rules are violated, they are not checked during form design, but note that recalculation request messages may repeatedly appear during package submission, or submission may be impossible if calculations are circular.

During package submission, calculations in each form of the Form List applied to server-side calculation processing are executed in the order described above. It is determined whether saving calculation results is necessary. If necessary, submission is rejected. In this case, pressing the check button to execute recalculation will allow submission afterward.