Name: Introducing Widget Essentials in Backoffice Framework in SAP Commerce Cloud
Uploaded: 2021-4-14
Duration: 219 s
Description: In this video, you will be introduced to widget essentials, and learn what a widget is from a technical point of view.

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>In this video, you will be introduced to widget essentials, and learn what a widget is from a technical point of view. </div></div></div></div></div></div></div>

Introducing Widget Essentials in Backoffice Framework in SAP Commerce Cloud

Hi, my name is Lily. In this video, we'll discuss WeChat essentials. We'll describe what a widget is from a technical point of view. Widgets are the building blocks for application designers and developers who create applications based on the back office framework. Widgets don't know about each other, but they can be wired together to communicate. Widgets may also be grouped together to form a reusable team of communicating widgets. We've mentioned in previous modules that a large set of widgets, called the Standard Widgets Library, is provided out of the box with the back office framework. Even with these out of the box widgets, it's common. The specific business requirements will require either the widget to be extended, or for there to be new, completely custom widgets created. The back office framework is designed for this concept of extension and customisation to get the most out of this video. A strong knowledge of widget essentials will enable developers to better understand how to extend existing widgets and create new custom widgets. Each widget is a standalone, deployable component with a clearly defined interface and a specific purpose. Each widget is uniquely defined by its ID and optionally defined by other elements such as its name, view, and controller class. A widget definition provides a blueprint for all instances of that widget. It describes what application files are necessary to make this widget display and function. It also describes what properties, such as settings, are available to be populated on a widget instance. When a widget is used within an application, it's called a widget instance. The relationship between a widget definition and its widget instance is analogous to the relationship between a Java class and its Java object. Here you can see a diagram representing the relationship of a widget definition to its widget instance. Note that there can be many widget instances for every one widget definition. Also, note that each widget instance can optionally have multiple child widget instances, and also may have one parent widget instance. We previously mentioned that widgets can have inputs and outputs that are called sockets. Each widget socket has an ID and a type definition. The type definition is important as it is used for compatibility checking when a user tries to wire two widgets together. The socket must match in order for a connection to be established. Socket connections are how widgets communicate. Each connection contains references to the source and target widget instances. The connection also contains the IDs of the output socket from the source widget, and the input socket from the target widget. This diagram shows how a widget connection and a widget socket relate to the concepts of a widget definition and widget instance. As you can see, the socket is part of the definition, which means it's part of the blueprint for all widget instances. A widget definition specifies the number of inputs and output sockets that any widget instance of that type can have. The widget connection is an actual instance of a connection between two widget instances. Each widget instance can have multiple connections configured. The type of connections that can be configured for a widget instance is determined by the widget definition. In this video, we described what a widget is from a technical point of view. Thanks for watching.