Motivation:
This blog focuses on the concept of destinations available for testing an Action within Action Project.
Actions Editor – Feature List, Usage and Maintenance of Actions Project | SAP Blogs
Actions can be executed by using destinations created in the subscriber's subaccount. Multiple destinations can be created in the cockpit, but not all of them are relevant for an Action Project, so filtering is necessary.
Destination Configuration:
In order to make a destination relevant for an Action Project, you should add a additional property "sap.applicationdevelopment.actions.enabled" with a value “true” in the destination configuration. For projects created using a live API source, add another property "sap.build.usage" with the corresponding value from the table below to the destination configuration.
API Source | Value |
Graph | "GRAPH" |
CAP | "CAP" |
RAP | "RAP" |
BTP | "odata_gen" |
Abhe | "apihub_enterprise" |
IFlow | "integration_flow_rt" |
Note: For the projects created using API specification as source, all the destination with "sap.applicationdevelopment.actions.enabled" property as true will be available.
Making a Destination available:
To enable a destination for testing an Action in Action Editor, the following process must be followed in control tower.
Navigate to control tower from lobby
Navigate to destinations inside control tower
Using the add functionality add the desired destination
The added destination will be available for selection in the destination dropdown present in test tab
Thanks for reading and I hope it helped to understand the concept of object flattening within the Actions Editor. Please feel free to leave a comment if there are any questions and I would be happy to receive any feedback.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
25 | |
16 | |
11 | |
11 | |
11 | |
9 | |
8 | |
8 | |
6 | |
6 |