SAP Community - SAP Build Work Zone, standard edition

SAP Build Work Zone - Transport Route

2024-02-16T08:56:37.857000+01:00

In this example, we are trying to establish the transport route for the application content type using the build work zone.

In this case we will have Dev, Test, Prod and CTMS subaccounts.

Below will the be structure of the transport setup

Step 1: Create the directories Dev, QA, Prod and CTMS.

Step 2: In the Dev, QA, Prod create the subscription and instance of the SAP Build Work Zone standard Edition.

Step 3: Create service keys for the build Workzone instance in Dev, QA, Prod instances

Step 4: Repeat step 2 and 3 in QA and Prod Subaccounts.

Step 5: in CTMS directory subscribe to the SAP Cloud Transport Management Service.

Step 6: In CTMS directory create an instance of the CTMS with the service key.

Step 7: Copy the service key details, and create a destination in the dev, qa, prod subaccounts, Navigate to the destinations and click on the create destination option and provide the below details

Name : ctms_destination

Description : destination to ctms

URL : copy the URL from the service key of the ctms - uri from the service key

Authentication type: OAuth2ClientCredentials

Client ID: Copy from the service key of the ctms

Client secret: Copy from the service key of the ctms

Token service url: copy from the service key and append /oauth/token

Additional properties : node-name : PORTAL_DEV/PORTAL_QA/PORTAL_PROD

Step 8: in CTMS create destination for Dev, QA, Prod Subaccounts. Copy the service key details of the each of the Build work zone instance and provide the details as below

Name:

Description:

URL: portalservice(from servicekey)+ /cdm_import_service

Client ID:

Client Secret:

Token Service url:

In CTMS,you should have destinations to the Dev, QA, Prod as below

Step 9: Now , navigate the global account ==> Boosters ==> select Configure Access to the Authorization Service ==> create the destination for each subaccount Dev, Qa, Prod,ctms which will be like below

Step 10: Login to the CTMS application and create the nodes as below - the transport node name should match with the node-name of each the destination created in dev, qa, prod subaccounts

Step 11: Create the transport routes from Dev ==> Qa and Qa ==> Prod

Route will look as below:

In this way , we can setup the transport route for the SAP BTP Build Work Zone using the CTMS.

Participate at the SAP Build Hackathon in April 2024

2024-02-20T16:26:02.117000+01:00

Update - March 2024: registrations are closed due to high demand. Thanks for registering and stay tuned for upcoming events!

SAP Build provides the easiest way to extend your SAP systems and to utilize LCNC to build applications and intelligent processes. Now it’s your chance to try out SAP Build and get your hands dirty – because for April 2024 we are offering another Hackathon

which is dedicated to SAP Build Process Automation and SAP Build Apps. This is your opportunity to create business applications or to build your own automation prototype to automate mundane tasks, that occur on your day-to-day business.

Background:

SAP Build addresses the growing gap of developers worldwide by empowering users with any skill level to create applications, automate processes and design engaging business sites. It provides people closest to the business problems The unified low-code portfolio has three core components:

SAP Build Apps – Enables the creation of applications with drag-and-drop simplicity
SAP Build Process Automation – Automates processes and tasks visually
SAP Build Work Zone – Facilitates rapid creation of engaging and personalized business sites

The goal of this Hackathon is to give you a better understanding of our LCNC capabilities and practical introduction to the development environment of Build Process Automation and Build Apps. We are using graphical layout-designer, pre-developed components and Design Thinking to generate a prototype within 3 days of development that you can take back home for further development and investigation. Please keep in mind that we are not going to include Work Zone in this format. If you have your own Work-Zone tenant, you are free to embed your prototypes into your Work Zone tenant by yourself.

During the event, you will meet our experts and learn directly from them. So, you would get access to the state-of-the-art technology, receive professional support and exchange knowledge with your peers from other companies.

Setup:

In this Hackathon we will provide a list of predefined Use-Cases and real-life business challenges which can be realized with SAP Build. You can decide which challenge is most suitable for you and start working on it right away. In order to give you a broad spectrum of our capabilities and to see your requirements reflected in the Hackathon we will include challenges related to workflow-orchestration, RPA-based automation, Machine Learning extraction, Fiori interfaces & mobile development into our challenges. The tool comes with a user-friendly, web-based interface which is absolutely ideal for this format. We are also planning to give presentations, hands-on exercises and involve expert trainers who can support your team if you are stuck.

Register directly via this link:

SAP Build Hackathon (16. – 18. April 2024): https://events.sap.com/eur/sap-build-hackathon/en/home

To see LCNC in action, check out the SAP Low-Code/No-Code Learning Journey – designed to increase low-code/no-code skills and teach citizen developers the basic concepts of software development and learn how to build mobile apps for free. Check out LCNC and Discover BTP plus much more free learning at SAP Learning site:

Stay tuned!

Embedding a Fiori app within another - SAP Build Work Zone, standard edition

2024-02-21T13:00:37.375000+01:00

This blog delineates the process of embedding a Fiori app within another Fiori app deployed in SAP Build Work Zone, standard edition. Here, for clarity, "Fiori apps" refers specifically to applications developed using SAPUI5.

Libraries, Fragments, and Component Containers stand out as the primary options for code reuse in SAPUI5-based Fiori applications. When considering the embedding of one Fiori app (which may be independently deployed) within another Fiori app, the optimal approach is to employ Component Containers, given that Fiori apps are built upon Components.

A Component Container serves as a receptacle for a component, as the name implies. It facilitates the loading of the child Fiori app based on a Component to a designated position within the Parent Fiori App.

When these apps are deployed within the SAP backend as BSP applications, no additional processing is necessary beyond linking both apps using relative paths during the instantiation of the Component Container. The backend system automatically resolves the path and identifies the correct app to load. However, if these apps are independently deployed within the BTP Cloud Foundry environment, and managed descriptors are utilized to register them with Build Work Zone-based portals, the parent app cannot load the child app solely using the relative path.

The pivotal step occurs within the mta.yaml file of the Child App.

Upon deployment of a Fiori App in Cloud Foundry, three service instances are generated by default: Destination Service, App Repository Service, and Authorization & Trust Management Service.

It is essential for the child app to reuse destination service of the parent app to enable resolution of Component Container paths.

mta.yaml file of the Child App needs to be adapted so that it can reuse the destination service of the Parent App.

Modules Section of mta.yaml of Child App:

Resources Section of mta.yaml of Child App:

By configuring these settings, the Component Container specified in the parent app will successfully load the Component from the child app and embed the child App into the Parent App.

Screenshots of an app which uses child app embedding on parent app is given below:

Parent App before embedding:

Child App launched independently:

Parent App with embedding enabled:

[INVITE]: Join us in driving development forward with SAP Build and SAP Build Code

2024-02-21T15:55:30.490000+01:00

[Call to Action] The SAP Customer Engagement Initiative (CEI) is carrying out a project to validate capabilities and concepts around how to create SAP extensions in fusion teams with SAP’s low-code development offering, SAP Build, and the code-based development offering, SAP Build Code. Registration period ends on 8th March 2024. SIGN UP for the CEI project now!

✔ What does this CEI aim to achieve?

In this exciting project, we'll dive into the dynamic synergy between SAP Build and SAP Build Code, uncovering their collaborative potential within fusion development teams, where business experts, key users, and professional developers find their place. We’ll be looking into example scenarios, future concepts, and as for your input on how to improve our offerings so they fit your needs on your transformation journeys.

The following SAP solutions will be in focus:

SAP’s low-code offering: SAP Build with SAP Build Work Zone, SAP Build Apps and SAP Build Process Automation
SAP’s pro-code offering: SAP Build Code

This CEI is for customers looking to speed up their digitization journey into the cloud by learning about extensibility options, and how to power their SAP application and process development with generative AI. This is your chance to give feedback on the current offering and share your use cases and needs to influence the product roadmaps. The CEI will also focus on scenarios which are and potentially will soon be available in the products in focus.

✔ What is SAP´s Customer Engagement Initiative?

SAP Customer Engagement Initiative (CEI) is a part of SAP Customer Influence Program and provides customers with the opportunity to gain early insights into upcoming SAP product development. This means you will get the opportunity to collaborate with SAP experts in adopting innovations early on, provide direct input to the roadmap as well as give feedback to new features.

This initiative facilitates and fosters a close interaction between SAP and its customers through a cooperative model and established legal framework. The customers can support SAP in shaping the future of innovation, making it mutually beneficial for both sides.

✔ What are the next steps?

The customer registrations are open until 8th March 2024. After your successful registration you will receive a welcome email in a few weeks and will be invited to an introductory session with our SAP project leads. This session will focus on answering all your questions and initiate further process. Until this point your participation in the project will be optional.

Please be informed that all customer engagements and activities are governed by the Feedback Agreement with SAP.

🚀Are you ready? JOIN US!

SAP Activate – What’s New in User Experience guidance with SAP Fiori for SAP S/4HANA

2024-02-22T06:45:12.736000+01:00

Good news for those implementing SAP Fiori for SAP S/4HANA!

Over the last couple of months, the SAP S/4HANA RIG team have been hard at work bringing several updates to the User Experience content and accelerators for SAP S/4HANA roadmaps in SAP Activate.

These updates bring the latest information for SAP S/4HANA 2023 (and 2022) releases to your project planning.

The following roadmaps now include User Experience content and accelerators:

What’s Changed?

Much of the UX-related task content has been updated in SAP Activate Methodology for RISE with SAP S/4HANA Cloud Private Edition.
Several accelerators have been updated and shared across multiple related roadmaps. Here’s a quick summary of what’s changed.

Below you will find a quick summary of what to use when you are:

Getting started with SAP Fiori for SAP S/4HANA
Want to see an examples of how experts introduce UX
Planning to demonstrate SAP Fiori
Planning your SAP S/4HANA upgrade
Moving to Spaces and Pages layout
Looking to grow your usage of SAP Fiori
Looking to add SAP Build Work Zone and SAP Mobile Start
Want more User Experience advice in SAP Activate

P.s. Much of the content in SAP Activate related to system conversions has also been updated by the SAP S/4HANA RIG team. You can find more about the other updates in blog post News from SAP Activate SAP S/4HANA Cloud Public Edition 2402

Getting started with SAP Fiori for SAP S/4HANA ?

Not sure how to explain User Experience to your business?

You’ll find some useful slides and preparation ideas in UX Adoption: Establish the Business Value of UX Workshop (Public)

