SAP C_WZADM_2404 - SAP Certified Associate - SAP Build Work Zone - Implementation and Administration

Shadow users are users that are created in the SAP BTP subaccount to map the users from the connected identity provider. Shadow users are required for users to access SAP Build Work Zone. The following methods can be used to create shadow users:

Automatic creation upon login via connected identity provider: This is the recommended and default method for creating shadow users. When a user logs in to SAP Build Work Zone for the first time using an identity provider such as SAP Cloud Identity Services, a shadow user is automatically created and assigned to the role collections that are mapped to the groups attribute in the identity provider1.

Admin UI on the SAP BTP subaccount cockpit: This is a manual method for creating shadow users. An administrator can use the SAP BTP subaccount cockpit to create and manage shadow users and assign them to role collections2.

Authorization & Trust Management Service API: This is a programmatic method for creating shadow users. An administrator can use the Authorization & Trust Management Service API to create, read, update, and delete shadow users and assign them to role collections3.

The following methods cannot be used to create shadow users:

Import from SAP SuccessFactors Employee Central: This method can be used to import users from SAP SuccessFactors Employee Central to SAP Cloud Identity Services, but not to create shadow users in the SAP BTP subaccount.

CSV file upload in the SAP BTP subaccount cockpit: This method can be used to upload users and assign them to role collections in the SAP BTP subaccount, but not to create shadow users. Shadow users are created only when the users log in via the connected identity provider. References:

1: Explaining the Authentication Flow of SAP Build Work Zone

2: Assign SAP Build Work Zone Roles to Users

3: Authorization & Trust Management Service API

: Importing Users from SAP SuccessFactors Employee Central

: Uploading Users and Assigning Them to Role Collections

Launchpad (shell) plugins are a way to extend the functionality and appearance of the SAP Build Work Zone header bar, sub-navigation bar, user menu, and user settings. They are different from UI integration cards, which are a way to display information and application content from different backend systems in a unified and consistent way in SAP Build Work Zone. Some of the characteristics that are applicable to launchpad (shell) plugins, but not to UI integration cards, are:

The SAP Build Work Zone Advanced extension is required in SAP Business Application Studio: This extension provides a set of tools and templates to create, test, and deploy launchpad (shell) plugins to SAP Build Work Zone. It also enables the direct deployment of the launchpad (shell) plugin from SAP Business Application Studio to SAP Build Work Zone, using the UI Integration Card: Deploy to SAP Build Work Zone, advanced edition option in the context menu of the manifest.json file1.

The application logs can be accessed from SAP BTP cockpit: Since launchpad (shell) plugins are deployed as HTML5 applications to SAP BTP, their application logs can be viewed and downloaded from the SAP BTP cockpit, under the HTML5 Applications section. This can help troubleshoot any issues or errors that occur during the runtime of the launchpad (shell) plugin2.

The source code can be downloaded directly from SAP BTP cockpit: Another feature of deploying launchpad (shell) plugins as HTML5 applications to SAP BTP is that their source code can be downloaded as a ZIP file from the SAP BTP cockpit, under the HTML5 Applications section. This can help backup or restore the launchpad (shell) plugin code, or share it with other developers2.

The characteristics that are not applicable to launchpad (shell) plugins, but to UI integration cards, are:

They are managed via the administration console of DWS: UI integration cards are managed via the administration console of SAP Build Work Zone, under the UI Integration Cards section. Here, users can upload, view, edit, and delete the UI integration cards that are available for their site. Launchpad (shell) plugins are not managed via the administration console, but via the SAP Business Application Studio or the SAP BTP cockpit34.

They are listed in the Content Manager based on the HTMLS content provider setup: UI integration cards are listed in the Content Manager of SAP Build Work Zone, under the HTMLS content provider, which is a way to connect to external HTML5 applications or UI integration cards. Users can browse, search, and add the UI integration cards to their site pages using the Content Manager. Launchpad (shell) plugins are not listed in the Content Manager, as they are not considered as content, but as extensions4 .

The Fit-to-Standard Analysis is a process of identifying the gaps between the customer’s business requirements and the standard SAP solutions, and determining the best way to close those gaps1. When pre-delivered content is planned to be used, such as the content packages provided by SAP Build Work Zone, some activities can help prepare the Fit-to-Standard Analysis, such as:

Expose business content: This means making the relevant business content (for example, SAP Fiori apps) available and accessible in the launchpad component of SAP Build Work Zone. This can be done by configuring the destinations, catalogs, and roles for the business content sources2. Exposing business content can help demonstrate the standard SAP solutions and evaluate their fit with the customer’s needs.

Maintain destination to SAP SuccessFactors: This means creating and configuring a destination to connect SAP Build Work Zone to SAP SuccessFactors, which is a cloud-based human resource management system. This can be done by using the SAP BTP cockpit or the SAP Cloud Connector3. Maintaining destination to SAP SuccessFactors can help leverage the pre-built content packages for SAP SuccessFactors that are available in SAP Build Work Zone, such as the Employee Onboarding package4.

