
Actions Project is one of the core building block of the SAP's LCNC portfolio and provides a central experience for cross consumption of API's and artefacts. In this blog post series, I will cover the following strategic topics through a series of blogs:
For information on use cases to consume Actions, Please check the blog - Consuming API's via Actions in Process from my colleague, @TJe
Terms | Definition |
Open API specification | It is the standard specification for describing, producing, consuming and visualising RESTful APIs and services. |
Citizen Developer | It is a persona who creates application capabilities for self and cross consumption using simplified tools. |
Action Designer | It is a persona that will use the Actions Editor to define and maintain the Actions Project and the Actions for subsequent cross-consumption. |
Action | A single operation or a method that references an API can be consumed in a reusable manner. |
Actions Project | Is a collection of customisable Action(s) that is implemented using the OpenAPI specification by the Action Designer. |
Store | A central space that offers reusable and curated content to be consumed by SAP Process Automation. |
It represents a collection of operation(s) or method(s) with a defined customisable signature that works like a thin layer of abstraction over an API to simplify its consumption. The new Actions Project is the result and the core offering from the upgraded Actions framework and helps to achieve the following objectives.
It is created to manage Actions Project and its corresponding Action(s) in a simplified way. It provides the following capabilities –
Action Editor
All existing Actions Project needs to be clicked from the Lobby area to open it in the new Actions Editor. The Action Designer would need to release and publish the Action Project with its artefacts to make it available for cross consumption.
If you would like to ask a question about Actions used in the SAP Process Automation, please post under the tag SAP Process Automation. Our team would be happy to take your questions into consideration and incorporate any suggestions that you may have. I truly appreciate your participation in our community.
Thanks for reading, and I would really appreciate your feedback. Please feel free to leave a comment in this blog post. You can look forward to my next blog of the series for a more detailed information on the usability of Actions Editor and its capabilities.
Initial understanding of how to create Actions Project can be found here.
More details on consumption of Actions within SPA is available here –
Develop Process Extensions with SAP Process Automation (Actions)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
7 | |
7 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 |