SAP Builders Blog Posts
Learn from peers about their low-code journey and write your own blog posts to share your thoughts and experiences as you become an SAP Builder.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert

blog hero image.pngGreetings Builders!

We’re pleased to announce this major feature release for our low-code portfolio SAP Build. It is now possible to trigger and consume processes from SAP Build Process Automation directly in SAP Build Apps.

By bridging the gap between the two products, this new capability is a significant step towards a more unified experience across SAP Build. Previously, the primary way to establish a connection was via APIs – the process is described in this blog. Now when developing applications and automations, the integration steps have been simplified to a smooth transition, allowing developers to get deeper insights into process and decision scenarios while enabling a native mobile or web experience.

How to get started

Before getting started with this feature in your projects, we recommend looking at the guide Best Practices: A Strategic Approach to SAP Build Apps. While the low-code approach allows both citizen and professional developers to get started quickly, it’s important to understand optimal approaches, especially for data integrations, to create enterprise apps and extensions that are both scalable and secure.

SAP BTP prerequisites

You will need a BTP Subaccount with service assignments for both SAP Build Apps and SAP Build Process Automation under your entitlements. See the initial setup guides for both:

Setting up the integration

👉 For the complete steps to set up this integration, see the Help Portal.

Important note:

  • When configuring destinations in the SAP BTP Cockpit, check your service destination (technical name: sap_process_automation_service_user_access) and make sure you have added the following properties: AppgyverEnabled – true, and MobileEnabled – true. This is mainly for subaccounts that were previously provisioned with SAP Build Process Automation via booster. For new ones, the booster should add these properties automatically.

To start discovering and utilizing processes within your applications, you will need to create at least one Business Process and release it in SAP Build Process Automation.

process leave.pngCheck out this blog from Rama Murari to explore these steps with a use case for releasing credit blocked sales orders in SAP S/4HANA.

You will find your published processes in the SAP Build Library, which is a new integration option for connecting SAP Build products. Once you enable the selected process, you can begin to leverage it in your apps by adding a logic function that will trigger the process.

trigger flow function.png

Important notes:

  • Only processes with an API Trigger are visible in the SAP Build Library.
  • SAP Build Apps can only access the latest published process version. Make sure to always publish the newest version to the library.

After completing the integration steps, you can test it out with the preview app to see that your process is running. In the SAP Build Lobby, you can also confirm your process is successfully triggered with the exact inputs entered into the app!

👉 See the complete steps for this feature in the Help Portal.

We’re excited to make this feature available to our customers as it brings SAP Build closer together with a more harmonized low-code experience. Let us know your thoughts and feedback in the comments.

Happy Building! 🥳🤝


▫️Check out what else is on the horizon this year in the Roadmap Explorer: SAP Build Apps and SAP Build Process Automation

▫️ For all recent releases, see What’s New: SAP Build Apps and SAP Build Process Automation

▫️Stay connected with the latest in SAP Build: Builders Group, LinkedIn, YouTube