This blog is the fourth part of this series of blogs: link to Introduction
Request a requirement approval. The end-user receives a notification in his inbox (SAP Build Process Automation) and can choose to accept or reject the new requirement. The requirement satus (SAP Cloud ALM) is updated accordingly to the user decision.
All integration scenarios of SAP Cloud ALM are based on the public APIs listed in the SAP Business Accelerator Hub.
A SAP Partner informed a customer about a new content (see Part 3: Use a mobile application (SAP Build Apps, SAP Cloud ALM) to trigger a requirement approval.) by triggering a workflow. The customer project manager is notified in his inbox about the new requirement to approve. Using a form he can accept or reject this requirement. The status is updated in the SAP Cloud ALM customer tenant.
SAP Build Process Automation combines workflow management, RPA functionality, decision management, process visibility, and embedded AI capabilities into one intuitive low-code experience. Read the solution in detail.
The goal of this blog is not to give you a step by step guide on how to create a SAP Build Process Automation workflow. You can follow this learning page for that.
The goal of this blog is to highlight the integration capabilities.
In the SAP Build lobby, create a new SAP Build Process Automation action.
Choose SAP Business Accelerator Hub as source, then SAP Cloud ALM tasks:
Select the patch action:
Adjust the parameters and body like this:
In the SAP Build lobby, create a new SAP Build Process Automation automated process – business process.
This is how the workflow looks like:
The trigger is the integration point with the SAP Build App (see Part 3: Use a mobile application (SAP Build Apps, SAP Cloud ALM) to trigger a requirement approval.) This is the way te receive the parameters (requirement ID and title).
Then a form is used to show the requirements to the end-user and ask for its approval.
Input parameter of the form
Form edition
If the requirement is approved the previously created action is ran with the requirement ID as input parameter. The requirement is updated on the SAP Cloud ALM Customer tenant.
From an end-user point of view, the form is sent in the user inbox:
The project manager can easily approve or reject the new requirement without accessing SAP Cloud ALM. The status is updated in SAP Cloud ALM and triggers other things which will be detailed in the next part.
Thanks for reading.