Explaining Extensibility Functionalities

In this lesson, you will learn how to explore the extensibility functionalities available in SAP Sales Cloud and SAP Service Cloud Version 2. These capabilities allow you to adapt the system to meet specific business requirements.

Extensibility enables organizations like NovaLink to go beyond standard functionalities by adding new fields, logic, and behaviors tailored to their processes. These extensions can be created by administrators or key users and range from simple UI enhancements to more advanced custom logic and integrations.

These extensibility capabilities can be accessed and managed within the System Settings under Extensibility Administration:

Custom fields, also known as extension fields, allow you to store additional data that is not part of the standard system. These fields can be added to business entities such as Accounts, Opportunities, or Cases to support specific business needs.

For example, NovaLink may require a field like Competitor Name in Opportunities or Equipment Age in Cases. These fields can be created directly in the system and displayed on relevant pages via Adaptation Mode.

In addition to creating custom fields, you can define field attributes, such as making a field required, and control how fields behave in list views by configuring whether they are searchable, filterable, or sortable.

Dynamic properties allow you to control how fields behave based on specific conditions. This includes making fields visible, mandatory, or read-only depending on the context.

For example, NovaLink can configure a rule that hides the Warranty Expiry Date field when a product is not under warranty. Similarly, priority-related fields can become required when a service ticket is marked as urgent.

Dynamic Properties can also be set for Layouts and Business Roles. These rules ensure that users only see and interact with relevant information, improving usability and reducing issues such as user interface complexity.

Custom logic allows you to extend application behavior by defining rules and automated actions. This enables you to implement business-specific processes without modifying the core system.

There are two main approaches:

• Business expression-based logic: Used for validations and determinations based on simple rules. For example, ensuring that a deal value must be entered before an opportunity can be saved.
• External API-based logic (hooks): Used for more advanced scenarios, where external systems are involved. For example, calling an external pricing service during quote creation.

This flexibility enables you to automate processes, enhance data quality, and integrate external services seamlessly.

External hooks allow you to extend standard application behavior by triggering external logic during specific events, such as saving a business entity. This enables integration with external systems or services, allowing complex validations, calculations, or processes to be handled outside the core application.

Reference Fields allow administrators to use attributes from related entities when defining custom logic on a specific business entity. This enables more advanced scenarios, such as using customer data within case logic to drive validations or determinations.

Custom code lists allow you to define your own values for drop-down fields, enabling you to align the system with your specific business terminology and processes.

Code list restrictions additionally enhance this by dynamically limiting available values based on context, ensuring users only select relevant and valid options.

• Extensibility in SAP Sales Cloud and SAP Service Cloud Version 2 allows organizations to adapt the system to specific business needs beyond standard functionality.
• Custom fields can be created to store additional data for business entities such as Accounts, Opportunities, or Cases.
• Field attributes and query properties can be configured to control behavior like mandatory fields, filtering, sorting, and searchability.
• Dynamic properties enable context-based behavior, such as making fields visible, required, or read-only depending on conditions.
• Custom logic can be implemented using business expressions for simple rules or external APIs (hooks) for advanced integrations.
• Custom code lists allow the definition of tailored drop-down values aligned with business terminology.
• Code list restrictions ensure that only relevant values are available based on specific conditions.
• These extensibility features improve usability, data quality, and process automation while keeping the core system unchanged.