SAP C_WZADM_2404 Exam Questions

Content package versioning is a feature that allows you to manage the updates of content packages in SAP Build Work Zone. Content packages have three types of versions: major, minor, and patch. Each version has a different impact on the existing content items and configurations. You can choose how you want to update your content packages based on the version type. The available options are:

Automatic update only for patch versions: This option will automatically update your content packages whenever there is a new patch version available. Patch versions are the least disruptive updates that usually fix bugs or improve performance. You will still need to manually update your content packages for major and minor versions.

Manual update for all versions: This option will give you full control over when and how you want to update your content packages. You will need to manually update your content packages for all types of versions: major, minor, and patch. This option is recommended if you have customized your content packages extensively and want to avoid any potential conflicts or errors.

Automatic update for all versions: This option will automatically update your content packages whenever there is a new version available, regardless of the version type. This option is recommended if you want to always have the latest features and enhancements of your content packages. However, this option may also cause some issues or changes in your existing content items and configurations, especially for major and minor versions.

The option that is NOT available for content package versioning is manual update only for minor versions. This option does not make sense because minor versions are more significant updates than patch versions, and they may introduce new features or change existing functionalities. Therefore, it would be illogical to update only minor versions manually and leave patch versions to be updated automatically.Reference:

Content Package Versioning

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 must create 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.Reference:

Accessing SAP Mobile Services Settings

About the SAP Build Work Zone Advanced Mobile App

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.

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.

1:External Users - Overview

2:Managing External Users

3:User Home Page for External Users

4:My Workspace

5:Forum Section

:User Profile

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