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

 Development artifacts are the components that are created or modified by developers to implement the business requirements of a project. In SAP Activate for SAP Build Work Zone, the development artifacts include launchpad plugins and UI integration cards. Launchpad plugins are extensions that enhance the functionality of the SAP Fiori launchpad, such as adding custom tiles, actions, or notifications. UI integration cards are reusable UI components that display data from different sources in a compact and user-friendly way. Home pages and workspaces are not development artifacts, but configuration artifacts. Configuration artifacts are the settings that are applied by administrators or end users to customize the appearance and behavior of the SAP Build Work Zone service, such as creating home pages, workspaces, or assigning roles and permissions. References:

SAP Build Work Zone Developer Guide, section “Development Artifacts”

SAP Build Work Zone Administrator Guide, section “Configuration Artifacts”

The SAP Build Work Zone mobile app passcode policy can be configured in the SAP BTP subaccount mobile service. This is the SAP Mobile Services instance that is used by the SAP Mobile Start app as an https endpoint for authentication and routing. It provides an Admin Cockpit that allows administrators to access logs and configure specific settings for the app, such as the passcode policy. The passcode policy determines the minimum length, complexity, and expiration time of the passcode that users mustcreate to access the app. By default, the passcode should have a minimum length of 8 digits/characters and it is possible to allow biometric authentication (for example, face ID, fingerprint) upon successful passcode creation. To access the SAP BTP subaccount mobile service, administrators need to have the MobileAdmin role assigned to them and construct the URL for the SAP Mobile Services Admin Cockpit. References:

Accessing SAP Mobile Services Settings

About the SAP Build Work Zone Advanced Mobile App

To perform the initial product setup for SAP Build Work Zone, standard edition, you need to do the following steps:

Set up a trial account on SAP BTP, if you don’t have one already. This will allow you to access the SAP BTP cockpit and the SAP Build Work Zone, standard edition service. You can also use a regular account with SAP BTP Free Tier service plan for SAP Build Process Automation1.

Run the booster on SAP BTP to automatically create a subscription and a service instance for SAP Build Work Zone, standard edition. The booster will also configure the necessary roles and authorizations for you to access the service. You can find the booster in the SAP BTP cockpit under Boosters SAP Build Work Zone, standard edition21.

Optionally, you can also complete the configurator steps to customize your SAP Build Work Zone, standard edition site, such as adding a logo, a theme, and a site name. You can access the configurator from the SAP BTP cockpit under Services Instances and Subscriptions SAP Build Work Zone, standard edition Configurator3.

You don’t need to install a business content package as part of the initial product setup. This is an optional step that you can do later if you want to use predefined content for SAP Build Work Zone, standard edition, such as templates, cards, and widgets4. References:

SAP Build Work Zone, standard edition - SAP Online Help

Configure SAP Build Work Zone, Standard Edition | SAP

SAP Build Work Zone, advanced edition - SAP Online Help

Questions about SAP Build Work Zone, standard edition

The SAP Cloud Transport Management service integration allows you to transport various content artifacts between subaccounts, such as UI integration cards, applications, and workpages. UI integration cards are reusable user interface elements that display data from different sources in a consistent way. Applications are software solutions that run on SAP Business Technology Platform and provide specific functionality for users. Workpages are collections of UI integration cards that can be arranged in different layouts and accessed from the SAP Build Work Zone home page. Workspaces are not content artifacts that can be transported using the SAP Cloud Transport Management service integration, but rather logical containers that group related content artifacts and provide collaboration features for users. References:

UI integration cards: [UI Integration Cards]

Applications: [Applications]

Workpages: [Workpages]

Workspaces: [Workspaces]

 The following are the features of SAP Build Work Zone that enable users to create and consume content:

UI embedding: This feature allows users to embed UI elements such as UI Integration Cards, URL apps, SAPUI5 apps, and WebDynpro ABAP apps into SAP Build Work Zone pages and workspaces123. UI embedding enables users to access various applications and services from a single interface and create personalized and engaging experiences.

Guided Experience: This feature allows users to create and consume interactive and step-by-step guides that help them complete tasks and workflows in SAP Build Work Zone and other applications12. Guided Experience enables users to learn and perform complex processes with ease and efficiency.

Content Package: This feature allows users to create and consume reusable and modular content bundles that contain UI elements, guided experiences, and workspace templates124. Content Package enables users to share and distribute content across different SAP Build Work Zone instances and environments.

References: 1: https://blogs.sap.com/2021/11/16/sap-work-zone-starter-tutorials/  2: https://learning.sap.com/learning-journey/implement-and-administer-sap-build-work-zone/explaining-the-architecture-of-sap-build-work-zone_c5cfecde-4e06-448e-9755-3fc76c77f74f  3: https://blogs.sap.com/2023/03/30/access-fiori-apps-via-sap-build-work-zone-site-with-federated-sap-s-4hana-content/  4: https://blogs.sap.com/2022/11/15/sap-build-work-zone-saps-no-code-offering-for-building-business-sites/

