Pass the SAP Certified Application Associate C_WZADM_01 Questions and answers with ExamsMirror

UI integration cards are a way to display information and application content from different backend systems in a unified and consistent way in SAP Build Work Zone. They can support operations on the UI, such as choosing the card header or a button, and they can call multiple backend systems using destinations. Destinations are a way to connect to external services or applications using a simple name. They must be maintained at the SAP BTP subaccount level and have the HTMLS.ForwardAuth Token property set to true. This property enables the SAP Build Work Zone to forward the authentication token to the destination service. UI integration cards cannot only consume business data from SAP systems, but also from non-SAP systems, as long as they are accessible via destinations.

For more information about UI integration cards, you can refer to the following resources:

UI Integration Cards | SAP Help Portal1

Direct Deployment of UI Integration Cards to SAP Work Zone | SAP Blogs2

Developing UI Integration Cards | SAP Help Portal3

SAP Build Work Zone, advanced edition - SAP Online Help4

Extensions for SAP Build Work Zone, advanced edition are custom applications that can be developed and deployed to enhance the user experience and functionality of SAPBuild Work Zone, advanced edition. Extensions can be used to integrate data and content from various sources, such as SAP or third-party systems, into SAP Build Work Zone, advanced edition. Extensions can also be used to customize the look and feel of SAP Build Work Zone, advanced edition, such as changing the logo, color scheme, or layout. Extensions can be developed using SAP Business Application Studio or any other development tool that supports the Cloud Foundry environment12.

The scenarios that could be implemented with extensions for SAP Build Work Zone, advanced edition are:

Show a list of flights or hotels booked by the user in the corporate travel system (B): This scenario requires integrating data from an external system (the corporate travel system) into SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to fetch and display the relevant data in a card or a widget on a workpage34.

Change the system logo and color scheme (D): This scenario requires customizing the appearance of SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to modify the system settings, such as the logo, color scheme, or theme5.

Show a list of incidents reported by a user from an on-premise or cloud system (E): This scenario requires integrating data from another SAP or third-party system (the incident management system) into SAP Build Work Zone, advanced edition. This can be achieved by developing an extension that uses the SAP Build Work Zone, advanced edition APIs to fetch and display the relevant data in a card or a widget on a workpage34.

The scenarios that could not be implemented with extensions for SAP Build Work Zone, advanced edition are:

Ensure single-sign-on experience for all users (A): This scenario does not require developing an extension, as SAP Build Work Zone, advanced edition already supports single-sign-on (SSO) for all users. SSO can be configured by the administrator using the SAP Cloud Platform Identity Authentication service.

Create a new link to corporate policies in the user menu ©: This scenario does not require developing an extension, as SAP Build Work Zone, advanced edition already allows adding custom links to the user menu. This can be done by the administrator using the SAP Build Work Zone, advanced edition UI.

References: 1: SAP Build Work Zone, advanced edition - Developer Guide 2: SAP Build Work Zone, advanced edition - Extensions 3: SAP Build Work Zone, advanced edition - Cards and Widgets 4: SAP Build Work Zone, advanced edition - APIs 5: [SAP Build Work Zone, advanced edition - System Settings] : [SAP Build Work Zone, advanced edition - Themes] : [SAP Build Work Zone, advanced edition - Single Sign-On] : [SAP CloudPlatform Identity Authentication service] : [SAP Build Work Zone, advanced edition - User Menu] : [SAP Build Work Zone, advanced edition - Custom Links]

This is a REST API based on the System for Cross-domain Identity Management (SCIM 2.0) specification that allows you to assign roles to users directly inside SAP Build Work Zone1.

Admin UI of the SAP BTP subaccount cockpit: This is a graphical user interface that allows you to assign role collections to users on the SAP BTP subaccount level234.

Attribute mapping for the connected Identity Provider: This is a configuration option that allows you to automatically create shadow users and map role collections based on the Groups assertion attribute from the connected Identity Provider1.

References: 2: https://help.sap.com/docs/build-process-automation/sap-build-process-automation/assign-sap-build-work-zone-roles-to-users  1: 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  3: https://developers.sap.com/tutorials/spa-configure-workzone.html  4: https://help.sap.com/docs/btp/sap-business-technology-platform/assign-users-to-role-collections

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 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

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

External users are the most restricted user type in SAP Build Work Zone, advanced edition. They are guests of your organization and are given access to only the specific private external workspaces to which they have been invited, as well as to their dedicated home pages (for external users) and their user profile1. Therefore, some actions that external users cannot do are:

Create workspaces: External users cannot create workspaces of any type. They can only join workspaces that they are invited to by internal users or other external users2.

Share user homepages with other external users: External users cannot share their user homepages with other external users. They can only view their own user homepage, which shows the workspaces they are a member of and the content they have recently accessed3.

Access My Workspace: External users cannot access My Workspace, which is a personal workspace for internal users where they can store and manage their own content. External users can only access the workspaces they are invited to and the content they are allowed to see4.

External users can do the following actions:

Post in workspace forums: External users can post in workspace forums of the workspaces they are a member of. They can also subscribe to topics, receive notifications, and mark answers as helpful or correct5.

Upload a custom profile picture: External users can upload a custom profile picture for their user profile. They can also edit their profile information, such as name, email, phone number, and bio.

References:

1: External Users - Overview

2: Managing External Users

3: User Home Page for External Users

4: My Workspace

5: Forum Section

: User Profile

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

SAP Business Application Studio is the recommended IDE for developing UI Integration Cards. SAP Business Application Studio is a modular development environment that provides desktop-like experience for developing business applications on SAP Business Technology Platform. It offers a set of tools and templates to create UI Integration Cards easily and efficiently. SAP Business Application Studio also enables direct deployment of UI Integration Cards to SAP Build Work Zone content repository. References:

SAP Business Application Studio

Direct Deployment of UI Integration Cards to SAP Work Zone

Developing UI Integration Cards

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