Business Objects and Role Permissions

1. Objects Accessible to Terminal Users

• Navigation: Service Connector -> System Settings -> Full Feature Config -> Terminal User Service Connector -> Business Objects

picture coming soon:

• Terminal Service Connector -> Business Objects lists the business objects terminal users are allowed to submit or query (use together with Terminal User Interconnection Role permissions).
• Object settings: The system predefines a set of business objects that are exposed to terminal users. Deleting these is not recommended. Click [Add Object] to expose more visible objects.

picture coming soon:

• You must configure which Record Types, page layouts, and data permissions are visible to external terminal user Roles for each business object.
• Record Type: The Record Types that terminal users can use for an object. We recommend exposing only one Record Type to simplify terminal user operations.

picture coming soon:

• Assigned Layouts: The page layouts of an object visible to terminal users.

picture coming soon:

2. Terminal User Role Permissions

Function permissions are based on Interconnection Roles. By assigning different permissions to Roles and adding terminal users to those Roles, you isolate and distinguish terminal user capabilities. Permissions include:

• Object-level permissions: Controls whether an object’s entry point is visible. For example, if the Interconnection Role “Individual User” has the Device object’s “View List” permission revoked, terminal users in that Role will not see the Device entry point.
• Action permissions: Permissions for operations such as Create, Edit, etc.

• Field permissions: Configure field-level Read/Write, Read-Only, or Hidden for an Interconnection Role. For example, you can set the Work Order Note field to Hidden for the Interconnection Role “Terminal User.”

• ShareCRM Service comes with predefined Roles for terminal users. For more Interconnection Role configuration guidance, see: https://help.fxiaoke.com/2615/ebc1/d910/7562

• You can assign object permissions, action permissions, and field permissions to terminal users.

  • Object entry permission: “View List” serves as the object entry permission for an Interconnection application.
  • Object detail permission: “View Details” controls access to an object’s detail page. Without this permission, terminal users cannot view Work Order details.
  • Action permissions: Granting action permissions is the prerequisite for terminal users to operate on business data. If you remove “Create”, “Edit”, or “Import” permissions, those actions will not appear on list or detail pages.

picture coming soon:

Note: Also confirm that specific action buttons are visible in the list/detail layouts. Verify that the layouts assigned to external Roles expose the required buttons, as shown below.

picture coming soon: