
This blog focusses on the usability of the Standard, Custom, Header and Body Parameters within an Action of the Action Project that can be maintained using the Actions Editor.
Actions Editor – Feature List, Usage and Maintenance of Actions Project
An API could be capable of consuming a complex input or returning a complex response structure but the “to-be” executed business process could only require a certain set of the parameters that is relevant for consumption. Similarly, not all the standard parameters may be sufficient while calling the API and there could be a scope for custom parameter to invoke an API and the business relevant data. This could be flexibly achieved by defining additional parameters.
Action Editor allows Action Designers to Add/Delete/Modify Input, Body and Output parameters within an Action of an Action Project. Additionally, It also provides the flexibility to Add/Maintain CUSTOM parameters that are not available from the API specification.
An Action Designer can use the Delete feature to remove any unnecessary parameters from the definition of the Action making it more light and relevant to the business process. Let us try to understand this with an example.
Example: Deletion of Input Parameter in Action Editor
Remove Icon
Remove Parameters Dialog Box
Note: The process to delete an Input-Body & Output parameter is identical to the above.
An Action Designer can use the Add feature to add the Deleted Input/Output/Body parameters. Let us try to understand this with an example.
Example: Addition of Input Parameter in Action Editor
Add icon
“Add New Field: Available Fields” panel.
Note: The process to Add an Input-Body & Output parameter is identical to the above.
Often APIs expose complex parameters which may not be suitable to be exposed directly to a Action Designer and hence they need to be broken down into simpler parameters.
An Action Designer can use the Add feature to also add a Custom header/query/path parameter that is originally not available within the definition of the Action of an Action Project from the specification. There could be potential use cases that that cannot be fulfilled by a standard parameter while invoking an API and this could be managed by defining a Custom Parameter. Let us try to understand this with an example.
Example: Addition of “Content-Type” Input Parameter in Action Editor
“Add New Field: New Field” Form with Custom Parameter add field.
Thanks for reading and i hope it helped to understand the concept of maintaining the Parameters 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 |
---|---|
24 | |
23 | |
22 | |
14 | |
12 | |
10 | |
9 | |
7 | |
7 | |
6 |