Want to see an examples of how experts introduce UX?

See how I do it in the openSAP course SAP S/4HANA UX for Business and Functional Experts. Missed it? No problem! Join the course self-paced.

Review the video:

Unit 1: How to explain the value of SAP Fiori

Planning to demonstrate SAP Fiori?

You will find it very helpful to review the SAP Fiori: Tips & Tricks for Users of SAP S/4HANA which is also listed in the SAP Activate accelerators.

You will need a User Experience Strategy to set your baseline expectations, architecture, features, and tools. Accelerator User Experience Strategy Template (Public) now contains much more assistance, along with some Guiding Principles to help you keep your team human-centred.

Want to discuss your UX Strategy with your business?

Accelerator UX Adoption: UX Strategy and Guiding Principles Workshop (Public ) now has a flipbook-style section showing how to make cross-functional feature in/out of scope decisions with your team.

Planning a SAP S/4HANA upgrade ?

Take a look at SAP Activate roadmap SAP Activate Methodology for SAP S/4HANA Upgrades

Even if you are going for a technical upgrade approach, you will still need to revisit your UX Strategy and launchpad feature usage. This ensures you cover any mandatory changes due to:

New, changed, or deprecated launchpad features
Obsolete, deprecated, or superseded apps
New, changed, or deprecated launchpad administration tooling

Accelerator UX Adoption: UX Strategy and Guiding Principles Workshop (Public ) shows how to make cross-functional feature in/out decisions with your team, and document the reasons for change. Accelerator User Experience Strategy Template (Public) has the latest best practices for launchpad features and administration tooling.

Missing some advice on upgrading your SAP Fiori for SAP S/4HANA? Please let us know what else you need in the comments.

Moving to Spaces and Pages layout?

You will find some suggestions on how to get started in UX Adoption: How to approach Design your Launchpad Layout Workshop (Public)

Doing a deeper dive with blog post Info Package: Making the Move from Launchpad Groups to Spaces (In SAP S/4HANA and in SAP S/4HANA Cloud, private edition)

Looking to grow your usage of SAP Fiori ?

Looking for ideas on which apps to use?

You will find updated guides for selecting apps by UX Value at UX Value Goal App Selection Guides (Public)

With more than 3K apps, even with suggestions from tools such as SAP Signavio Process Insights, and Readiness Check, you’ll need a way to narrow down the focus.

The UX Adoption Planning process shows how to have a now/next/later discussion to engage with your business stakeholders.

You can find an introduction to the major steps in openSAP course SAP S/4HANA UX for Business and Functional Experts. Missed it? No problem! Join the course self-paced.

Review the videos:

You will find the entire matching series of updated workshop templates in SAP Activate. You will even find some suggestions on which major decision points to focus on at each stage to keep it simple.

Use it all or just whatever helps you move forward. That’s the intention ... and how other customers tell us they are using the content.

Looking to add SAP Build Work Zone and SAP Mobile Start?

With SAP S/4HANA focus on SAP Build Work Zone, standard edition.

You will find the latest guidance and suggestions at SAP Community topic page for SAP Build Work Zone

As a first step, you should review the latest architecture guidance announcements in blog post SAP Fiori Deployment Options and System Landscape Recommendations

You will find some suggestions on where to incorporate SAP Build Work Zone in your UX Strategy in accelerator User Experience Strategy Template (Public). You can engage your business on your SAP Build Work Zone journey by using the Cross-Functional Feature Decisions approach shown in accelerator UX Adoption: UX Strategy and Guiding Principles Workshop (Public )

Then get the latest news on what’s possible by reviewing the latest roadmap blog posts from SAP such as:

SAP UX Innovations in Public Cloud Products, Joule, AI, Entry Points, Apple Vision Pro and more

Want more SAP Activate updates for User Experience?

Whew! There’s a lot of content in SAP Activate so if you see something that needs improving, please let us know in the comments!

Don't forget to use the User Experience tag (in the left-hand filter pane) of SAP Activate to find the rest of the recommended UX content and accelerators already available in SAP Activate.

Find out more about SAP Activate on the SAP Activate topic page.

Follow the SAP Activate page on the SAP Community. Remember to turn on your notification to receive updates or information about items requiring your attention.
Tune into the SAP Activate Minute videos in our SAP Activate Playlist. Subscribe to get notified when we drop new videos. We have big plans to add interesting new topics.

Find more from the SAP S/4HANA RIG team via tag S4HANA RIG

Find more on UX at our SAP Fiori for SAP S/4HANA topic page

Witness Thomas Volmering Unveil Fusion Development: SAP Build in Action

2024-02-27T14:17:58.537000+01:00

In the fast-paced world of ERP, innovation isn't just about introducing new features: innovation is about optimizing existing systems while preparing for future demands. A recent webcast led by @Thomas on February 15 delved into this very topic, showcasing the power of SAP Build and SAP Build Code.

However, beyond just demonstrating features, the session provided valuable insights into strategies for maintaining a clean core and extending on SAP BTP.

Clean Core Strategy

The concept of a "Clean Core" was a central theme throughout the webinar. This approach emphasizes keeping the core system as standard and untouched as possible. With a Clean Core strategy, organizations can ensure that their ERP systems remain agile and adaptable to changing business requirements. Upgrades become easier, requiring less manual effort for testing and adapting existing structures.

Streamlined development of extensions and tailored functionalities on SAP BTP with SAP Build simplifies the extension creation process, expediting time-to-market and promoting collaborative efforts.

Fostering Collaboration through Fusion Teams

The concept of collaboration brings Fusion Teams, where individuals with varying expertise collaborate seamlessly toward common goals. Fusion Teams represent a departure from traditional siloed approaches to software development. By bringing together diverse skill sets and perspectives, these teams foster collaboration and creativity, resulting in solutions that are not only technically robust but also closely aligned with business objectives.

A key enabler of collaboration within Fusion Teams is the lobby area of SAP Build – a central hub for fusion development. Here, team members can seamlessly consume components created with SAP Build Code, leveraging the power of pro-code efficiency within the intuitive framework of low-code simplicity. This integration empowers teams to rapidly prototype, iterate, and deploy solutions, accelerating time-to-market and ensuring alignment with business objectives.

Insights for Innovation

If you're ready to unlock the full potential of your ERP system and to drive innovation within your organization, consider utilizing the insights shared in this webinar. Explore SAP Build and SAP Build Code on YouTube to discover how you can maintain a clean core, streamline development, and foster collaboration through Fusion Teams.

To stay updated throughout the year on Application Development and Automation on SAP BTP, regularly browse our public roadmaps for SAP Build + SAP Build Code and… feel free to follow Thomas here on SAP Community and/or on LinkedIn to be notified of his next blog posts!

What is new for SAP Build Work Zone? Product Highlights in January and February 2024

2024-03-05T11:26:01.183000+01:00

Welcome to my first product update of the year 2024. This blog post will provide you with the product news and highlights for SAP Build Work Zone in January and February 2024.

You might know what SAP Build Work Zone is? If not, here is a short introduction: SAP Build Work Zone empowers IT professionals and line of business experts to easily build and design engaging business sites for employees, partners and customers with intuitive drag-and-drop functionality. It connects to all systems (SAP a non-SAP) by creating a single access point to applications, processes, information and data on any device,from desktop or mobile, and it maximize team productivity by enabling guided experiences and knowledge sharing.
SAP Build Work Zone is coming with two editions: SAP Build Work Zone, standard edition and SAP Build Work Zone, advanced edition. The latest addition to the SAP Build Work Zone family is SAP Start, which became generally available in July 2023. If you have more questions on SAP Build Work Zone, visit our FAQ page on SAP Community.

Roadmap Updates

We recently updated the roadmap for SAP Build Work Zone standard and advanced edition. You can find updated information for Q1, Q2 and Q3 2024:

Note that the information on the roadmap can be subject to change at any time, check out the Roadmap Explorer for the latest information.

Administration Experience

SAP Build Work Zone, standard edition

Translation in the new site experience with pages and spaces:
The translation capabilities are now available in the productive systems: Content managers can enable end users to view their sites in selected language, and they can support the translation of spaces and pages:

Role Assignments by usage of Identity Provisioning
For role assignments, there is now an alternative option that we recommend: using the identity provisioning part of SAP Cloud Identity services, instead of creating role collections:

This new capability allows to provision the user role mapping from a source system - such as as SAP S/4HANA - directly into the Work Zone stack via an dedicated API. Note that this new role assignment option is available across all Work Zone editions as well as for SAP Successfactors Work Zone.
There is a new Admin UI that allows the administrator to analyze the roles that were assigned to a specific user and provisioned by the Identity Provisioning service of SAP Cloud Identity Services.

Support of new common Super Domain workzone.cloud.sap
The new workzone.cloud.sap common super domain is now supported to bring applications under one aligned domain name. Administrators can configure the workzone.cloud.sap common super domain for exposing a site instead of using the default ondemand.com domain. In the first step this features is only available for the standard edition, the introduction of super domain is planned for the advanced edition in upcoming releases.

SAP Build Work Zone, advanced edition

New Wizard Layout in Workspaces
This feature is now also available in productive systems (in Q4 2023 it was only available in the preview systems). Workspace administrators can create wizard-like predefined processes, to help users complete complex business flows. The wizards can include multiple stages and steps, and cards and widgets can be added to them.
By providing a flexible framework for defining process steps and by enabling content managers to create and configure UI card-based, interactive experiences, business users can be guided through a wizard-like predefined process:

Public Workspaces: Access Levels for Non-Members
A non-member visibility is now available for workspaces to give non-members access to the workspace content. Workspace admins have the choice: (1) to give non-members the same collaboration settings as members or (2) to use a new read-only mode for non-members. This will hide the different membership & collaboration related features for the non-members across the workspace and its content. Workspace administrators can define specific users lists and users who can access the workspace as non-members. This is only available for public workspace as a first step.

Public Workspace: Role-Based Access for Non-Members
Company administrators can define role-based access to workspaces for non-members. Workspace admins, who are not company admins, can view the settings but cannot modify them. To set this option, you go to the Participation tab of the workspace settings, then go to the Non-Member Settings section, and in the Access Policy options you choose Specific roles.

Integration with Notification Service and Task Center
Site administrators can choose whether to use the default notification mechanism available in their site, or to enable the integration with the central notification service of SAP BTP, and show notifications from multiple notification providers. One of the supported notification providers is now also SAP Build Work Zone, advanced edition.

