Name: Configuring Spring Expression Language in Backoffice Framework in SAP Commerce Cloud
Uploaded: 2021-3-17
Duration: 251 s
Description: In this video, we’ll explain SpEL (Spring Expression Language) notation and we’ll show you how to use it within the configuration in SAP Commerce Cloud.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><div><div><div><div><div><p>In this video, we’ll explain SpEL (Spring Expression Language) notation and we’ll show you how to use it within the configuration in SAP Commerce Cloud.</p>  <p> </p></div></div></div></div></div></div></div></div></div></div></div>

Configuring Spring Expression Language in Backoffice Framework in SAP  Commerce Cloud

Hi, my name is Lily. In this video, I'll explain SpEL spring expression language notation and I'll show you how to use it within the configuration. In previous videos, we saw a specific type of expression language used in some of the back office framework XML files. This expression language is called the Spring Expression Language or SpEL for short. SpEL is a powerful expression language that provides a back office framework with support for querying in object craft at runtime. You will most commonly see SpEL used to evaluate the expression against an object instance called the root object. This allows you to access an object's property values within back office framework. Typically, this is done with the syntax. For example, catalog ID would signify that you want the value of the ID field from the catalog version object. The SAP Commerce documentation specifies where SpEL can be used in the back office framework. Configuration files. An instance where you have seen that SpEL can be used is when specifying the base user interface configuration for a component's context. This is what provides the spring representation for a given object. This configuration is commonly used in reference editors to present an object on a selection list, or on a list of previously selected items. Not all aspects of SpEL can be used within the back office configuration files. Back office framework does not support the construction of any objects from SpELs due to security considerations. For more information about SpEL, please see the Spring Framework documentation. Let's first take a look at the existing SpEL expression in the configuration for the catalog version type. For doing that, I'll open the cockpit config XML file. Then I'll use the Show Filter Options button at the top of the screen. The component we want to work with is base, and the type we want to config is catalog version. After selecting these two filters, I'll click on the search blue button and the specific portion of the file for this particular component and type is shown. You can see here that the default string representation for the base component for catalog version is a catalog label retrieved by using the label service and the version separator with a colon. Now I'll change the SpEL expression for this configuration to show how we can access other properties of the catalog version. As you can see, when we start with the dot notation, we can then refer to any properties of the catalog version. Here we are specifying that the values for the active property should also display, in addition to the catalog, label and version. We can even use the dot notation to access further nested properties, allowing us to traverse the entire object graph. I'll save these changes in the configuration by clicking the store button at the bottom right of the screen. Now let's see how our changes are reflected in the back office user interface. I'll select the product type on the explorer tree and choose one product from the list. In the editor area. On the first tab, we have a reference editor for the catalog version. You can see that the string representation of this object consists of the label of the catalog, its version, and its active flag, just as we defined in the configuration. In this video, we looked at what the SpEL notation is and how it is useful in specific places within the configuration. Thanks for watching.