Name: Working with Backoffice Framework Actions in SAP Commerce Cloud
Uploaded: 2021-2-15
Duration: 355 s
Description: This demo explains the concept of actions in the Backoffice Framework and how you can utilize them in your application.

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>This demo explains the concept of actions in the Backoffice Framework and how you can utilize them in your application.  <br></div></div></div></div>

Working with Backoffice Framework Actions in SAP Commerce Cloud

Hi, my name is Lily. In this video, we'll discuss back office frameworks, actions and how you can utilize them in your own application. I'll show you an example of back office framework actions. Here we see a list of sample products displayed in a widget called Collection Browser. For products, there is a set of relevant actions available. Add a new item. Delete the selected item. Synchronize the selected item and any others. An action can be thought of as a button with its associated icon that invokes some operation on demand. When the button is clicked by a user, an action is an independent component and can be reused in any widget. For example, let's click on an item to open it in the editor area widget. As we can see, the same delete action is also available from this widget. When you create a new widget and would like to add delete functionality to it, you can just reuse the generic delete action and bring it to the appropriate model property to be deleted. How to add an action to a widget will be shown in detail in the subsequent instructor led, hands on training. For more information about how to add an action to a widget, you can view the Using Actions in Widgets Help page. An action can be configured so that it displays a confirmation pop up with a custom message. Here's a library of predefined actions available in back office framework that you can use in your own application. You can check what actions are available out of the box in the actions gallery in the help pages. For example, there are actions like create, delete and so on. Here you can also see each actions default icon. When a widget, such as the editor area widget is able to work with multiple item types. It's possible to configure different sets of actions to be enabled per type. As an example, let's first look at the editor area widget. For the product type. You can see here that this widget is configured for the delete action, the clone action and the synchronize action on the referred product item. Now if we look at the same editor area widget, but with the employee type, we can see that a different set of actions is configured in the editor. For this type. The editor area widget allows us to delete the current employee item and also to edit its permissions. Let's take a closer look at the permission management action. Clicking the permission management action from the editor area widget fires up the Permission Management Group widget. Different user types can have different access rights within an application, and this is managed through this group widget. As a side note, the Permission Management Group widget consists of multiple widgets that are already configured to communicate with each other and with the permission action. You can read more about this in the standard Widgets library. Documentation. In the XML configuration, actions are selected to be displayed for the types in your system. Configuration will be described in more detail later, but for now, it's enough to know that by editing the XML configuration, you can specify which actions will be enabled for each type in a specific widget. Let's look at an example where we have overridden the default actions for a widget. Here we can see that we have overridden the default back office actions for the editor area widget. Remember that the editor area widget is configured with just a delete action by default. We are overriding the editor area actions only for the principal type. We have added the principal permission action to the action group for this combination of type and widget. In back office, the principal type is the super type for a few other types, including the employee and customer types. Because of this XML configuration that you just saw, the principal type and all of its subtypes will have the permission management action enabled for certain business requirements. You may need to extend or implement a custom action in your application. Creating custom actions is a subject in the back office framework instructor led training course. If you would like more information about creating custom actions, please see the help page called Creating an Action. Normally, only widgets send and receive data through sockets to communicate. Actions are used inside the widgets. In some cases though, you may need to have your action communicate with other widgets. Back office framework allows actions to contain sockets for this purpose. These actions are called socket aware. For more information about how to implement socket aware actions, please see the help page called Creating Socket Aware Actions and Editors. Now let's look at an example of an action that is socket aware. The create action in the collection browser widget is socket aware and connected to the wizard widget, which is not visible by default. When a user clicks the create action, it sends the type of the currently displayed items through a socket to the Wizard widget. The Wizard widget then becomes visible and enables the user to create a new object of that type. In this video, I showed you the back office framework's actions and how you can utilize them in your own application. Thanks for watching.