Note that - as part of this change - some notifications will be migrated to the Task Center. On the Help Portal you will learn about notifications that were previously visible in the notifications area of a site and are now moved to SAP Task Center.

With the support of dynamic KPI tiles, you can now see Task Center information on tiles in this way:

Business User Experience

SAP Companion Content - Expanded Support (only relevant for the advanced edition)
SAP Companion provides on-screen help for end users. Activating this capability enables end users to view help content, that is specific to the screen. Additional integration content is now added out of the box, provides on-screen help, documentation & selected guided tours.

Developer Experience

We are happy to announce a Central GitHub repository for SAP Build Work Zone providing templates for SAP Build Work Zone code samples as a starting point for developers:

For the standard edition the repository contains content package samples providing information about how to create custom content for SAP Start and SAP Build Work Zone, standard edition (new site experience). UI Integration Cards and the corresponding CDM (Common Data Model) descriptions are covered within this samples. For the advanced edition the repository contains code samples for these two main areas: Content Package and Guide Experience (Wizard).

Deploying a SAP Build App project with backend to SAP Build Work Zone
For applications that include a backend project in visual cloud functions, we have now introduced a simplified method for integrating with SAP Build Work Zone. For more information and instructions, check out the blog post What's New for SAP Build Apps - Enhanced Fusion Development.

What is Coming Next?

I would like make you aware of some upcoming new innovations for SAP Build Work Zone, advanced edition. A new workspace creation dialog is planned as well as the removal of external workspace as a separate workspace type combined with a consistent experience between private and public workspaces. The access control concepts will be expanded, and external users can access public and private workspaces both as members and non-members.
The full feature set supporting this innovation is planned to become available in the preview systems in March 21, stay tuned for further information. You can find more details already now in the What's New Viewer, see also this blog post explaining some of the new concepts.

More Information on new Features and Functions

Check out the roadmap for standard & advanced edition.
You can find more information in the What is new Viewer for standard edition and advanced edition.
The availability date of the new features on the preview systems and the information about how to use them can be found in the What's New on Preview Systems.

Learn more

SAP Build Work Zone on: sap.com / SAP Community
Discovery Center missions: standard / advanced edition
SAP Build Work Zone on SAP PartnerEdge

Follow SAP Build on Social Media and Join the SAP Builders Group

