Which of the following URL pattern represents the Digital Workplace Service component?
https:/ /
https://
https://
https:/ /
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://
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
Which HTML tag does the Web Content Card use to embed internal and external web pages into SAP Build Work Zone workpages?
The Web Content Card uses the
Which artifact must be deleted manually after a content package has been removed?
UI integration cards
Workpage configuration
Workspace templates
SAP BTP destinations
Which of the following can be used to integrate SAP IBP with SAP Build Work Zone? (Choose three.)
UI embedding
Guided Experience
Content Federation
Task Collaboration
Content Package
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/
Which of the following can you use to create user lists in SAP Build Work Zone? (Choose two.)
Digital Workplace Service admin UI
Digital Workplace Service SCIM API
SAP BTP subaccount admin UI
SAP Cloud Identity Service SCIM API
To create user lists in SAP Build Work Zone, you can use either the Digital Workplace Service SCIM API or the SAP Cloud Identity Service SCIM API. Both of these APIs allow you to manage users and groups programmatically using the System for Cross-domain Identity Management (SCIM) protocol. The Digital Workplace Service SCIM API is used to create user lists in the Digital Workplace Service admin UI, while the SAP Cloud Identity Service SCIM API is used to create user lists in the SAP BTP subaccount adminUI. You cannot use the Digital Workplace Service admin UI or the SAP BTP subaccount admin UI directly to create user lists, as they do not provide the option to do so. References:
Creating User Lists
Digital Workplace Service SCIM API
SAP Cloud Identity Service SCIM API
In which of the following product setup steps are role collections created?
Run Booster
Check prerequisites
Perform Post-Booster
Run Work Zone Configurator
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
What can be used to deploy UI Integration Cards to SAP Build Work Zone? (Choose two.)
Admin Console in SAP Build Work Zone.
SAP Business Application Studio.
Command Line Interface (CLI)
Content Manager
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.
Which characteristics are applicable to Launchpad (shell) plugins, but not to UI integration cards? (Choose three.)
They are managed via the administration console of DWS.
The SAP Build Work Zone Advanced extension is required in SAP Business Application Studio.
They are listed in the Content Manager based on the HTMLS content provider setup.
The application logs can be accessed from SAP BTP cockpit.
The source code can be downloaded directly from SAP BTP cockpit.
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 .
What are some actions that external users CANNOT do? (Choose three.)
Create workspaces
Post in workspace forums
Upload a custom profile picture
Share user homepages with other external users
Access My Workspace
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
Which SAP Build Work Zone administrator types require an assignment of a role collection? (Choose three.)
Company administrator
Sub-Workspace administrator
Support administrator
Workspace administrator
Area administrator
SAP Build Work Zone administrator types are divided into three levels: company, workspace, and area. Each level has a corresponding role collection that needs to be assigned to the users who perform administrative tasks at that level. The company administrator role collection enables users to manage the overall SAP Build Work Zone service instance, such as creating workspaces, assigning workspace administrators, and configuring global settings. The support administrator role collection enables users to access the support portal and perform tasks such as viewing logs, monitoring performance, and managing incidents. The workspace administrator role collection enables users to manage a specific workspace, such as creating areas, assigning area administrators, and configuring workspace settings. The sub-workspace administrator and area administrator types do not require a role collection assignment, as they are created and managed within the SAP Build Work Zone content manager by the workspace administrator or the area administrator respectively. References:
SAP Build Work Zone, advanced edition - SAP Online Help
Explaining the Provisioning of Users and Roles in SAP Build Work Zone
Which of the following scenarios applies only to the subscription of SAP Build Work Zone but not to the service instance?
API-based deployment of UI integration cards
Application for users to access the solution
API-based deployment of content packages
Post-booster activation of SAP Cloud Identity Services (IPS)
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
Which of the following key deliverables are part of the SAP Activate Explore phase? (Choose two.)
Integration setup
Fit-to-Standard Analysis
Cloud System Provisioning
Data Load Preparation
The SAP Activate Explore phase is the phase where the project team validates the fit of the standard SAP solution to the customer’s business requirements and identifies any gaps or deltas that need to be addressed1. The key deliverables of this phase are2:
Fit-to-Standard Analysis: This is a series of workshops where the project team demonstrates the predefined scenarios and processes in the SAP solution using the customer’s starter system and sample data. The customer validates the fit of the standard solution to their business needs and identifies any gaps or deltas that require additional configuration, customization, or extension3.
Data Load Preparation: This is the process of preparing the data migration objects and templates, defining the data migration strategy and approach, and performing data quality checks and cleansing. The project team also executes the initial data load to the quality system and validates the results4.
The other options are not part of the SAP Activate Explore phase, but rather of the following phases:
Integration setup: This is part of the SAP Activate Realize phase, where the project team configures and tests the integration scenarios between the SAP solution and other systems, such as legacy systems, third-party applications, or cloud services5.
Cloud System Provisioning: This is part of the SAP Activate Prepare phase, where the project team requests and receives the access to the SAP cloud systems, such as the starter system, the quality system, and the production system6.
References: 1: SAP Activate Elements and Phases | SAP Blogs 2: SAP Activate – Explore Phase: Use Fit-to-Standard to confirm business process fit and identify gaps in your SAP S/4HANA Cloud Implementation | SAP Blogs 3: Fit-to-Standard Analysis | SAP Help Portal 4: Data Load Preparation | SAP Help Portal 5: Integration Setup | SAP Help Portal 6: Cloud System Provisioning | SAP Help Portal
A user cannot access the administration console of SAP Build Work Zone.What could be a reason?
Administrator permission in Digital Workspace Service is missing
SAP BTP global account viewer role collection is missing
SAP BTP subaccount viewer role collection is missing
Space manager permission on SAP BTP subaccount level is missing
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
For a user to access an application that is deployed to SAP BTP (Cloud Foundry), what must be assigned or mapped to the user at the SAP BTP subaccount level?
Group
User list
Role
Role collection
A role collection is a set of roles that are required to access an application or a service in SAP BTP. A role is a granular authorization that defines what actions a user can perform on a specific resource. A user must be assigned or mapped to a role collection at the SAP BTP subaccount level to access an application that is deployed to SAP BTP (Cloud Foundry). A group is a collection of users that share the same attributes, such as department or location. A user list is a way to manage users in the SAP BTP cockpit. Neither of these are related to the access control of applications or services in SAP BTP. References:
Define a Role Collection
Assign a Role Collection to a User
Which SAP Fiori applications does the SAP Workflow service provide for working with workflows in SAP Build Work Zone? (Choose three.)
UI Integration Cards
My Inbox
Monitor Workflows: Workflow Definitions
Workflow Journey App
Monitor Workflows: Workflow Instances
The SAP Workflow service provides three SAP Fiori applications for working with workflows in SAP Build Work Zone1:
My Inbox: This application allows you to access and manage your workflow tasks from different sources in one central place2. You can view, approve, reject, forward, or add comments to your tasks, as well as perform mass actions on multiple tasks2. You can also customize the layout and filter options of your inbox, and use the search function to find specific tasks2.
Monitor Workflows: Workflow Definitions: This application allows you to monitor the status and performance of your workflow definitions3. You can view the details of each workflow definition, such as the version, description, start conditions, and context data3. You can also see the number of workflow instances that are running, completed, or failed for each workflow definition, and drill down to the instance level3.
Monitor Workflows: Workflow Instances: This application allows you to monitor the status and performance of your workflow instances. You can view the details of each workflow instance, such as the start time, end time, duration, and current user task. You can also see the graphicalrepresentation of the workflow model, and the log entries for each step of the workflow execution.
References: 1: SAP Workflow Service 2: My Inbox 3: Monitor Workflows: Workflow Definitions : Monitor Workflows: Workflow Instances
Out of the box, what can you use to integrate Microsoft Teams and SAP Build Work Zone, advanced edition? (Choose three.)
Microsoft Teams application for SAP Build Work Zone
Microsoft Teams chat enabled standalone
SharePoint Online integration for document repositories
Microsoft Teams UI integration cards
Microsoft Teams chat enabled as part of the SharePoint integration
Out of the box, you can use the following options to integrate Microsoft Teams and SAP Build Work Zone, advanced edition:
Microsoft Teams application for SAP Build Work Zone: This is a custom app that you can download from SAP Build Work Zone, advanced edition and upload to Microsoft Teams. It allows you to access and share your workspaces, inbox, and apps from SAP Build Work Zone, advanced edition within Microsoft Teams. You can also chat with your colleagues in Microsoft Teams from your site. For more information, see 1.
SharePoint Online integration for document repositories: This is a feature that enables you to use SharePoint Online as a document repository for your workspaces in SAP Build Work Zone, advanced edition. You can create, edit, and share documents stored in SharePoint Online from your workspaces. You can also use the Microsoft Teams chat feature as part of the SharePoint integration. For more information, see 2.
Microsoft Teams UI integration cards: These are cards that you can use to display information from SAP Build Work Zone, advanced edition in Microsoft Teams. You can create and configure these cards using the UI Integration Card Designer in SAP Build Work Zone, advanced edition. You can also use actions and parameters to enable interactions with the cards. For more information, see 3.
The options that are not available out of the box are:
Microsoft Teams chat enabled standalone: This is not a feature that is provided by SAP Build Work Zone, advanced edition. You can only use the Microsoft Teams chat feature as part of the SharePoint integration or the Microsoft Teams application for SAP Build Work Zone, advanced edition.
Microsoft Teams chat enabled as part of the SharePoint integration: This is not a separate option, but rather a sub-feature of the SharePoint Online integration for document repositories. You cannot enable the Microsoft Teams chat feature without integrating with SharePoint Online.
References:
1: Integrating with Microsoft Teams | SAP Help Portal
2: Integrating with SharePoint Online | SAP Help Portal
3: UI Integration Cards | SAP Help Portal
What must you do as part of the initial product setup? (Choose two.)
Complete configurator steps
Run booster on SAP BTP
Install business content package
Set up trial account
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
Which feed widget setting is used on the home page level to show all public feed updates?
Public
Global
Home
Company
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