You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/api-designer/getting-started-api-designer/README.adoc
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,6 +118,7 @@ ifndef::qs[]
118
118
* You're logged in to the {product-long-api-designer} web console at {service-url-api-designer}[^].
119
119
endif::[]
120
120
121
+
121
122
.Procedure
122
123
. In the {service-url-api-designer}[{product-long-api-designer} web console^], click *Create design*.
123
124
. Complete the form to provide the following details for the new design:
@@ -145,9 +146,9 @@ The content of the *Source* tab automatically updates when you edit values on th
145
146
* _(OpenAPI only)_ Resource paths, data types, and responses
146
147
* _(AsyncAPI only)_ Channels, data types, messages, operation traits, and message traits
147
148
. Click *Save*.
148
-
149
+
+
149
150
The new design is listed on the *API and Schema Designs* page.
150
-
You can use the options icon (three vertical dots) to view details about the design (including export and import events, and the edit history), rename the design, open the design editor, download the design to a file, export the design to {product-long-registry}, or delete the design.
151
+
You can use the options icon (three vertical dots) to view or edit the design details, edit the design content, export the design to {product-long-registry}, download the design to a file, or delete the design.
151
152
152
153
.Verification
153
154
ifdef::qs[]
@@ -181,9 +182,9 @@ endif::[]
181
182
. _(Optional)_ To see the changes that you made since the last save, click *Actions > Show changes*.
182
183
. _(Optional)_ For Apache Avro or JSON Schema designs, you can click *Actions > Format content* to insert spaces and tabs that align your design content correctly.
183
184
. Click *Save*.
184
-
185
+
+
185
186
The new design is listed on the *API and Schema Designs* page.
186
-
You can use the options icon (three vertical dots) to view details about the design (including export and import events, and the edit history), rename the design, open the design editor, download the design to a file, export the design to {product-long-registry}, or delete the design.
187
+
You can use the options icon (three vertical dots) to view or edit the design details, edit the design content, export the design to {product-long-registry}, download the design to a file, or delete the design.
187
188
188
189
.Verification
189
190
ifdef::qs[]
@@ -246,7 +247,7 @@ For more information, see {base-url}{getting-started-url-registry}[Getting start
246
247
247
248
.Procedure
248
249
. On the *API and Schema Designs* page of the {service-url-api-designer}[{product-long-api-designer} web console^], select the design that you want to test.
249
-
. Click *Edit* to open the design editor.
250
+
. Click the options icon (three vertical dots), and click *Edit design content* to open the design editor.
250
251
. From the *Actions* menu, click *Test using Service Registry*.
251
252
. From the *Registry instance* list, select a {registry} instance.
252
253
. In the *Group* and *ID* fields, specify the artifact details.
@@ -283,7 +284,7 @@ For more information, see {base-url}{getting-started-url-registry}[Getting start
283
284
284
285
.Procedure
285
286
. On the *API and Schema Designs* page of the {service-url-api-designer}[{product-long-api-designer} web console^], select the design that you want to export.
286
-
. Click the options icon (three vertical dots), and click *Export to {registry}*.
287
+
. Click the options icon (three vertical dots), and click *Export design to {registry}*.
287
288
. Complete the form to specify where to save the new design. Provide the following details:
288
289
+
289
290
NOTE: If the design was originally imported from {product-long-registry}, the fields are prepopulated with the details of the original {product-registry} instance, and the *Version* field is blank.
0 commit comments