Twitter (hashtag #SAPBuild)
LinkedIn

Join also the SAP Builders group and engage with a community of peers to unleash innovation by building apps, process automations, and creating business sites.

Tips to add your SAP Build Apps application to different BTP environments - Part 1

2024-03-08T16:51:01.697000+01:00

Hi SAP Builders!

In this blog post, I will showcase 'how to add your deployed SAP Build Apps application to different environments in SAP BTP (Business Technology Platform).

In Part 1, let's see how to do this when all the required services (SAP Build Apps, SAP Build Work Zone, Standard Edition) are running as part of the same Subaccount in BTP.

Pre-requisites

You are familiar with creating an application using SAP Build Apps and deploying it to the CF (Cloud Foundry) Space of your Subaccount.

For your quick reference, access the SAP Discovery Center and check out the mission ‘Keep the Core Clean Using SAP Build Apps with SAP S/4HANA’. Here in the area ‘Project Board’ under the section ‘DEVELOP’ you can find a tutorial to ‘Create a No-Code Application using SAP Build Apps’.

You may also refer to the SAP Build Apps help portal content to learn about Building a SAP Build Apps application and deploying it.

Verify that the newly deployed app is available in your Subaccount

Before we add your application to the different BTP environments, let us verify that the right version of the app is available in your BTP Subaccount.

For this you need to look up for your app in the HTML5 Applications repository section of your BTP Subaccount.

Spoiler

The direct url of the deployed application can be always found here!
Take a note that the Application Name is constructed as a concatenation of 'buildapps' with your SAP Build Apps project id: '86796'

The direct url of the deployed application can be always found here!Take a note that the Application Name is constructed as a concatenation of 'buildapps' with your SAP Build Apps project id: '86796'

Hint: It is also possible to launch and test the application from here.

Integrate your SAP Build Apps application to SAP Build Work Zone, Standard edition

Preparations before integration!

Select the SAP Build Work Zone, standard edition from the list of subscription.

NOTE: Only users assigned to the Role Collection: Launchpad_Admin have access permission to SAP Build Work Zone, Standard Edition to create artifacts at design time.

Refer to Initial Setup | SAP Help Portal -> Procedure-> 3. Assign users to the Launchpad_Admin role collection for some hints in case of any issues while accessing the SAP Build Work Zone, standard edition in the first place.

From the Channel Manager, refresh the HTML5 Apps to update it with the newly deployed app content.

Next, we need to access the Content Manager and go to the Content Explorer and select the HTML5 Apps from there.

Here you should be able to find your newly deployed SAP Build Apps application!

To add your application to the content of this Subaccount, select it and click on Add.

Finally, add this application to all the required roles of your end user via Content Manager -> Roles and save it as illustrated below.

Now, we are good to get started with adding the application to the different flavors in the SAP Build Work Zone, Standard Edition.

Spaces and Pages New Experience

Create a Site using Site Manager, choose the Display mode 'Spaces and Pages - New Experience and add all the necessary settings for this Site and save it.
Create a Page and add the application to it.
Create a Space and add the Page to it.
Add the Space to the Role.

Go to Site settings and add all the required role(s) containing this app and this space to the Site and to the end user via BTP Cockpit.
Check the Site for this app under this Space and Page and launch it at runtime.

Classic Launchpad with Groups

Create a Site using Site Manager, choose the Display mode 'Groups' and add all the necessary settings for this Site and save it.

Create a group or select an existing Group and add the application to it.
Check for the app under this group in the Site and launch the app at runtime.

(OR)

Create or select an existing Catalog and add the application to it.
Go to the Site settings and add all the required role(s) containing this app to the Site and to the end user via BTP Cockpit.
Edit the Launchpad and select the app from Catalog to add it to a new group or under any existing group.
Click on back button or navigate via SAP logo to Home page and launch the app from runtime.

New Launchpad with Spaces and Pages

Create a Site using Site Manager, choose the Display mode 'Spaces and Pages' and add all the necessary settings for this Site and save it.
Create or select an existing Catalog and add the application to it.

Go to the Site settings and add all the necessary role(s) containing this app to the Site and to the end user via BTP Cockpit.
Edit the Launchpad and select the app from Catalog to add it to a new section or under any existing section.
Click on back button or navigate via SAP logo to Home page to launch the app from runtime.

With this, I hope that you would also be able add your deployed SAP Build Apps application to SAP Build Work Zone, Standard Edition.

Spoiler

Coming up next ...
In the Part 2 blog, you will learn to add your deployed SAP Build Apps application to SAP Build Work Zone, Advanced Edition.

Coming up next ...In the Part 2 blog, you will learn to add your deployed SAP Build Apps application to SAP Build Work Zone, Advanced Edition.

Stay tuned and Happy building!

Leverage SCIM APIs of SAP Build Work Zone to view users and groups provisioned into Work Zone

2024-03-12T21:42:39.965000+01:00

In my earlier blog I explain how we can use SAP Cloud Identity Provisioning Service to read users/groups from remote content provider such SAP Business Technology Platform, ABAP Environment into SAP Build Work Zone. The advantages of why you may consider doing this are explained in my earlier blog. There are other reasons why you may need to provision users in SAP Build Work Zone. For eg. to leverage SAP AI service called Joule(see blog) with your SAP SuccessFactors suite requires users and groups to be provisioned from SAP SuccessFactors into SAP Build Work Zone.

SAP Build Work Zone standard or the foundations edition recently released a user interface to search for a user and see it's assigned groups. For more details on this feature refer to the help guide. The feature mentioned in the help guide is probably where you should start, but there are certain scenarios where it may not be sufficient and that's where we can leverage the SCIM APIs offered by Work Zone. The purpose of this blog is to showcase how we can use the SCIM APIs of SAP Build Work Zone to read which users and groups are provisioned into SAP Build Work Zone. SAP Build Work Zone has a standard SCIM interface we can leverage to accomplish this.

To setup the request with your rest client, follow the process below. Exact steps might be different for other rest clients but the process should be same.

Access your SAP BTP subaccount where you have an instance of SAP Build Work Zone.
Click the key created for your Work Zone instance. If you don't have a key, follow my previous blog to understand the steps on how to create a new key.
Make note of the following fields:
- endpoints -> portal-service
- uaa -> clientid
- uaa -> clientsecret
- uaa -> url
Open a rest client and configure the Get request as follows to read provisioned users from SAP Build Work Zone. I am using Postman as my client, but you can use any other rest client of your choice.
- URL: <endpoints -> portal-service>/roleMapping/scim/v1/Users for eg. https://portal-service.cfapps.us10.hana.ondemand.com/roleMapping/scim/v1/Users
- Authorization
  - Grant-type: Client Credentials
  - Access Token URL: <uaa -> url>/oauth/token for eg. https://workzone-uf9rmd8s.authentication.us10.hana.ondemand.com/oauth/token
  - Client ID: uaa -> clientid
  - Client Secert: uaa -> clientsecret
Get a new access token.
Use the token in your request.
Send the request and confirm the users are read from SAP Build Work Zone. See screenshot below on type of user information that is returned.

For reading groups, change the URL to <portal-service>/roleMapping/scim/v1/Groups.

To read a specific user, add a filter using email or externalID. For eg:

https://portal-service.cfapps.us10.hana.ondemand.com/roleMapping/scim/v1/Users?filter=emails.value eq "harjeet.judge@sap.com"

https://portal-service.cfapps.us10.hana.ondemand.com/roleMapping/scim/v1/Users?filter=externalId eq "fee8b135-502c-49dd-bf1b-10499cc05754"

It may also be useful to filter for users tied to particular providerId. Eg.

https://portal-service.cfapps.us10.hana.ondemand.com/roleMapping/scim/v1/Users?filter=urn:ietf:params:scim:schemas:extension:2.0:mapping.providerId eq "Tutorial"

Note: By default the Identity Provisioning Service writes only minimal user attributes to SAP Build Work Zone so the user information that can be pulled back using the API is minimal.

To write a user in SAP Build Work Zone, send a POST request with the appropriate user/group payload.

Note: A POST request from a rest client should really be only used for troubleshooting. For actually provisioning users/groups into SAP Build Work Zone, you should be leveraging the SAP Cloud Identity Provisioning service as described in the blog link I shared earlier. If for some reason certain users fail to provision during Identity provisioning job, in those scenarios it may be helpful to test writing that user to SAP Build Work Zone through a rest client like Postman. See an example POST request in the screenshot below:

Happy reading!

Tips to add your SAP Build Apps application to different BTP environments - Part 2

2024-03-15T13:46:29.333000+01:00

Hi SAP Builders!

This is a follow up blog to Tips to add your SAP Build Apps application to different BTP environments - Part 1 and here I will continue to showcase 'how to add your deployed SAP Build Apps application to different environments in SAP BTP (Business Technology Platform)', when all the required services (SAP Build Apps, SAP Build Work Zone, Advanced Edition) are running as part of the same Subaccount.

Integrate your SAP Build Apps application to SAP Build Work Zone, Advanced edition

Preparations before integration!

Ensure that the SAP Build Work Zone, advanced edition is available in the list of subscriptions and is accessible.

Spoiler

Users need to be assigned to at least the following 2 role collections to be able to create artifacts at design time in SAP Build Work Zone, Advanced Edition and access it later at runtime.

Workzone_Admin

Workzone_End_User

Refer to Onboarding to SAP Build Work Zone, advanced edition - Setup and Configuration ,[SAP BTP Onboarding Series] - Step-by-Step guide to activate your SAP Build Work Zone, Advanced Edition for some helpful hints in case of any issues while accessing the SAP Build Work Zone, advanced edition in the first place.

For additional detailed reference feel free to consult the Implementing and Administering SAP Build Work Zone | SAP Learning - Explaining the Implementation Methodology - Explaining the Prepare Phase and About Administrators | SAP Help Portal.

Users need to be assigned to at least the following 2 role collections to be able to create artifacts at design time in SAP Build Work Zone, Advanced Edition and access it later at runtime.Workzone_AdminWorkzone_End_UserRefer to Onboarding to SAP Build Work Zone, advanced edition - Setup and Configuration ,[SAP BTP Onboarding Series] - Step-by-Step guide to activate your SAP Build Work Zone, Advanced Edition for some helpful hints in case of any issues while accessing the SAP Build Work Zone, advanced edition in the first place.For additional detailed reference feel free to consult the Implementing and Administering SAP Build Work Zone | SAP Learning - Explaining the Implementation Methodology - Explaining the Prepare Phase and About Administrators | SAP Help Portal.

Design-time setup

Access the SAP Build Lobby and select the option to create a business Site, ‘Build a Business Site.’

Further select the option to ‘Configure Site Content.’
Switch to Channel Manager.
From the Channel Manager, refresh the HTML5 Apps to update it with the newly deployed app content.
Next, we need to access the Content Manager and go to the Content Explorer and select the HTML5 Apps from there.

Here you should be able to find your newly deployed SAP Build App application. To add your application to the content of this Subaccount, select it and click on add.

Finally, add this application to all the required roles of your end user via Content Manager -> Roles and save it as illustrated below.

Now, we are good to start with adding your application to SAP Build Work Zone, Advanced Edition, Business Site.

Add and access the application at run time

Access the SAP Build lobby again, this time click on the option ‘Manage Workpages and Workspaces’.
Create a ‘New Workspace’.
Provide the required details and click on create.
Alternately you can also edit an existing Workspace.
Create a Workpage and save it.
Alternately you can just access the Home page and add your content it.
Add a section and add a widget to it.
Here, our SAP Build Apps application can be found under the widget type 'Tiles'.
Select your SAP Build Apps application and add it.
Finally publish it.
Now, we can launch our application by clicking on the Tile.

Spoiler

Design Your First SAP Build Work Zone, Advanced Edition Business Site | SAP Tutorials
SAP Build Work Zone | SAP Community

As our goal is to add a deployed SAP Build Apps application to our Work Zone Site, we did not deep dive further into enhancing it. If this is interesting for you, please refer to the following materials on SAP Build Work Zone, Advanced Edition to explore further.Design Your First SAP Build Work Zone, Advanced Edition Business Site | SAP TutorialsSAP Build Work Zone | SAP Community

With this, I hope that you would also be able to add your deployed SAP Build Apps application to SAP Build Work Zone, Advanced Edition.

Spoiler

Coming up next...
In the Part 3 blog, you will learn to add your deployed SAP Build Apps application to different environments in SAP BTP (Business Technology Platform), when the SAP Build Apps service is running as part of a different subaccount in your global account (or) running as part of a different global account.

Coming up next...In the Part 3 blog, you will learn to add your deployed SAP Build Apps application to different environments in SAP BTP (Business Technology Platform), when the SAP Build Apps service is running as part of a different subaccount in your global account (or) running as part of a different global account.

Stay tuned and Happy building!

SAP BTP - A Deep Dive into SAP Build Capabilities

2024-03-21T15:36:03.932000+01:00

A Deep Dive into SAP Build Capabilities

Citizen development is transforming the way businesses build applications. SAP BTP Build sits at the forefront of this movement, empowering everyone, not just professional coders, to create custom applications that address specific business needs. In this comprehensive blog, we'll delve into the intricacies of SAP BTP Build, exploring its core services, functionalities, and the benefits it offers.

Demystifying SAP BTP Build: A Suite of Powerhouse Services

SAP BTP Build isn't just a single tool; it's a unified platform housing three robust services, each catering to distinct application development needs:

SAP Build Apps (formerly SAP AppGyver):
- Visual Development Paradise: Unleash your creativity with a drag-and-drop interface. Build web and mobile applications intuitively, using pre-built components and functionalities. No coding experience required!
- Seamless Integration: Connect your applications seamlessly with existing SAP and non-SAP systems using pre-built connectors and APIs. This eliminates the need for complex integrations, saving time and resources.
- Offline Functionality (Mobile Apps): Keep your mobile applications operational even without an internet connection. This ensures uninterrupted workflows and enhances user experience, especially in scenarios with limited connectivity.
- Advanced Features: For those with a coding background, SAP Build Apps offers JavaScript extensions for more granular control and customization.
SAP Build Process Automation (formerly SAP Process Automation):
- Wrangle Repetitive Tasks: Feeling bogged down by repetitive tasks? Automate them with SAP Build Process Automation!
- Intuitive Flow Builder: Design automated workflows visually using a user-friendly interface. Connect various steps, decision points, and actions to streamline complex processes.
- Pre-built Connectors: Leverage pre-built connectors to integrate with diverse systems like SAP S/4HANA, Salesforce, and more. This eliminates the need for custom coding and accelerates automation implementation.
- Advanced Monitoring and Error Handling: Track the performance of your automated workflows, identify errors promptly, and configure robust error handling mechanisms to ensure smooth operation.
SAP Build Work Zone (formerly SAP Work Zone and SAP Launchpad service):
- Centralized Information Hubs: Create captivating business sites with SAP Build Work Zone. These sites serve as central hubs, providing users with easy access to information, applications, and processes.
- Branding and Customization: Tailor the look and feel of your business sites to match your company's branding. Embed logos, customize colors, and layouts to create a cohesive user experience.
- Single Sign-On Integration: Streamline user access by integrating SAP Build Work Zone with your existing single sign-on (SSO) solution. This allows users to access all applications and resources with a single login.
- Personalization Capabilities: Cater to individual user needs by personalizing the content and functionality of business sites. Deliver a more relevant and engaging experience for each user.

Unveiling the Benefits of SAP BTP Build: A Citizen Developer's Dream

By leveraging SAP BTP Build, businesses can unlock a treasure trove of benefits that empower employees and streamline operations. Let's explore some key advantages:

Empowering Citizen Developers: Bridge the gap between business needs and IT capabilities. Anyone can now build applications without writing code, fostering a culture of innovation and problem-solving across the organization.
Increased Productivity: Automate manual tasks and streamline workflows, freeing up valuable time for employees to focus on more strategic initiatives. Employees can also build custom tools to enhance their daily tasks, leading to significant productivity gains.
Enhanced Agility: Respond quickly to changing business requirements by rapidly building and deploying custom applications. This allows businesses to adapt to market shifts and seize new opportunities with greater agility.
Improved User Experience: Build applications with a user-centric approach. SAP BTP Build's visual development tools ensure applications are intuitive and user-friendly, leading to higher user satisfaction and adoption rates.
Reduced Development Costs: Eliminate the need for extensive coding resources and complex development environments. Build applications faster and at a lower cost compared to traditional development methods.

Who Can Benefit from SAP BTP Build? A Wide Spectrum of Users

The beauty of SAP BTP Build lies in its accessibility. Here's how different user groups can leverage the platform's capabilities:

Business Users: Build custom dashboards, reports, and approval workflows to streamline their daily tasks. Imagine a sales manager creating a mobile app to track leads on the go or a finance professional building a dashboard for real-time budget insights.
HR Professionals: Automate onboarding processes, manage leave requests, and build self-service portals for employees

To delve deeper and explore more use cases relevant to your organization needs, technical configurations for complex scenarios or to know more on value add feel free to connect.

Design of the new Apple Vision Pro App for SAP Mobile Start

2024-04-02T12:48:50.763000+02:00

The new Apple Vision Pro App for SAP Mobile Start is officially out! 🎉

Screenshot – SAP Mobile Start for Apple Vision Pro

3 months ago, around mid of October, we began designing and building SAP Mobile Start for a completely new and innovative platform: Apple Vision Pro. We made the first steps in the snow and explored the next era of spatial computing together with Apple.

From a design point of view, the past few months were super exciting and filled with new learnings. We had dived into a completely new design system consisting of translucent materials that needed to work against real-world environments with different light and background conditions. Apple Vision Pro offered new ways of navigating a UI by only using your eyes, hands, and voice.

Gestures in visionOS - Apple WWDC 2023, Designing for spatial input

Before we could design our own app on Apple Vision Pro, we first needed to understand the foundations of spatial design by researching best practices for this new territory. For that, we studied the deep dive sessions from Apple’s WWDC Vision Pro announcement, their first human interface guidelines for visionOS, the UIKit for visionOS and the headset’s hardware capabilities in general.

UI Kit for visionOS

Screenshot – Apple’s visionOS guidelines

Now you could ask “Why not just port the existing iPad app to visionOS?”. In theory, this would have probably been the easiest way to publish an app for Apple Vision Pro. We soon learned that even though visionOS and iPadOS have many similarities, visionOS has unique needs when it comes to interaction and visual design. To create a visionOS app with the best user experience, you must consider platform specifics and follow the respective patterns for that environment.

WWDC 2023, Principles of spatial design & Design for spatial input

visionOS Design – Best Practices

For us, that meant challenging some of the concepts we already had on the iPhone, iPad, and Apple Watch and re-think them for Apple Vision Pro. One example for this was the whole re-organization of the top-level app navigation and secondary navigation targets. We experimented with ornaments, three-pane layouts, extra windows, dialogs, and lastly the sidebar to optimize the experience of SAP Mobile Start for the Infinite Canvas of Apple Vision Pro. The introduction of the sidebar required a re-design of several patterns like to-do details or insight card details. It also had an impact on our existing iPad app.

Screenshot – To-Do Details Screen

Old draft – To-Do Details as separate window

With the help of dedicated concept review sessions with our developer support contacts at Apple, hands-on test sessions, and peer reviews with our design experts from the mobile design systems team, we managed to nudge our concept into the right direction and finalize it in a very short time.

To finish the app for the launch of Apple Vision Pro, we needed a small team that was able to take fast decisions and quickly react. During this time, our core team – consisting of our two lead iOS developers and myself as the lead UX designer – collaborated very closely and synced daily or even sat together in one meeting room. We designed and developed in real-time and discussed new ideas together. This short feedback-loop helped us detect technical limitations and unfeasible designs at a very early stage.

After the app development was finished and visuals for featuring the app had been provided, the SAP Mobile Start app for Apple Vision Pro was ready to be shipped to the App Store on Feb 2nd.

Mockup – SAP Mobile Start in the App Store

But as we all know: A good product is never finished. Stay tuned for updates to SAP Mobile Start for visionOS in the future!

If you want to know more about our 1.10 release, have a look at our release article here.

----------------------------------------------------------------------------------------------------------

For further information on the new topics, please check our SAP Mobile Start documentation on SAP Help.

SAP Mobile Experience offers intelligent native mobile solutions that help businesses build more efficient, resilient and sustainable end-to-end processes, improving people’s work life wherever they are.

Visit SAP Mobile Experience Community Page and click “follow” to get the latest development and innovation of our solutions. We look forward to hearing your experience with setting up the solution in your landscape; please do share your thoughts and comments below. Enter here for additional questions regarding SAP Mobile Experience Applications. Want to be notified? Check your profile settings to ensure you have your settings activated.

How to develop Customer creation Application in SAP Build Apps with OData service

2024-04-05T16:34:12.935000+02:00

Objective: -

Implementing SAP OData URI to SAP Build and Creating Customers in SAP BUILD which can replicate to SAP System

Business Scenario: -

How to create Customers using SAP Build Apps and OData Service.

Prerequisites: -

-> You Have an SAP BTP account or trial account.

-> Inside the BTP account, go to Instances and Subscriptions and create an instance of SAP Build Apps

-> Now go to Security -> Users Tab and assign Role to the user for SAP BUILD Apps

Now, we have to create the SAP Backend connection to SAP BTP : -

Before mapping data from S4H or our SAP System to Build Apps, we need to create a Destination in the BTP and give the required details of the S4H system with ODATA Uri too which we will consume (BTP->Connectivity->Destination )

Connection is now established to that service.

Now go to SAP Build Apps and navigate to Create to create a project.

Now click on Build an Application to create a Application

Now Click on Web & Mobile Application

Now Give the project name and Description and You are good to go.

Inside the app you are working on SAP Build App go to the Authentication section and implement authentication

Now create an App Variable that holds all fields that are present in our OData service.

Now create a page and install a template from the marketplace which is Basic List and implement your UI for Customer Creation and a home page where all customers are displayed.

Now go to the DATA Section then go to SAP Systems and connect to your s4h System and the service that you called from the destination from SAP BTP will be available to you now.

Now Click on this list go to ‘list resource’ fill in all the fields and configure authentication from Properties

Now Go to the Logic section of List and implement logic like this

Now click on the Create button go to Show logic for Button then implement this logic

Now create another page as shown below and build a form to create Customer Data using input fields.

Now do data binding to all fields by clicking on it and then assigning value to it

Now do a similar mapping for every field

Also, implement a condition to alert that an empty value is not allowed.

Now on the submit button implement logic that submit the data and updates the data to that OData service and thus will be reflected in the database table too

Preview Your Developments: -

Now when everything is done go to the Launch section then Preview your app.

By this, we can preview our application either on the web or can be previewed in Smartphones.

Our Application Now looks like-

When we click on the create button the second page appears

Fill out details and now our customer is created.

So now your customer is created in your database table which you can check by going to se11->KNA1

And you can see your entry got updated in table KNA1

Tips to add your SAP Build Apps application to different BTP environments - Part 3

2024-04-10T15:12:58.956000+02:00

Hi SAP Builders!

This is a follow up blog to Tips to add your SAP Build Apps application to different BTP environments - Part 1 and Tips to add your SAP Build Apps application to different BTP environments - Part 2, here I will continue to showcase 'how to add your deployed SAP Build Apps application to different environments in SAP BTP (Business Technology Platform)'.

In Part 3, let's focus on how to do this when the required services (SAP Build Apps, SAP Build Work Zone, standard edition) are running in different subaccounts in SAP BTP (either within the same Global account or in different Global accounts).

Pre-requisites

As indicated in the Solution diagram above, both Subaccounts must be connected to the same IAS configuration for SAP Cloud Identity Service.
You know the URL of the deployed SAP Build Apps application.

Hint: The direct URL of the deployed application can be always found in the HTML5 Applications repository section of your BTP Subaccount.

* NOTE: If a new version of the application is deployed to CF the URL would change, so we need to check for it again here to adjust any bookmark reference to your application. Only then we can continue to access the application without any issues.

Spoiler

If the URL is from an earlier deployment then the application will no longer be available for access.

Integrate your SAP Build Apps application to SAP Build Work Zone, standard edition

Design time configuration of SAP Build Apps in SAP Build Work Zone, standard edition

Create an application via ‘Content manager’.
Provide the required details, important is to copy the latest deployed URL of the SAP Build Apps and add / adjust * it under the field 'URL' in Configuration.

Add the application to all the required roles of your end user.

Integrate the application to the runtime

To add your application to the desired runtime environments in SAP Build Work Zone, standard edition, refer to my previous blog post Tips to add your SAP Build Apps application to different BTP environments - Part 1 under the sections:

Spaces and Pages New Experience
Classic Launchpad with Groups
New Launchpad with Spaces and Pages

Launch your SAP Build Apps application at runtime

When we configure our SAP Build Apps application as a URL application and launch it at runtime, we will be prompted to login. This is expected behavior as the SAP Build Apps service is running in a different Subaccount and is essential for metering.

If this is not desired, then configure the Default IDP for your organization to enable Single Sign On (SSO) login automatically.

With this, I hope that you could also bookmark your deployed SAP Build Apps application (from a different Subaccount) to your SAP Build Work Zone, standard edition (in this Subaccount) and use it successfully.

Disclaimer: Bookmarking is a work around approach to use the SAP Build Apps application and may not function optimally at all times. Yet we are sharing this 'Know-how' as SAP Build Apps services is currently not supported in all data centres and accessing SAP Build Apps across different subaccounts (either within the same Global account or in different Global accounts) is a possible use case.

Spoiler

Coming up next,
In Part 4 of this blog series I will cover the same scenario for SAP Build Work Zone, advanced edition.

Coming up next,In Part 4 of this blog series I will cover the same scenario for SAP Build Work Zone, advanced edition.

Stay tuned and Happy building!

使用Business Application Studio开发SAP Build Work Zone插件

2024-04-17T07:57:25.904000+02:00

SAP Build Work Zone是BTP上最新的企业门户平台服务，通过Work Zone，企业可以更好的配置企业应用统一入口。与SAP Portal类似，Work Zone底层也是基于SAP Fiori Launchpad，所以Work Zone的插件开发，利用的就是Fiori Luanchpad的插件开发技术。

与On premise系统中的SAP Fiori Launchpad一样，通过插件的开发，开发人员可以扩展SAP Fiori Launchpad的基本功能，可以在SAP Fiorilaunchpad中添加自定义代码，在页面上添加新的元素等。

Fiori Luanchpad中的插件(Shell plugin)开发使用SAPUI5开发技术，SAP Business Application Studio作为开发平台。本文会展示如何开发、打包、部署Shell Plugin插件以及如何并在Work Zone中配置。

准备工作：请在SAP BTP中创建以下服务，并分配用户权限。

SAP Business Application Studio
SAP Build Workzone/ SAP Portal/ SAP BTP Fiori Launchpad

1. SAP BAS开发环境准备

打开SAP BTP中的BAS服务，创建SAP Fiori的开发空间。

2.BAS中开发插件

Shell Plugin应用本质上是一个MTA中的Freestyle的Fiori应用。所以与Fiori应用开发一样，需要创建MTA工程，添加Managed Approuter等。未来可以在MTA中添加CAP、Nodejs或者JAVA等后端程序，并连接SAP HANA Cloud, SAP Event Mesh等服务实现复杂需求。本文仅展示如何使用模板创建Fiori应用，不会涉及到后端程序。

具体步骤如下：

选择 "New Project From Template"并选择"SAP Fiori Application"模板

选择Basic模板，并填入所有参数

Data Source：None

设置Viewname(本文中的开发不涉及的到view和controller，所有的开发都在componentjs中进行)

设置应用基本信息，并勾选Add deployment configuration以及Add FLP configuration。

部署target选择CF环境。

设置 Semantic Object为Shell，Action为plugin。

完成设置，创建mta工程成功，webapp为Fiori应用所在文件夹，mta.yaml文件为mta工程的描述文件。

修改Fiori应用Manifest文件，添加Shell Plugin参数：修改类型为component，添加hideLauncher，添加flp类型，请参考文档：adding-shell-plugin

添加代码，添加自定义menu等。自定义代码需要添加在component.js中，本文自定义代码实现两个功能：

代码可参考SAP官方github SAP-samples

当用户打开workzone时，弹出对话框显示自定义消息
在Fiori launchpad的表头中添加自定义button。

获取ushell的render对象

在component.js的init方法中添加自定义button 以及dialog。

代码开发完成后，将mta工程打包并发布到BTP CF环境中。

在mta.yaml文件上右键打开菜单，选择Build MTA Project

打包完成后，选择mta_archives中的mta文件右键打开菜单选择 Deploy MTA archive，将工程部署到BTP中

部署结束后，在BTP中可以看到创建的instance以及Shell plugin 程序

Workzone配置插件

打开workzone的site配置页面

channel manager页面刷新 HTML5 apps

content manager页面中的content explorer，选择HTML5 app

在content explorer中可以看到刚部署的Shell plugin 应用，注意确认应用type为shell plugin，选择然后点击add添加应用

回到content manager，并将开发的应用添加到预定义好的everyone角色中。

workzone配置完成，现在可以打开workzone测试！

打开workzone的site 可以看到，我们添加的dialog已经显示出来，并且在左上角添加了我们的自定义button。

打开F12，代码已经加载成功。

恭喜你，插件开发成功！

What’s in SAP Build for our Partners? Insights from sovanta AG

2024-04-18T10:30:11.505000+02:00

sovanta AG, our esteemed partner, plays a crucial role in our collaborative efforts. Join us for an engaging interview with sovanta, where they will shed light on empowering customers through innovative SAP Build portfolios. Be prepared to be inspired as Christian Heinrich, Executive Board Member, and Lisa Keller, Senior Project Manager at sovanta, share their valuable insights!

SAP has recently launched Enterprise Automation with SAP; how do you perceive its importance in the context of your customers' journey?

Process Automation is certainly one of the most important topics for our customers now. On the one hand, it is a topic with extremely high potential. Every customer can name off the top of their head a multitude of processes within their company or their department where there is potential for improvement. And all the customers we talk to quickly realize that SAP Build Process Automation can help them with exactly those challenges. On the other hand, the topic is an excellent opportunity to get started with BTP. Many of our customers have used it to gain initial experience with the platform and the cloud and have ventured into other topics from there.

SAP and sovanta at DSAG Technologietage 2023 in Mannheim: Official launch of the sovanta Innovation Factory

What are the biggest issues your customers are facing now?

We have many clients that we are privileged to serve on BTP. Some are already well advanced on their BTP journey, while others have just started their journey. We repeatedly hear similar challenges from customers who are still very new to BTP. On the one hand, they wonder how best to get started on BTP. On the other hand, they don't know which expertise they need to get started or they simply do not have the resources available to get active on BTP. Many companies have a lot of expertise with traditional SAP, but do not yet have enough employees with expertise in BTP. In my view, SAP Build can be an important pillar in answering these challenges, as many of the tools offer a quick and lightweight introduction and employees have a steep learning curve.

How do you consider low code generally at sovanta?

The topic of low code plays a decisive role for us. As a member of the AppHaus Network, we have been pursuing the human-centered approach to innovation for years, in which close coordination with end users and their involvement in IT projects is of crucial importance. Up to now, we have relied heavily on visual prototypes for coordination with users. Low Code offers us completely new opportunities to involve business users even more closely in projects. Not only do we get results even faster, but we also increase commitment, because it's always different when you've worked on a solution yourself.   

In addition, the issue of speed cannot be overestimated. On the one hand, low code gives us the opportunity to integrate other user groups into the solution creation process and thus scale it differently, and on the other hand, we are increasingly able to convince pro developers of the advantages of low code and thus make their work even more efficient. Low Code is a great addition to the toolbox for developers.

Christian Heinrich on stage at the SAP Build Experience Day in the sovanta Innovation Factory

How did you start with SAP Build?

We started a lot of activities before the actual announcement of SAP Build. We worked actively with customers in SAP Work Zone and SAP Workflow Management, and we tried SAP Build Apps for internal solutions.

What is SAP Build for in your portfolio?

We have integrated the entire SAP Build portfolio into our sovanta portfolio. Because in the end, for us it is always about improving the user experience. SAP Build is an excellent tool for this. We help customers to implement employee or customer portals based on SAP Build Work Zone. We modernize and improve processes for our customers with the help of SAP Build Process Automation and we help to implement extensions based on SAP Build Apps. Of course, SAP Build Apps cannot support all our extension projects, for many of them we continue to rely on the established Pro Code support such as SAP CAP or SAP Fiori (Elements). But where it makes sense, we have had good experience of working in "fusion teams" with the citizen developers on the customer side. We have developed a special solution for this called "SAP Build Apps Bootcamp" in which we realize a solution together with business experts on the customer side in just three weeks. The customer does the actual low-code work, and we provide support with UX design, integration, and expert consultations.

SAP & sovanta speakers at the SAP Build Experience Day in the sovanta Innovation Factory

Can you share an example on how SAP Build Process Automation helped in a customer project?

We all must admit, paper-based processes are still around a lot. While those scenarios might not be the shiniest ones, they are the ones with a lot of potential and clear business cases. One of our customers from the real estate management sector has really taken a liking to process automation and we have already been able to improve several processes together with them. One of these processes involved a classic of process automation - approvals. Investments as part of renovation work must be checked and approved by several people. However, the associated documents can sometimes fill several folders. Instead of carrying these across the company as before, the process can now be mapped completely digitally thanks to process automation.  

Can you share an example on how SAP Build Apps helped in a customer project?

If it's ok, I'd like to use a sovanta internal example here. This example shows very well the challenges that SAP Build Apps can help with. It involved the implementation of a solution within our Innovation Factory. We wanted to provide employees with all relevant information and assets from our Innovation Factory in one central location. However, sometimes it is difficult to find the right experts for a new internal topic even within a software company at short notice, especially when everyone is heavily involved in customer projects. So, we thought, let's just try it out ourselves based on SAP Build Apps. And I have to say, it worked very well. Sometimes SAP Build Apps simply opens new possibilities for tackling projects quickly, even when resources are scarce.

Hands-on session at the SAP Build Experience Day in the sovanta Innovation Factory

Can you share an example on how SAP Build Work Zone helped in a customer project?

SAP Build Work Zone is great whenever you have processes span multiple systems. Having relevant data sitting in separated systems can lead to scenarios where there is a lot of room for improvement. This was also the case within a project we realized together with one of our customers in the retail field. Within one of their core processes the customers employees had to touch multiple systems to get their jobs done. By using SAP Build Work Zone for a central cockpit, we now allow the users to have all relevant information at hand and to trigger all needed steps for the process from one central cockpit.

How do you plan to use SAP Build in the future?

For us SAP Build Process Automation and SAP Build Work Zone are really a no brainer. They are well established within our portfolio; our experts know how to handle it and are always up to date when it comes to new features.

 For SAP Build Apps we are currently figuring out how we can further support the decision process. A lot of customers ask us about parameters that indicate whether a planned solution should be realized by Low Code or by Pro Code. Whereas we worked out a set of criteria to support that decision there is still the need to give even better guidance, maybe by introducing a clear decision tree.

In addition, we are really interested in getting our hands dirty with SAP Build Code, how GenAI and Low Code can be integrated into the everyday work lives of our Developers.

Could you kindly provide insights into your methodology and activities for assisting customers in migrating from SAP Intelligent RPA and SAP Workflow Management to SAP Build Process Automation?

It is possible to make processes easily available in the ‘new world’ via the appropriate APIs. However, we recommend using the moment to challenge and improve the process and remodel it with the SAP Build artifacts - this way customers benefit from the advantages of Low Code.

We want to give a big thank you to Christian and Lisa for taking the time to join us in the interview. Their commitment to connecting with customers through SAP Build solutions is truly impressive. We appreciate their efforts and can't wait to work with them in the future.

Additionally, SAP Build has organized an insightful interview with Maria Woydich, Senior Software Engineer, and Christian Bernhardt, Senior Project Manager, both from sovanta. Don't miss out on their fantastic insights:

▶️Learn more about sovanta’s SAP Build solutions: https://sovanta.com/en/simplify-it/process-automation/

Thanks for reading! Enjoyed the highlights or have feedback? Press thumbs up and reach out to us in the comments. Follow and engage with us on LinkedIn, X and YouTube and sign up for SAP Build newsletter to avoid missing updates!

Demystifying the Common Super Domain for SAP Mobile Start

2024-04-24T10:34:47.592000+02:00

Refresher: The Problem with Third-Party Cookies

The web is heavily based on a technology called cookies. In a nutshell, cookies are a small set of information stored in your browser for later use by a website you visited. Cookies are for instance used to temporarily persist your session after you have logged in to a website or service using your browser – usually until you close your browser window. Cookies are also used when ticking the small check-box whenever a login page offered you to "Keep me signed in" or "Remember me", just settings its validity to a defined timeframe. On the other hand, the web is leveraging cookies also for tracking purposes. We speak of third-party cookies whenever a website, let's say example.com, is integrating some form of content (scripts, images, iFrames, etc.) that is running under a different domain (for example sap.com) and this content or domain is using cookies.

Some time back, all major browser vendors or their underlying browser engines did announce to heavily restrict the usage of third-party cookies with different rollout strategies and timelines (see WebKit, Google/Chrome, Mozilla). This brings us basically to the point, that web applications will only function correctly by default in the future (and partially already today), if they do not rely on third-party cookie scenarios.

SAP Mobile Start and SAP Build Work Zone, standard edition

SAP Mobile Start is a native mobile application serving as the native mobile entry point for the Intelligent Enterprise (read more). Besides bringing relevant business data to the app by leveraging native features like Widgets, Complications, Push Notifications and more, relevant business transactions and processes for mobile scenarios can be executed using the exposed & configured apps. These can be other native apps (like SAP SuccessFactors on iOS and Android) or mobile-optimized web apps – for example SAP Fiori apps exposed from SAP S/4HANA. From a content perspective, SAP Mobile Start is based on SAP Build Work Zone, standard edition (alternatively you can also use SAP Start). SAP Start is the central entry point for the browser into (selected) SAP Cloud Solutions. It allows users to search for applications, see all their tasks in one place via SAP Task Center and get recommended interest cards that are relevant to their role. SAP Build Work Zone, standard edition is an application-centric central entry point which supports more systems than just selected SAP Cloud Solutions and provides you more configuration flexibility.

A typical (and recommended) integration approach for web apps, especially for SAP Fiori apps, is to launch these embedded into the central shell. This approach is often also referred to as the "in-place" mode. On a technical level this means, that the actual app is running inside an iFrame within the surrounding shell of SAP Build Work Zone, standard edition. This holds true for both launching embedded / in-place apps in SAP Build Work Zone, standard edition on your regular desktop browser as well as when launching these via SAP Mobile Start. The latter is instantiating an in-app browser window provided by the mobile operating system where the web app is launched using its unique target URL. The following figure shows the same business app (in our case "Manage Purchase Orders") both started on the left with a laptop device using SAP Build Work Zone, standard edition and on the right side using the native mobile app SAP Mobile Start.

SAP Fiori App launched in SAP Build Work Zone, standard edition and SAP Mobile Start

Example: Problematic Landscape Configuration

Let's look at an imaginary landscape configuration where third-party cookie restrictions may be causing issues. Such an example will help us to illustrate potential issues during your system landscape setup and segue to the next section where we will focus on how to overcome these issues. In the following scenario we have provisioned the following resources:

A new SAP S/4HANA Cloud Public Edition tenant that is available under the imaginary URL my000000.s4hana.cloud.sap
The SAP S/4HANA system is trusted with an SAP Cloud Identity Services – Identity Authentication tenant using the URL example.accounts.cloud.sap
Your SAP BTP subaccount is trusted with same SAP Cloud Identity Services – Identity Authentication tenant, but using the URL example.accounts.ondemand.com
On the SAP BTP subaccount, SAP Build Work Zone, standard edition is subscribed
SAP Build Work Zone, standard edition is used by your end-users with the URL example.launchpad.cfapps.eu10.hana.ondemand.com and SAP Mobile Start is onboarded on this environment with the same URL
Content from SAP S/4HANA Cloud Public Edition is exposed with in in-place integration mode

When your purchaser employee is now launching the "Manage Purchase Order" application exposed from the SAP S/4HANA system via SAP Mobile Start, the following technical steps happen during the launch:

SAP Mobile Start is instantiating the in-app browser view and passes the URL which points to the tapped application on SAP Build Work Zone, standard edition.
SAP Build Work Zone, standard edition running on the SAP BTP will most likely not have an active browser session, thus redirecting to the connected Identity Provider.
Ideally the session on the Identity Provider is still valid from the initial onboarding of SAP Mobile Start, otherwise re-established by the configured authentication abilities. (Note: A session cookie on the SAP Cloud Identity Services – Identity Authentication tenant will be set in the context of ondemand.com)
SAP Build Work Zone, standard edition is now loading the context including the information of the targeted application
The in-place app is being loaded in an iFrame on the page, pointing to my000000.s4hana.cloud.sap
Since there is no active session, a redirect is being triggered to the connected Identity Provider of the SAP S/4HANA system (example.accounts.cloud.sap)
The iFrame connected to example.accounts.cloud.sap can neither access cookies of the same SAP Cloud Identity Services – Identity Authentication tenant set in the context of example.accounts.ondemand.com nor use cookies under the context of example.accounts.cloud.sap

The iFrame connected to example.accounts.cloud.sap can neither access cookies of the same SAP Cloud Identity Services – Identity Authentication tenant set in the context of example.accounts.ondemand.com nor use any cookies, since the main window is operated under ondemand.com and an iFrame running under cloud.sap is considered a third-party cookie scenario. The second aspect holds true if the browser is restricting the usage of third-party cookies. As an example, this holds true already for SAP Mobile Start on iOS, since the browser is based on WebKit.

Schematic illustration of issues with the third-party cookie restrictions

As a conclusion, the observed issues are caused by the fact that multiple cloud solution are operated under different super domains. When integrating these technically using an iFrame, which is the case for SAP Build Work Zone, standard edition with the "in-place" mode, browsers will run – depending on their (default) settings – into third-party cookie restrictions. In the worst scenario, this makes the integrated business application unusable for some or all users.

Correcting the Configuration

To avoid any of such cross-domain scenarios leading to possible third-party cookie restrictions, it is key that all integrated cloud solutions – especially those running in an iFrame – are operated under the same root domain. This fact is often referred to as "having a Common Super Domain". Since SAP Build Work Zone, standard edition as a product is supporting the Common Super Domain of SAP, it is recommend to operate it in this case under cloud.sap – matching the root domain of the integrated SAP S/4HANA content.

In our example case this means, we should consume our SAP Build Work Zone, standard edition Site, where the content is exposed to via the URL example.eu10.workzone.cloud.sap instead of the other one mentioned above. This holds true as well for the onboarding configuration of SAP Mobile Start, which can be done either via the QR Code shown in the User Settings when opened with the desired URL or with a Managed App Configuration, where Administrators can push this config using an MDM system to enrolled mobile devices. Please note: In case you were already using SAP Build Work Zone, standard edition with the URL based on ondemand.com, you need to inform your users to use the desired URL going forward. Same applies for previously onboarded users to SAP Mobile Start.

In addition, adjust the SAP Cloud Identity Services – Identity Authentication tenant used by SAP Build Work Zone, standard edition to use the accounts.cloud.sap domain. This will allow that the Identity Provider session (and generally cookies) being established for the main page of SAP Build Work Zone, standard edition can be reused by the app iFrame.

Pro tip: We strongly recommend to leverage the "Identity Authentication" feature of SAP Build Work Zone, standard edition. This procedure will establish a direct trust using Open ID Connect to SAP Build Work Zone, standard edition and it will result in an own "Application" entry within your SAP Cloud Identity Services – Identity Authentication tenant. This also enables you to maintain dedicated configuration settings, separately from your general trust to the SAP BTP. At the time of writing this blog post, this feature is optional. It is very likely that it will get much more relevance in the future – hence our strong recommendation already today.

Schematic illustration of a configuration to avoid third-party cookie scenarios

Summary – Key Take-Aways

Integrating Cloud Solutions that are operated under different super domains can cause issues due to third-party cookie restrictions in modern browsers. (read more)
Going forward, such issues can be solved by leveraging the Common Super Domain cloud.sap
This also holds true for the configured Identity Provider, that is capable of creating and holding a user session.
SAP Build Work Zone, standard edition can be used with the Common Super Domain following the logical schema <subdomain>.<datacenter>.workzone.cloud.sap (read more)
SAP Start can be used with the Common Super Domain following the logical schema <subdomain>.<datacenter>.start.cloud.sap
Make sure to onboard SAP Mobile Start with the correct URL using the QR Code or an MDM solution. Make sure to roll it out correctly to all of your end-users.

Thanks to @florian_buech for co-authoring this article.

How to embed SWZ portal into an iFrame?

2024-04-24T18:54:14.805000+02:00

How to embed SWZ portal into an iFrame? Where to insert my embedding domain into the list of SWZ trusted domains?

When trying to embed the entire SWZ portal into an iFrame I get the following error:

Refused to frame 'https://btp-tenant.workzone.cfapps.eu10.hana.ondemand.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' https://teams.microsoft.com https://btp-tenant.cpp.cfapps.eu10.hana.ondemand.com https://btp-tenant.launchpad.cfapps.eu10.hana.ondemand.com https://btp-tenant.workzone.cfapps.eu10.hana.ondemand.com https://btp-tenant.workzonehr.cfapps.eu10.hana.ondemand.com https://btp-tenant.mobile.workzone.cfapps.eu10.hana.ondemand.com https://btp-tenant.mobile.workzonehr.cfapps.eu10.hana.ondemand.com".

The list in the frame-ancestors is a list of SWZ trusted domains. Thus, for instance, I can embed the same SWZ portal into MS Teams. This works because https://teams.microsoft.com is already on the trusted domains list above.

Worth mentioning, this is a different trusted domain list from the list of the trusted domains maintained in SWZ's SAP IAS. The latter is used when embedding 3rd party content into SWZ.

Q. So the question is how do I get added any custom domain to the list of trusted domains to embed SWZ into?

A. Eventually I figured out how to do it with either SAP Workzone edition, namely free/standard and advanced.

You have to edit the list of relevant security headers in the site manager settings as depicted in the screenshot below. Then you can embed SWZ in your website;

Voila; that's it.

PS.

The following links were helpful:

https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/security

https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/using-security-headers

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy

Free SAP Build account error "Creation Failed: Couldn't create an instance..."

2024-04-26T18:12:58.540000+02:00

When trying to create a free SAP Build free account, the error "Creation failed" stop the process.

This issue is due to the Sub-account doesn't find an Identity Provider to make everything works.

To solve it:

1. Go to your Trial subaccount > Service tab (side panel) > Instance and Subscriptions > Create

2. A new windows will open. Then we will install the Cloud Identity Services into our subaccunt. This will help us to have an Identity tool to make everything works.

You will receive a welcome email from IAS. Follow the IAS procedures (not described at this bolg)

3. Once the Cloud Identity service is installed you can try to reinstall your free SAP Build application.

If you liked it give me a Kudo!

Consuming SAP with SAP Build Apps - Web App in SAP Build Work Zone, standard edition

2024-05-02T03:19:46.516000+02:00

This blog post is the fourth in a series of posts that cover the connectivity options available for SAP Build Apps to interface with SAP systems. The series will cover connecting SAP Build Apps with the following:

CAP-based services
S/4HANA systems
ABAP systems

The format of this post is similar to a tutorial. However, I'll provide more comprehensive details, tips and the opportunity for you to provide feedback. Based on the feedback we will be able to adjust and enhance this post and future parts of the series, and might even be able to improve the products involved as well.

Introduction

Before we get into the details of setting up connections between SAP Build Apps and SAP Systems, I intend to introduce a couple of SAP technology components in each post that are relevant for the use cases covered in the series.

SAP Build Work Zone

SAP Build Work Zone is a digital workplace experience that enables users to build and customise business sites that provide centralised access to business application information from any device.

Key capabilities are:

Quickly create corporate websites providing secure and central access for apps, tasks, notifications, information and communication.
Easily connect with SAP and third-party enterprise applications.
Provide a personalised and role-based user experience.
Provide an extensible framework for development, customisation and branding.

The service is currently available in 2 editions:

Standard edition - this is basically the same as what we previously called the SAP Launchpad service. This is the edition we will use in this blog post. It has a strong focus on integration of business applications.
Advanced edition - this is what we previously referred to as the SAP Work Zone service. It includes additional capabilities on top of what is available in the standard edition. The information in this blog post can be applied in this edition as well. You typically subscribe to only one edition. The advanced edition adds capabilities around workspaces, knowledge management and user engagement.

MTAR

A multitarget application (MTA) is comprised of multiple parts (also referred to as "modules"), created with different technologies and deployed to different targets, but with a single, common lifecycle.

A multitarget application archive (MTAR) is an archive that contains a deployment descriptor, configuration files, and module and resource binaries. The archive follows the JAR file specification. A JAR file is essentially a zip file that contains an optional META-INF directory.

An example relevant for the use cases in this blog series is an MTAR created in SAP Build Code that contains the Destination, a node.js based CAP service, and a HANA database deployment application for setting up the persistency layer. All are deployed during a single deployment action, for a specific version of the archive.

Use case D : Consume the CAP service with a web app provided in SAP Build Work Zone

For this use case, we will make use of the previously created basic CAP service in SAP Build Code. In the previous blog post, we have created dedicated mobile apps for the iOS and Android platforms to consume this service with SAP Build Apps. We will now use the exact same UI application to build and deploy a web application to SAP Business Technology Platform. After that, we will configure SAP Build Work Zone to provide access to the application.

Solution diagram

Like in the previous blog post, we will start with a quick look into what needs to change in our solution overview to accommodate for web apps. Building upon the solution diagram created earlier, we now add SAP Build Work Zone, standard edition. The design time environment of SAP Build Apps will deploy the web application to the HTML5 Application Repository service. The application is made available to end users through SAP Build Work Zone, which is configured separately. End users can access the web app from any device. The web app authenticates with the Identity Authentication service (IAS) and accesses data via a Destination. Only users who have the correct Roles assigned will be able to access the data provided in the CAP-based data service.

Building the web app in SAP Build Apps

As the application we have developed so far is actually a cross-platform app, we don't need to change anything in the app itself. We simply need to build it for a different runtime. And for this, we will again make use of the cloud build service we have utilised in the previous blog post.

Starting in SAP Build Apps, navigate to the Launch tab and select Open build service.

Next, select CONFIGURE for the Web App.

For the Bundle Settings, select MTAR and click NEXT.

In the Image Assets tab, upload a 32 x 32 pixel icon image (PNG file) for the Favicon and click NEXT.

On the Plugins tab, you can add React Native plugins for your app. For our app you can see a few plugins have been selected by default, based on the functionality we have already added in the app. We can use the default selection in this case and click NEXT.

Now that we have completed configuring the web app build settings, select BUILD.

Select MTAR and the Client runtime version. Provide a version number for your application. Select BUILD.

Once the build is done, you will be able to download the MTAR file, or simply deploy the MTAR.

Select DEPLOY MTA.

Select the Cloud Foundry API endpoint of your target subaccount. In our case, we will use the same subaccount as the one we have set up in the first blog post of this series.

Once you've selected your target Cloud Foundry organisation and space, select DEPLOY MTA TO <your space name>

The deployment process will start and your web application will be deployed to the HTML5 Application Repository Service. You can track the progress in the logs.

Once the deployment finishes, the URL to your application will be shown.

When you try to open the URL, you are quite likely greeted with the message "Internal Server Error". Looking into details in your browser's developer tools, you can find a response code 500. This indicates something has not been set up correctly (yet). Not to worry ... we'll fix this in the following steps.

If your subaccount was correctly configured, then you should actually see the web app.

Provide access to the web app in SAP Build Work Zone

We are now going configure SAP Build Work Zone. There are multiple ways to access this. In the context of SAP Build, we can start from the SAP Build landing page. On the landing page, select the Create button.

What would you like to do ? Well, we'd like to Build a Business Site !

Select Configure Site in Admin Console.

Note that in the screenshot below the tile "Manage Workspages and Workspaces" is marked as 'Not Subscribed'. This is because I am using the standard edition of SAP Build Work Zone, which was subscribed through the "Get started with SAP Build Apps" booster. If you have a subscription to the Advanced Edition, then this tile can be selected as well.

Alternatively, if you are not using SAP Build, you can configure SAP Build Work Zone by opening the link in your subaccount's cockpit.

As prerequisite, please check whether your user has the Role Launchpad_Admin assigned.

Once configured (and you might need to log out & log in to activate that Role), navigate to the subscriptions and open the link to SAP Build Work Zone, standard edition.

SAP Build Work Zone configuration

Now, let's set up a business site that includes our app. Select Create Site.

Provide a name for the Site and click Create.

Navigate to the Content Manager tab and select the Content Explorer button.

The Content Explorer will open.

Click on HTML5 Apps to see which apps have been deployed to the HTML5 Application Repository. You will see the app we've created in SAP Builds Apps. Besides that, you will also notice the Launchpad for the products service we've deployed from SAP Build Code. Select the app created and deployed with SAP Build Apps and click the Add button.

Going back to the Content Manager, select the Create button and create a new group. Give the group a name and assign the previously added app to the group.

Go back to the Content Manager and select the Everyone Role. Enable the previously selected app to be accessible for everyone. Note that this will give users access to the web app itself. Access to the data service is still limited to those having the Role we have configured in the second blog post of this series.

Resolving the "Internal Server Error"

And now for the previously mentioned 500 response code, resulting in "Internal Server Error". This happens when the authentication mechanism for SAP Build Work Zone and SAP Cloud Portal service uses XSUAA, while your subaccount is actually configured to use a custom IdP (IAS). To switch to Identity Authentication, navigate to the Settings, select the Identity Authentication tab and click Enable (please read the notes before doing this, and confirm that you've completed the required trust configuration).

Accessing the web app in SAP Build Work Zone

The link to the site can be found on the Site Directory.

Depending on how you've configured your site in SAP Build Work Zone, it might look a bit different. But you should have the tile of your app visible on your site.

Clicking on the tile will open our web app. Notice the SAP BTP authentication happening before opening the app. Also note that you can open the URL on any device; on mobile as well as desktop devices.

In case you are wondering where the icon ended up: check your web browser's tab.

Alternatively, you can also open the URL provided in SAP Build Apps, or find a link to your app in your subaccount, under the tab HTML5 Applications.

Summary – use case D

In this use case we have built and deployed our cross-platform app as a web app to SAP BTP. Building and deploying the app in the cloud is easy, as you don't need to install any tools on your local development machine.

SAP Build Apps deploys the application to the HTML5 Application Repository service. Using the web app, end users authenticate with IAS. Only users who have the correct Role assigned will be able to access the data provided in the CAP-based data service, which we can access through the BTP Destination.

Access to the app requires configuration of the Identity Authentication in the subaccount.

We have set up a simple business site in SAP Build Work Zone, to provide end-users easy access to the app.

And again, all the above was done without writing a single line of code.

What's next

In the next blog post, we will continue on the connectivity topic and connect to an S/4HANA system.

SAP Community - SAP Build Work Zone, standard edition

SAP Build Work Zone - Transport Route

Participate at the SAP Build Hackathon in April 2024

Embedding a Fiori app within another - SAP Build Work Zone, standard edition

[INVITE]: Join us in driving development forward with SAP Build and SAP Build Code

SAP Activate – What’s New in User Experience guidance with SAP Fiori for SAP S/4HANA

Getting started with SAP Fiori for SAP S/4HANA ?

Want to see an examples of how experts introduce UX?

Planning to demonstrate SAP Fiori?

Want to discuss your UX Strategy with your business?

Planning a SAP S/4HANA upgrade ?

Moving to Spaces and Pages layout?

Looking to grow your usage of SAP Fiori ?

Looking to add SAP Build Work Zone and SAP Mobile Start?

Want more SAP Activate updates for User Experience?

Witness Thomas Volmering Unveil Fusion Development: SAP Build in Action

Clean Core Strategy

Fostering Collaboration through Fusion Teams

Insights for Innovation

What is new for SAP Build Work Zone? Product Highlights in January and February 2024

Roadmap Updates

Administration Experience

SAP Build Work Zone, standard edition

SAP Build Work Zone, advanced edition

Business User Experience

Developer Experience

What is Coming Next?

More Information on new Features and Functions

Learn more

Follow SAP Build on Social Media and Join the SAP Builders Group

Tips to add your SAP Build Apps application to different BTP environments - Part 1

Pre-requisites

Verify that the newly deployed app is available in your Subaccount

Integrate your SAP Build Apps application to SAP Build Work Zone, Standard edition

Preparations before integration!

Spaces and Pages New Experience

Classic Launchpad with Groups

New Launchpad with Spaces and Pages

Leverage SCIM APIs of SAP Build Work Zone to view users and groups provisioned into Work Zone

Tips to add your SAP Build Apps application to different BTP environments - Part 2

Integrate your SAP Build Apps application to SAP Build Work Zone, Advanced edition

Preparations before integration!

Design-time setup

SAP BTP - A Deep Dive into SAP Build Capabilities

A Deep Dive into SAP Build Capabilities

Demystifying SAP BTP Build: A Suite of Powerhouse Services

Unveiling the Benefits of SAP BTP Build: A Citizen Developer's Dream

Who Can Benefit from SAP BTP Build? A Wide Spectrum of Users

Design of the new Apple Vision Pro App for SAP Mobile Start

How to develop Customer creation Application in SAP Build Apps with OData service

Tips to add your SAP Build Apps application to different BTP environments - Part 3

使用Business Application Studio开发SAP Build Work Zone插件

1. SAP BAS开发环境准备

2.BAS中开发插件

What’s in SAP Build for our Partners? Insights from sovanta AG

SAP has recently launched Enterprise Automation with SAP; how do you perceive its importance in the context of your customers' journey?

What are the biggest issues your customers are facing now?

How do you consider low code generally at sovanta?

How did you start with SAP Build?

What is SAP Build for in your portfolio?

Can you share an example on how SAP Build Process Automation helped in a customer project?

Can you share an example on how SAP Build Apps helped in a customer project?

Can you share an example on how SAP Build Work Zone helped in a customer project?

How do you plan to use SAP Build in the future?

Could you kindly provide insights into your methodology and activities for assisting customers in migrating from SAP Intelligent RPA and SAP Workflow Management to SAP Build Process Automation?

Demystifying the Common Super Domain for SAP Mobile Start

Refresher: The Problem with Third-Party Cookies

SAP Mobile Start and SAP Build Work Zone, standard edition

Example: Problematic Landscape Configuration

Correcting the Configuration

Summary – Key Take-Aways

Read More

How to embed SWZ portal into an iFrame?

How to embed SWZ portal into an iFrame? Where to insert my embedding domain into the list of SWZ trusted domains?

Free SAP Build account error "Creation Failed: Couldn't create an instance..."

Consuming SAP with SAP Build Apps - Web App in SAP Build Work Zone, standard edition

Introduction

SAP Build Work Zone

MTAR

Use case D : Consume the CAP service with a web app provided in SAP Build Work Zone

How do you consider low code generally at sovanta?