My Workspace is a personal workspace that only you can access and edit1. You cannot invite other users to join your My Workspace, unlike other workspaces that can be shared with internal or external users23. The layout of My Workspace can be based on templates, just like other workspaces1. You can also create multiple tabs in My Workspace, as well as in other workspaces1. References: 1: SAP Build Work Zone, advanced edition - SAP Online Help, https://help.sap.com/docs/build-work-zone-advanced-edition/sap-build-work-zone-advanced-edition/workspaces-8ff3df94802449f3877af5c380b22c4b  2: What are SAP Build Work Zone workspaces? |Summer Tutorial Series Lesson 3: Workspaces, https://blogs.sap.com/2022/10/04/what-are-sap-work-zone-workspaces-summer-tutorial-series-lesson-3-workspaces/  3: Enhance the Digital Workplace Experience using SAP Work Zone – Overview and Components, https://blogs.sap.com/2021/03/30/enhance-the-digital-workplace-experience-using-sap-work-zone-overview-and-components/

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

An administrative area is a designated space for subject matter experts to manage content and interact within their lines of business. Company administrators assign area administrators to administrative areas. Area administrators have a subset of company administrator capabilities to perform area-related tasks. The company area is created by default and it is the top level of the internal structure of the site. Information on the company level is visible to all users in the company. There can only be one company level. If you want to add multiple subsidiaries or business areas, you can create different administrative areas for them. References:

Administrative Areas

Area & Workspace Configuration

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

 The URL pattern for the Digital Workplace Service component is composed of the following elements:

The subaccount subdomain, which is the name of the subaccount that hosts the service instance.

The work zone type, which is either workzone for SAP Build Work Zone, standard edition, or workzoneadv for SAP Build Work Zone, advanced edition.

The DWS datacenter, which is the region where the service instance is deployed, such as eu10, us10, or ap10.

The suffix cfapps.hana.ondemand.com, which is the domain name for Cloud Foundry applications.

Therefore, the correct URL pattern is https:// .cfapps..hana.ondemand.com.

The other options are incorrect because they do not follow the correct order or format of the URL elements.

References:

Introducing SAP Build Work Zone, Unit 2, Lesson 1, Slide 5

SAP Build Work Zone - Implementation and Administration, Unit 2, Lesson 2, Slide 6

 Content packages enable you to easily install various types of content into your subaccount1. A content package is a collection of content items such as cards, workspace templates, home pages, workflows, and workspaces that are bundled together in a ZIP file2. You can create content packages in SAP Business Application Studio, and deploy them to SAP Build Work Zone using the Development Tools for SAP Build Work Zone extension3. Content packages allow you to bundle development and content artifacts to a single deployable unit (package) that can be easily uploaded and installed in your subaccount. References: 1: SAP Build Work Zone, advanced edition - SAP Online Help 2: Content Packages | SAP Help Portal 3: Create and Deploy Content Packages for SAP Build Work Zone Advanced Edition using BTP | SAP Blogs : SAP Build Work Zone, standard edition - SAP Online Help

UI Integration Cards are reusable components that display information and application content from different backend systems in a unified and consistent way in SAP BuildWork Zone. They can be deployed to SAP Build Work Zone using one of the following methods:

Admin Console in SAP Build Work Zone: This method allows users to manually upload a ZIP file that contains the UI card definition and resources to the Admin Console UI Integration Cards section, using the Upload Card button. Users can also view, edit, and delete the existing UI cards in the Admin Console1.

SAP Business Application Studio: This method allows users to directly deploy the UI card 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 file. This method requires the subscription to SAP Business Application Studio to exist on the same subaccount as the subscription to SAP Build Work Zone, and a token-exchange destination to be configured. Users can also package the UI card into a ZIP file and download it for manual upload, using the UI Integration Card: Package option2.

The methods that are not used to deploy UI Integration Cards to SAP Build Work Zone are:

Command Line Interface (CLI): This method is not supported by SAP Build Work Zone, as there is no CLI tool available for UI Integration Cards development or deployment.

Content Manager: This method is used to manage the unstructured content in SAP Build Work Zone, such as blogs, multimedia, surveys, polls, wiki pages, events, knowledge base articles, tasks, and feeds. It is not used to deploy UI Integration Cards, which are considered as structured content3.

Knowledge base articles can be created in the workspaces Knowledge Base feature, which is enabled by the workspace administrator. The workspace has a Knowledge Base page that displays the knowledge base articles created in the workspace and where users can create knowledge base articles. Users can select a template, insert images, links, and videos, assign a category, and set permissions and publish settings for the knowledge base articles. Users can also view, edit, tag, like, bookmark, and comment on the published knowledge base articles. References:

SAP Build Work Zone, advanced edition | SAP Help Portal, section “Knowledge Base”

SAP Build Work Zone, advanced edition - SAP Online Help, section “Creating, Publishing and Editing Knowledge Base Articles”

 In My Inbox, you can access content from the following components:

Workflows from SAP Build Work Zone: You can process tasks that are created by workflows that you design and run on SAP Build Work Zone. For more information, see Using My Inbox.

Workflows from SAP BTP Workflow Management: You can process tasks that are created by workflows that you design and run on SAP Business Technology Platform Workflow Management. For more information, see Configure My Inbox App.

Notifications from other SAP solutions: You can receive notifications from other SAP solutions that are integrated with SAP Build Work Zone, such as SAP SuccessFactors, SAP S/4HANA, SAP Ariba, and SAP Fieldglass. For more information, see Exploring the Information Architecture. The option B is not correct because notifications from SAP SuccessFactors are not accessed directly in My Inbox, but rather through the integration with SAP Build Work Zone. References:

Using My Inbox

Configure My Inbox App

Exploring the Information Architecture