Configuration Layout Rules

1. Definition of Layout Rules

• Use layout rules to make fields change (show, hide, require, etc.) when certain conditions are met or when records are created/edited.
• Scope: Layout rules apply only to manual create/edit and record detail pages. They do not apply to import, OpenAPI, workflow post-actions that change fields, or bulk updates.
• Entry: Preset Object Management / Custom Object Management -> Layout Rules

2. Creating a New Layout Rule

• Each layout rule applies to one layout.
• Each layout can have up to 10 layout rules.
• Layout rules are divided into Field Control and Page Control.

2.1 Field Control

• Each layout rule selects a master field (主字段 / master field). Allowed master field types: Single Select (dropdown), Single-line Text, Multi-line Text, Multi-select, Number, Currency, Date, Time, DateTime, Mobile Phone, Email, URL, Boolean, Percent, Region/Location component.

• Conditions between different groups are OR; conditions within the same group are AND.
• Each layout rule can include multiple condition groups, up to 20 actions.
• Field controls must not form cycles; they can form chains only.
• Actions triggered when conditions are met:
  • Show Fields:
    • You may select multiple fields.
    • Allowed scope: non-required fields in the layout (system fields, Owner, Owner Dept., Life Status, Lock Status, Record Type, Sub-object, payment component, check-in component, auto-increment Code, formula fields, rollup/statistics fields, fields that have a parent) are excluded.
    • Effect: fields are hidden by default and appear when the condition is met.
  • Set Required Fields:
    • Allowed scope: non-required and non-read-only fields in the layout (same exclusions as above).
    • Effect: fields become required when the condition is met.
  • Set Read-Only Fields:
    • Allowed scope: non-required fields in the layout (same exclusions as above).
    • Effect: fields become read-only when the condition is met.

2.2 Page Control

• Based on whether the user is on the Create or Edit page, configure which fields are hidden or read-only.
• Business scenarios:
  1. For the Work Order object, after-sales processing fields do not need input during create; they are shown and handled only during after-sales processing. (Hide non-required fields on Create)
  2. For the Quotation request object, basic information can be entered during Create but must be locked during Edit while other fields remain editable. (Allow modification only during Create; lock during Edit)
• Configuration entry:
  • Add a new rule type “Page Control” within object layout rules.

• How to configure:
  1. When the page is Create, you can only set fields to Hidden.
  2. When the page is Edit, you can set fields to Hidden or Read-Only.
  3. Field scope: non-required fields in the layout (exclude system fields, Owner, Owner Dept., Life Status, Lock Status, Record Type, Sub-object, payment component, check-in component, auto-increment Code, formula fields, rollup/statistics fields, fields that have a parent).

3. Layout Rule List

• Support searching by rule name.
• Support filtering by associated layout: default = All.
• List columns: Rule Name, Master Field (and master field status: Disabled, Deleted), Layout Rule Type, API Name, Trigger Mode, Actions.
• Actions:
  • Create
  • Edit: The Edit button is hidden for rules whose master field is disabled/deleted.
  • Enable: shown when status = Disabled
  • Disable: shown when status = Enabled
  • Delete: shown when status = Disabled
  • When status = Enabled, deletion is blocked with the message: “Only disabled layout rules can be deleted.”
  • Copy

4. Frequently Asked Questions

1. Why do users with different Roles see different fields even though they share the same layout?

Role A and Role B share a layout, but Role A lacks some layout fields. A layout rule uses Field1 as the master field. Role A has permission to see Field1, so fields hidden by that layout rule remain hidden for Role A. Role B does not have permission to view Field1, so the fields that would be hidden by that rule are displayed for Role B.

2. Why can’t I select a particular field when configuring a layout rule?

Two possible reasons: 1) A field already used as a condition (master/condition field) cannot simultaneously be a controlled field. 2) That field in this layout is not set to Show.

3. Why can’t a field be changed back to non-required?

If a layout rule marks Field1 as required, that layout rule overrides the field configuration. Even if you set Field1 to non-required in field settings, the front-end still enforces it as required due to the layout rule.

4. Why can I submit when editing even though a required field is empty?

Quick inline editing of a single field does not trigger layout rules.

5. Why is the Layout Rule Type “Page Control” sometimes gray and sometimes active?

Whether “Page Control” is disabled (grayed out) depends on the selected layout type. Only Create/Edit layouts support Page Control.

6. Why can I sometimes not select Page Control type layout rules?

The gray/active state for Layout Rule Type - Page Control depends on: 1) Is the layout a Sub-object? => If yes, Sub-object layouts do not support Page Control rules. 2) Has the object enabled a Create/Edit page layout? a. If not enabled, Page Control is not grayed out. b. If enabled: if the currently chosen layout is a Detail layout, Page Control is grayed out; if it’s a Create/Edit layout, Page Control is active. This is the platform-wide logic. If you find an exception for a specific preset object, contact the corresponding business team. ps: To locate the responsible business team quickly, search the “Business Modules and Related Owners” object in the FS system.

7. Why do hidden fields controlled by layout rules still contain values?

Example: A rule hides FieldText1 when FieldText (single-line text) does not contain “1”. If a user previously entered a value in FieldText1 while FieldText contained “1”, then later changed FieldText to a value that does not contain “1”, FieldText1 becomes hidden but its existing value is not automatically cleared. Submitting the record preserves that hidden field’s value, causing the observed behavior.

8. Sub-object fields on Create/Edit page are not editable and do not show values

If sub-object fields on Create/Edit are not editable or do not display values, check whether the field is hidden by a layout rule or hidden by UI events. Hiding a sub-object field via UI events or layout rules only hides the field value, not the entire column header (table components do not support dynamic table header rendering).