« Inside the Application   |   Labels and Names »

Designing and Managing Applications

Designer Administrator
This manual is in pilot operation.

Design Objects and Management Objects

To facilitate the construction of applications that meet the diverse needs of each enterprise, fusion_place provides a variety of configuration information. While these settings are necessary to flexibly meet user needs, having to understand all of them during application operation could significantly complicate operations.

To prevent such situations, fusion_place classifies configuration information (objects) into "Design Objects" and "Management Objects".

Type of Configuration Information Description

Design Objects

Configuration information required for building an application. Necessary during initial setup or when system requirements change, but not during regular operations.

[Manager] under the "Design" tab can be accessed.

Management Objects

Configuration information expected to be added, changed, or deleted as part of regular business operations.

[Manager] under the "Maintenance" tab can be accessed.

While there are more types of Design Objects than Management Objects, regular operation users do not need to handle Design Objects. This classification ensures that regular operations do not require extra effort unnecessarily.

Examples of Design Objects include:

Examples of Management Objects include:

User Roles

According to the classification of configuration information mentioned above, the roles of users registering or modifying configuration information are also divided into Designers and Administrators.

Designer

Has the authority to add, change, and delete both Design Objects and Management Objects.

Administrator

Has the authority to only add, change, and delete Management Objects.

Designer authority encompasses Administrator authority. By only granting Administrator authority to users involved in management, it is possible to avoid the risk of inadvertently modifying Design Objects.

In addition to registering or modifying configuration information, Designers and Administrators also have the authority to perform various administrative processes. Specifically, the following processes are included (these can be executed from the [Manager] under the "Execution" tab):

Users other than Designers and Administrators are called "Operational Staff" or "General Users".

  • Operational Staff …​ Has authority to engage in (design, management aside) regular business operations focused on data input and output.

Related Document: User Accounts and Permissions

Application-Specific Design and Management Authority

By specifying Designers and Administrators as "Application-Specific" (granting additional permissions), it is possible to limit the applications that a user can design and manage. Which applications a user can actually design and manage is specified in the application’s "Design and Management Authority Table".

The Design and Management Authority Table is set for each application and registers the following information:

  • Responsible User …​ The target user permitted to design and manage that application.

  • Presence of Design Authority …​ Specifies whether to grant the "Responsible User" design authority, in addition to management authority.

However, the permissions granted to a user account take precedence over the entries in the Design and Management Authority Table. This means:

  • If a user is not a Designer or Administrator, they will not be granted design or management authority, even if registered in the Design and Management Authority Table.

  • If a user is not a Designer, they will not be granted design authority, even if the Design and Management Authority Table specifies they have it.

  • If a user is a Designer or Administrator without "Application-Specific" limitation, they can design or manage any application regardless of the entries in the Design and Management Limitation Table.

Only Administrators with user management authority can modify the Design and Management Authority Table.