Submission Route Definition
This manual is in pilot operation.
|
Submission route definition refers to the path through which submission target data (submission packages) are submitted and circulated within a business process. The submission route definition can be viewed as a tree of participants. That is, starting from the terminal participants tasked with submitting packages, through intermediate units responsible for compilation/approval, up to the unit at the top responsible for final approval.
Except for the terminal units, all participants are, in principle, required to approve the submission packages submitted by the terminal units. However, by specifying during the submission route registration, approval can be automated (accept/approve submission data as soon as it arrives).
The tree hierarchy can have any number of levels, and it’s fine for parts of the tree to have different depths (number of levels from the terminal to the final approval unit). Also, it’s not necessary to include all participants in the submission route. For example, while all departments may be included in the expense budget submission route, only the sales departments may be included in the sales budget submission route.
Multiple submission route definitions can be set up within an application.
Components of Submission Route Definition
A submission route definition includes the following components (configuration items):
Label and Name
A submission route definition must have a unique label within the application and an arbitrary name.
Responsibility Splitting Criterion Dimension
Specifies the dimension along which the data submission responsibilities of the participants included in this submission route definition are divided.
For example, if the expense budget is created by department, then there exists a department dimension, which becomes the "Responsibility Splitting Dimension" for the expense budget submission route. For participants included in the route, one member of the route’s responsibility splitting dimension must be specified as the "Responsibility Scope Key." Whether the specification has been made is checked not at the time of registration/modification of the participant or submission route definition but at the time of new business process generation, so please be cautious.
Auto-Receipt/Approval Method (fusion_place >= 17.0)
Determines how the automatic receipt and approval methods are specified for this submission route definition. Choose from the following three values:
-
Using single attribute: Automatic receipt and automatic approval are specified together (specifying automatic approval also implies automatic receipt is specified).
-
Using individual attribute: Automatic receipt and automatic approval are specified independently.
-
Forcing auto-receipt: Automatic receipt is always performed; automatic approval may optionally be specified.
Of the above, "Using single attribute" is compatible with the older specification. When migrating to the version in which this feature is applied (17.0), the "Auto-Receipt/Approval Method" for existing submission route definitions will be set to "Using single attribute."
Depending on the specification of this item, whether "Auto-receipt" and "Auto-approval" can be edited for each participant in the route details changes as follows.
| Auto-Receipt/Approval Method | Auto-receipt | Auto-approval |
|---|---|---|
Using single attribute |
Not editable (takes the same value as Auto-approval) |
Editable |
Using individual attribute |
Editable |
Editable |
Forcing auto-receipt |
Not editable (always ON) |
Editable |
Based on the values of "Auto-receipt" and "Auto-approval" in this table, automatic receipt and automatic approval are performed at the time of submission and so on:
-
If only Auto-receipt is ON, receipt is performed automatically when the submission package arrives at the participant, and the submission package stays at that participant without being approved.
-
If only Auto-approval is ON, receipt is not performed automatically when the submission package arrives at the participant. When it is received manually, it is regarded as approved as well, and the submission package is sent to the next participant on the submission route.
-
If both are ON, receipt and approval are performed automatically when the submission package arrives at the participant, and the submission package is sent to the next participant on the submission route.
Contents of the Submission Route
As mentioned above, the submission route is a tree structure of participants. You can select which participants to include in the tree and specify the participants that are next in line on the route. In relation to the submission route, the following terms may be used:
- Submitter
-
The terminal participant in the tree. It bears the responsibility of submitting the type of submission package represented by the submission package definition to which the submission route definition applies.
- Submission Path
-
The branch from the submitter to the top of the tree.
- Recipient
-
A participant on the submission path starting from a submitter, excluding the submitter itself.
- Final Recipient
-
The last participant on the submission path (i.e., the top of the tree).
Although the submission route appears similar to a member tree in a dimension, it can be set up differently from a member tree.
Proxy Submission
While the basic principle is that the participants at the end of the submission route submit the submission packages and the recipient participants approve these packages, it’s possible to grant authority to any recipient to submit on behalf of its subordinate submitters. To do this, check the submission route item "Can Submit on Behalf of Submitter" in the submission route section.
When a participant two or more levels above the submitter on the submission route submits on behalf of the submitter, the approval of the recipients between the submitter and that participant is "skipped".
