Configure Attribute Display in Attribute Groups

Use Configure Fields and Regions in Business Rules to conditionally display or populate attribute values during view, edit, or create operations.

You can do the following actions with attributes:
  • Show or hide them
  • Assign default values
  • Mark it as read-only
  • Make it mandatory
Note: Defaulting of attribute values is only supported in the Create Object pages.

How to Hide an Attribute

You can hide or show an attribute or attributes on a page using Visual Builder Studio.

Here's how you can hide an attribute within an attribute group:
  1. Navigate to the page.
  2. Select the Edit Page in Visual Builder Studio task from the Settings and Actions menu.
  3. Select your project or create a new one. Ensure that you're in Express mode.
  4. Click the Configure Fields and Regions button in Business Rules.
  5. In the Fields and Regions area, click Regions and select the attribute group within which the field exists.
  6. In Extension Rules, click the plus (+) icon.
  7. In the Create Business Rule window, enter the rule details and click Create.
  8. In the rule window, select the attribute that you want to show or hide and click the Hidden column.
  9. Select Visible to show the attribute or Hidden to hide the attribute.
    Note: See the Use Case section to see how to create rules, and hide attributes.
  10. Preview and publish your changes.

The following sections provide a few use cases that use the Configure Fields and Regions task in Visual Builder to configure attributes for various objects.

Use Case to Hide and Default Item Attributes based on Roles

The following example shows how to build conditions and actions using the Configure Fields and Regions task to hide and default attributes for users with the Product Data Steward role.
  • Condition:
    • Role = Product Data Steward
  • Actions:
    • Hide Attributes:
      • All Secondary Unit of Measure attributes, except the Primary Unit of Measure.
    • Default and set as read-only:
      • Engineered Item Flag = true
      • Lifecycle Phase = Design

This image shows an example of hiding attributes and defaulting attribute for a Product Data Steward.

Use Case for Hiding Engineering Item

Here's an example of hiding attribute groups for an engineering item:

  • Condition:
    • Engineered Item Flag = true
  • Actions:
    • Hide Attributes:
      • All Operational Attributes attribute groups, except the Item Basic attribute groups.
This image shows an example of hiding attribute groups for an engineering item.

Attributes to Define Item Conditions

Entity Attributes
Item

Engineered Flag

Item Class

User

User Name: For example: Logged in user's user name John.Dove

Role: For example: Logged in user's role- SupplierProductDesignEngineer

Use Case to Hide Migrated Attribute in Workflows

You can conditionally display attributes during view, edit, or create flows based on attributes described in Attributes Available for Workflow Conditions table.

Here's how you hide an attribute within a workflow object:

Use the Configure Fields and Regions to conditionally to hide an attribute within a workflow:

  • Hide Attribute:
    • Migrated

    This image shows an example of hiding the Migrated attribute

Use Case to Make the Organization Field Read-Only and Set a Default Priority for New Item Requests

Here’s how you can mark the organization as read-only, defaulting it to the master organization, and setting the priority to Low when creating a new item request.

  • Condition:
    • BaseChangeType = NewItemRequest
  • Actions:
    • Set attributes as read-only:
      • Organization
    • Set default value for attributes:
      • Organization = V1
      • Priority = Low

This image displays how we can configure new item request attributes using Visual Builder

Use Case for Change Orders

Here's an example for hiding the organization for change orders. In Visual Builder set the condition and action as follows:
  • Condition:
    • BaseChangeType = Change Order
  • Action:
    • Hide attribute = Organization
This image shows how Visual Builder can be used to configure change order attributes.

Attributes Available for Workflow Conditions

Entity Attributes
Workflow

BaseChangeType

Organization

Priority

Reason

Type

User

User Name: For example: Logged in user's user name John.Dove

Role: For example: Logged in user's role- SupplierProductDesignEngineer

Use Case to Hide Company Profile Region in Create Manufacturer based on Country

Here's an example of hiding Company Profile Region when manufacturer is in the United States. In Visual Builder set the condition and action as follows:
  • Condition:
    • Country = US
  • Action:
    • Hide Tab:
      • Manufacturer Company Profile Attributes

This image shows how Visual Builder can be used to configure manufacturer attributes

Use Case to Configure the Company Profile Region for Manufacturers Based on Status

Here’s an example of how to use Configure Fields and Regions in Visual Builder to hide company profile region attributes for a manufacturer when the status is Inactive, while also setting the Website field to read-only.
  • Condition:
    • Status = Inactive
  • Actions:
    • Hide attributes:
      • Classification
      • Industry
      • Channels
      • Brands
      • Products
      • Headcount Details
      • Global Revenue
    • Make attributes read-only:
      • Website
This image displays how Visual Builder can be used to configure manufacturer profile attributes

Attributes to Define Manufacturer Conditions

Entity Attributes
Manufacturer

Manufacturer Basic Attributes: For example: Country, Brand, Status

Manufacturer Attachments Attributes: For example: Category, Type

Manufacturer Extensible FlexFields (when exists)

User

User Name: For example: Logged in user's user name John.Dove

Role: For example: Logged in user's role- SupplierProductDesignEngineer