|
Blogs by

Seshadri Sreenivas R

This is part of a multi-blog series concentrating on how to consume the backend APIs in SAP Cloud Platform Workflow Service. Context Building and extending cloud application workflows can unify processes across systems and connect human-centric activities

Context In the competitive world, the best run companies continuously optimize their business processes to minimize the cost incurred and maximize the throughput and efficiency. Prior to digitization, this process was tedious and time consuming.

This is part of a multi-blog series concentrating on how to consume the backend APIs in SAP Cloud Platform Workflow Service. Context Building and extending cloud application workflows can unify processes across systems and connect human-centric activities

Context The SAP Cloud Platform Workflow offers state-of-the-art process automation capabilities. This lightweight workflow service orchestrates service calls and user interaction steps. There are quite a few use cases for consuming such a service in

Warning: This page contains code snippets and require the reader to have good understanding about the model-view-controller (MVC) architecture in SAPUI5. This is part of the blog series which details about the possible UI extensions in

Warning: This page contains code snippets and require the reader to have good understanding about the model-view-controller (MVC) architecture in SAPUI5. This is part of the blog series which details about the possible UI extensions in

Warning: This page contains code snippets and expects the reader to have good understanding about the model-view-controller (MVC) architecture in SAPUI5. In the previous blog, i have explained the concept of UI extensions in OPInt.

Warning: This page contains code snippets and require the reader to have good understanding about the model-view-controller (MVC) architecture in SAPUI5. This is part of the blog series which details about the possible UI extensions in