The other options are incorrect because they are not related to the pre-delivered content for SAP Build Work Zone. SAP Cloud Transportation Management service and SAP IBP are different SAP solutions that are not part of the content packages for SAP Build Work Zone.

References:

Proven practices for fit-to-standard for your SAP Activate project, Section 1

Explaining the Prepare Phase, Section 2.2

Create and Configure Destinations, Section 2.1

SAP Build Work Zone Content Packages, Section 2.2

 Launchpad shell plugins are HTML5 applications that can be deployed to SAP Build Work Zone using SAP Business Application Studio. The deployment process is automated and involves creating a project from a template, adding the shell plugin code, and deploying the project to the SAP BTP subaccount HTML5 application section. The launchpad administrator can then add the shell plugin app to the launchpad using the launchpad configuration cockpit. References:

Exploring Launchpad Plugins - SAP Learning

Add a new HTML5 application to the MTA - SAP Help Portal

Creating and Configuring Shell Plugin Apps - SAP Help Portal

The feed widget setting that is used on the home page level to show all public feed updates is Global. The feed widget is a type of widget that embeds a feed in an external web page. The feed widget builder allows users to create and customize feed widgets using various settings, such as the feed source, the feed type, the feed layout, and the feed filter. The feed source setting determines which feed is displayed in the widget. There are four options for the feed source setting: Public, Global, Home, and Company. The Public option displays the public feed of the site, which includes all public updates from all workspaces and members. The Global option displays the global feed of the site, which includes all public and private updates from all workspaces and members that the user has access to. The Home option displays the home feed of the user, which includes all updates that are relevant to the user, such as updates from their workspaces, followed members, and @mentions. The Company option displays the company feed of the user, which includes all updates from the user’s company, such as updates from their colleagues, managers, and subordinates. The feed widget setting that is used on the home page level to show all public feed updates is Global, because it shows all the updates that the user can see on the site, regardless of their workspace or member affiliation. The other options are either too restrictive (Home and Company) or too broad (Public) for the home page level. References:

Widget Builders

About Widgets

A subscription of SAP Build Work Zone is an application that allows users to access the solution and its features, such as creating and joining workspaces, accessing integrated tools and applications, and personalizing their sites. A service instance of SAP Build Work Zone is a space in SAP BTP where the solution runs and where content packages and UI integration cards can be deployed using APIs. Both the subscription and the service instance require the activation of SAP Cloud Identity Services (IPS) as a prerequisite, but only the subscription requires a post-booster activation of IPS to enable user authentication and authorization. The post-booster activation of IPS is a step that must be performed after creating a subscription of SAP Build Work Zone in the SAP BTP cockpit. It involves configuring the IPS settings, such as the identity provider, the trust configuration, and the role collection mapping. The service instance does not require this step, as it inherits the IPS settings from the subscription. References:

Create a Subscription for SAP Build Work Zone

Create a Space and a Service Instance

Deploy Content Packages Using APIs

Deploy UI Integration Cards Using APIs

 Role collections are created in the Perform Post-Booster step of the product setup. This step involves running the Work Zone Configurator, which creates the role collections for SAP Build Work Zone and SAP SuccessFactors Work Zone. These role collections are used to assign authorizations to users and groups on the SAP BTP subaccount level1. References: 1: Explaining the Provisioning of Users and Roles in SAP Build Work Zone, https://learning.sap.com/learning-journey/implement-and-administer-sap-build-work-zone/explaining-the-provisioning-of-users-and-roles-in-sap-build-work-zone_f81cff40-ea59-49fc-8c9e-65f68b63a812

The HR content package is a collection of content items such as UI integration cards, guided experience, or workspace templates that are bundled together in a ZIP file and can be easily uploaded and installed to your subaccount1. The HR content package provides the following functionalities:

Workspace templates: These are pre-built workspaces that you can use to create your own workspaces for various HR scenarios, such as onboarding, offboarding, performance management, and so on. You can customize the workspace templates to suit your needs and preferences1.

Guided experience: These are workflow-based cards that help you perform specific tasks through a multistep process possibly spanning multiple systems. For example, you can use the Onboarding Guided Experience to provide a personalized journey for your new hires from the time they receive an offer letter to their first 90 days at your company. You can also use the Return to Workplace Guided Experience to plan a safe return to the workplace for your company employees2.

UI Integration Cards: These are cards that display data from various sources and allow you to interact with them. For example, you can use the Employee Profile Card to view and edit the personal and professional details of an employee. You can also use the Employee Feedback Card to give and receive feedback from your peers and managers1.

The HR content package does not include chatbots or content templates as part of its functionalities. References:

Guided Experiences | SAP Help Portal

SAP Help Portal

 To access the administration console of SAP Build Work Zone, you need to have the administrator permission in Digital Workspace Service. This permission is granted by the company administrator or the area administrator of the site that you want to access. Without this permission, you will not see the Administration Console option under your avatar in the User Actions menu. The other options (B, C, and D) are not related to the administration console access, but to the SAP BTP account and subaccount level permissions that are required for setting up SAP Build Work Zone. References:

SAP Build Work Zone, advanced edition - SAP Online Help

SAP Build Work Zone - Implementation and Administration