The approval flow configuration information defines the approval flows used when addition, modification, or deletion of resource information of Cloud Services Management is requested. Configure each approval flow based on the type of resources to be added such as organization information, projects, platforms, etc. In addition, depending on the target resource, configure an approval flow based on the department to which the user who operates that resource belongs.
The file name and storage location are as follows: It is necessary to restart the services to reflect any modifications.
When a key is not configured for a definition file, or when a value that cannot be specified is specified, the default value is used to define the approval flow.
request_flow.xml
%FSCSM_HOME%\conf
Item | Description |
|---|---|
menu.approval-Planners | Specify the approval flow necessary for performing addition, modification, or deletion of menus. Specify one of the following values: manager_approval: Requires the approval of Planners - Approver no_approval: Approval is unnecessary Default: manager_approval For details on the approval flows, refer to "Figure 4.5 The Menu Approval Process" in the "FUJITSU Software Cloud Services Management User's Guide for Planner and Operator". Route 1 in the figure is the flow used when "manager_approval" is specified and Route 2 in the figure is the flow used when "no_approval" is specified. |
org.approval-Operators | Specify the approval flow necessary when performing addition, modification, or deletion of organizations. Specify one of the following values: manager_approval: Requires the approval of Operators - Approver no_approval: Approval is unnecessary Default: manager_approval For details on the approval flows, refer to "Figure 2.2 The Organization Information Approval Process" in the "FUJITSU Software Cloud Services Management User's Guide for Planner and Operator". Route 1 in the figure is the flow used when "manager_approval" is specified and Route 2 in the figure is the flow used when "no_approval" is specified. |
user.approval-Operators.applicant-Operators | Specify the approval flow necessary when operators perform addition, modification, or deletion of users. Specify one of the following values: manager_approval: Requires the approval of Operators - Approver no_approval: Approval is unnecessary Default: manager_approval For details on the approval flows, refer to "Figure 2.3 The User Information Approval Flow (for Operators)" in the "FUJITSU Software Cloud Services Management User's Guide for Planner and Operator". Route 1 in the figure is the flow used when "manager_approval" is specified and Route 2 in the figure is the flow used when "no_approval" is specified. |
user.approval-Operators.applicant-PlannersProviders | Specify the approval flow performed by operators which is necessary when planners or platform providers perform addition, modification, or deletion of users. Specify one of the following values: full_approval: Requires approvals of Operators - Representative and then Operators - Approver. single_approval: Requires the approval of either Operators - Representative or Operators - Approver no_approval: Approval is unnecessary Default: full_approval For details on the approval flows, refer to "Figure 2.4 The User Information Approval Flow (for Planners - Representative)" and "Figure 2.5 The User Information Approval Flow (for Planners - Approver)" in the "FUJITSU Software Cloud Services Management User's Guide for Planner and Operator". Or refer to "Figure 2.3 The User Information Approval Flow (for Platform Providers - Representative)" and "Figure 2.4 The User Information Approval Flow (for Platform Providers - Approver)" in the "FUJITSU Software Cloud Services Management User's Guide for Platform Provider". Route 1, Route 2, and Route 3 for [Operators] in the figure are the flows when "full_approval", "single_approval", and "no_approval" are selected, respectively. |
user.approval-PlannersProviders | Planners or platform providers specify the approval flow performed within their own department which is necessary when performing addition, modification, or deletion of users. Specify one of the following values: manager_approval: Requires the approval of an approver belonging to the same department/organization as the requester no_approval: Approval is unnecessary Default: manager_approval For details on the approval flows, refer to "Figure 2.4 The User Information Approval Flow (for Planners - Representative)" in the "FUJITSU Software Cloud Services Management User's Guide for Planner and Operator". Or refer to "Figure 2.3 The User Information Approval Flow (for Platform Providers - Representative)" in the "FUJITSU Software Cloud Services Management User's Guide for Platform Provider". Route 1 in the figure is the flow used when "manager_approval" is specified and Route 2 in the figure is the flow used when "no_approval" is specified. |
platform.approval-Operators | Specify the approval flow performed by operators which is necessary when performing addition, modification, or deletion of platforms. Specify one of the following values: full_approval: Requires approvals of Operators - Representative and then Operators - Approver. single_approval: Requires the approval of either Operators - Representative or Operators - Approver no_approval: Approval is unnecessary Default: full_approval For details on the approval flows, refer to "Figure 4.7 The Platform Approval Flow (for Project Users, with the Level Specified)", "Figure 4.8 The Platform Approval Flow (for Project Managers, with the Level Specified)", and "Figure 4.9 The Platform Approval Process (Approval is Unnecessary)" in the "FUJITSU Software Cloud Services Management User's Guide for Platform Provider". Route 1, Route 2, and Route 3 for [Operators] in the figure are the flows when "full_approval", "single_approval", and "no_approval" are selected, respectively. |
service.approval-Operators | Specify the approval flow performed by operators which is necessary when performing addition, modification, or deletion of services. Specify one of the following values: full_approval: Requires approvals of Operators - Representative and then Operators - Approver. single_approval: Requires the approval of either Operators - Representative or Operators - Approver no_approval: Approval is unnecessary Default: full_approval For details on the approval flows, refer to "Figure 4.13 The Service Approval Flow (for Project Users, with the Level Specified)", "Figure 4.14 The Service Approval Flow (for Project Managers, with the Level Specified)", and "Figure 4.15 The Service Approval Flow (Approval is Unnecessary)" in the "FUJITSU Software Cloud Services Management User's Guide for Platform Provider". Route 1, Route 2, and Route 3 for [Operators] in the figure are the flows when "full_approval", "single_approval", and "no_approval" are selected, respectively. |
project.approval-Operators | Specify the approval flow performed by operators, which is necessary when performing addition, modification, or deletion of projects (but not for member operations). Specify one of the following values: full_approval: Requires approvals of Operators - Representative and then Operators - Approver. single_approval: Requires the approval of either Operators - Representative or Operators - Approver no_approval: Approval is unnecessary Default: full_approval For details on the approval flows, refer to "Figure 3.5 The Project Addition Approval Flow" and "Figure 3.5 Approval Process of Addition, Modification, and Deletion of a Project" in the "FUJITSU Software Cloud Services Management User's Guide for Platform Provider". Route 1, Route 2, and Route 3 for [Operators] in the figure are the flows when "full_approval", "single_approval", and "no_approval" are selected, respectively. |
project-member.approval | Specify the approval flow performed by operators, which is necessary when a project user performs addition, modification, or deletion of projects. Specify one of the following values: manager_approval: Requires the approval of a project manager no_approval: Approval is unnecessary Default: manager_approval For details on the approval flows, refer to "Figure 3.6 The Project Member Addition and Deletion Approval Flow (Project User)" in the "FUJITSU Software Cloud Services Management User's Guide for Platform Provider". Route 1 in the figure is the flow used when "manager_approval" is specified and Route 2 in the figure is the flow used when "no_approval" is specified. |
project.auth.level | Specify a hierarchy level of the approval flow within the organization, which is necessary when performing addition, modification, or deletion (excluding member operations) of projects. Specify 1 for the organization at the top level of the hierarchy, 2 for its sub-organization, or 3 for an organization in the sub-organization. For this reason, when 1 is specified, the approval of each hierarchy level, in ascending order, of the organization to which the user who performed the operation belongs is required. The value must be an integer between 1 and 7 and equal to or smaller than the value of org.depth.max that is defined in "2.10.1 System Information". If no approvals are necessary within the organization, specify "no_approval". Default: 1 For details on the approval flows, refer to "Figure 3.5 The Project Addition Approval Flow" and "Figure 3.5 Approval Process of Addition, Modification, and Deletion of a Project" in the "FUJITSU Software Cloud Services Management User's Guide for Platform Provider". Route 1 in the figure is the flow used when a hierarchy level is specified and Route 2 in the figure is the flow used when "no_approval" is specified. |
Note
When approval flow configuration information is modified, processes under request are processed with the previous configuration settings.
Information
Approval settings within the organization in an approval flow for platforms and services are not configured in approval flow configuration information.
Approval settings change depending on the value of the approval level specified using the menu selected when a platform is added.
The following settings eliminate the necessity of approval processes for platforms or services.
platform.approval-Operators:no_approval
service.approval-Operators:no_approval
It is not necessary to set an approval level for menus.
By combining these settings with the limit management function, it is possible to enable platform providers to operate services within the limits for usage charges.
