Managing Dynamic Property Rules

Objective

After completing this lesson, you will be able to adapt dynamic property behaviors in SAP Sales Cloud and SAP Service Cloud Version 2 based on conditions and roles.

In this lesson, you will learn how to use Dynamic Property Rules to control field properties, layouts, and behavior based on defined conditions. Dynamic Property Rules are a powerful, no-code configuration tool available in SAP Sales Cloud and SAP Service Cloud Version 2. They allow you to dynamically change a field's properties. For example, making the field visible, required, or read-only based on conditions you define.

This functionality applies to detail screens for a single entity instance (for example, a specific Case, Lead, or Opportunity). It does not apply to list views or tables that display multiple entities.

Types of Conditions in Dynamic Property Rules

Field Attributes: These conditions evaluate the current value of specific fields and change the field’s properties within the same business entity. For example, making the Escalation Manager field required when Priority equals High.

Layout Conditions: These conditions are specialized rules that manage the properties of sections, tabs, and buttons in the user interface, controlling visibility (visible/hidden) based on the application's state.

Role-Based Attributes: Conditions that trigger actions based on the user's assigned business role, enabling different field behaviors for different user types.

Diagram showing types of conditions in dynamic property rules: “Field Attributes” evaluate field values, “Layout Conditions” control UI elements, and “Role-based Attributes” trigger actions based on user roles.

To access the Dynamic Property Rules, go to your user profile menu and navigate to System Settings→All Settings→Extensibility→Extensibility Administration. Now choose a business entity, such as Case, on the left side. You will find the Dynamic Properties tab on the right side. To create new Field Attributes, Layout Conditions, or Role-Based Attributes, select the plus icon in the top-right corner.

In the Dynamic Properties tab of the Case entity, three different types of rules can be created, namely Field Attributes, Layout Conditions and Role-Based Attributes.

Benefits of Dynamic Property Rules

  • Enhance Data Quality: Enforce data entry standards by making fields required only when relevant.
  • Improve User Adoption: Simplify the user interface by hiding unnecessary fields, reducing clutter, and guiding users through each step of the process.
  • Increase Agility: Adapt the UI to changing business processes quickly, without requiring a development cycle.
  • Reduce Total Cost of Ownership (TCO): Fulfill complex UI logic requirements through configuration instead of custom code.

Applying Dynamic Property Rules in Real-Life Scenarios

Dynamic Property Rules help NovaLink tailor SAP Sales Cloud and SAP Service Cloud Version 2 to the needs of different users. The following scenarios show how Adrian (Sales Rep), Tom (Service Agent), and Jennifer (System Administrator) apply these rules in their daily work.

Scenario 1: Mandatory Invoice Fields for Billing Cases (Field Attributes)

When Tom works on billing related service cases, the system automatically requires him to enter key information such as the Invoice Number and Customer Account. This ensures billing inquiries are complete and ready for processing without back and forth clarification. This scenario is achieved using Field Attributes:

  • Condition: If Case Type is 'Billing Inquiry'.
  • Action: Make Invoice Number field and Customer Account field required.

Scenario 2: Priority‑Based Section Display (Layout Conditions)

When a case priority is critical, Adrian sees escalation‑related sections automatically appear on the case page, while less relevant sections are hidden. This helps him focus on the information needed to handle cases efficiently. This scenario is achieved using Layout Conditions:

  • Condition: If Case Priority is 'Critical'.
  • Action: Show Escalation Management section and hide Standard Resolution section.

Scenario 3: Manager Override for Priority Changes (Role‑Based Attributes)

Jennifer wants to set up rules so that only Service Managers can modify the Case Priority field. Agents see the field as read-only, while managers can override it when necessary, ensuring proper control over sensitive case updates. She can achieve this scenario using Role Based Attributes:

  • Condition: If Business Role is 'Service Manager'.
  • Action: Enable updates for Case Priority field while keeping it read-only for agents.

Exploring the Different Types of Conditions in Dynamic Property Rules

  1. Field Attributes

    Field Attributes are a specific type of Dynamic Property Rule condition. They define field properties (entity attributes) such as creatable, updatable, required, or hidden, based on the application's context. Field Attributes control individual field behaviors through condition-based logic, enabling administrators to modify field properties without custom development.

    Field Attributes control several key properties:

    • Creatable: Indicates whether the attribute can be set during entity creation. If set to false, the Custom UI marks the corresponding fields as read-only.
    • Updatable/Read-only: Determines if the attribute can be modified during update operations. If set to false, the API implementation ignores the values.
    • Required/Mandatory: Specifies whether users must enter a value, shown by an asterisk beside mandatory fields.
    • Hidden/Visible: Controls field visibility based on application context and business conditions.
    A Dynamic Property rule for Field Attributes, based on the case type and warranty extension field, the priority field will be marked as required.
  2. Layout Conditions

    Layout Conditions manage the properties of UI elements, such as sections, tabs, and buttons, within the user interface. They control visibility (visible/hidden) based on specific business conditions.

    Unlike Field Attributes, which affect individual fields of business entities, Layout Conditions manage entire sections, tabs, and buttons in your user interface. They enable dynamic user interfaces that adapt to your business context, ensuring users see only relevant information based on current data conditions.

    A Layout Conditions rule for the Case entity based on the case type and priority fields.

    In the following video, you will learn how to create and apply Layout Conditions using Dynamic Property Rules to customize your interface based on specific business logic. Following a practical example with Adrian Chase, a Sales Representative, you will be guided step-by-step through setting up a rule that shows or hides tabs depending on customer classification.

  3. Role-Based Attributes

    Role-Based Attributes are specialized Dynamic Properties Rules that control field behavior based on a user's assigned business role. They enable different access levels and field properties for different user types within the same entity.

    This type of rule is built on a layered model to provide both broad and granular control. Default Rules establish a universal baseline of field behavior that applies to all users. For more targeted requirements, you can create Role-Specific Rules that apply only to users assigned to specific business roles.

    The system has built-in Override Mechanisms to handle conflicts. These mechanisms ensure that specific, role-based rules take precedence. They supersede default rules and other static field properties. This layered approach provides a flexible and powerful way to tailor the user experience for different groups.

    A Role-Based Attributes rule for the Case entity based on the case type and business role, the timePoints/escalatedOn field will be made Visible.

Lesson Summary

  • Dynamic Property Rules in SAP Sales Cloud and SAP Service Cloud Version 2 enable no-code configuration to modify field properties (visible, required, read-only) based on conditions, improving UI adaptability.
  • Field Attributes dynamically control individual field behaviors, including creatable, updatable, required, and hidden properties, based on values within the same business entity.
  • Layout Conditions control the visibility of UI elements such as sections, tabs, and buttons, allowing the interface to adapt by showing or hiding components based on business conditions.
  • Role-Based Attributes tailor field behavior according to the user’s assigned business role, using layered rules with override mechanisms for flexible, role-specific configurations.
  • Applying Dynamic Property Rules improves data quality, simplifies the user interface, increases agility, and reduces the need for custom development, thereby lowering the total cost of ownership.
  • Real-life examples include hiding or making fields required for specific case types in SAP Service Cloud Version 2 and setting fields to read-only during certain sales phases in SAP Sales Cloud Version 2.
Learning
SAP FacebookSAP YoutubeSAP LinkedIn