Skip to content

W-11585544: Update Studio version #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fermujica merged 1 commit into from
Aug 11, 2022
Merged

W-11585544: Update Studio version #91

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/ROOT/pages/apikit-basic-anatomy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Example: OrderTshirt:/TshirtService/TshirtServicePort/api-config

The name of each backend flow corresponds to the resource-action pairing or to some operation-service mapping. For example, the XML code for the backend flow named `get:/machines:apiConfig` maps to the RAML resource `/machines` and its nested `get:` action.

After generating backend flows, you integrate the functional processes to take the expected input and produce output. From RAML, Studio infers information about the metadata for the input of a flow and exposes this information through xref:6@studio::datasense.adoc[DataSense]. In a REST API, this input might arrive in the following forms:
After generating backend flows, you integrate the functional processes to take the expected input and produce output. From RAML, Studio infers information about the metadata for the input of a flow and exposes this information through xref:6.x@studio::datasense.adoc[DataSense]. In a REST API, this input might arrive in the following forms:

* Request body
* Query parameters
Expand Down
⚡