image tag fixed

redhat-scholars · Nov 22, 2024 · 920ce1b · 920ce1b
1 parent 62202d2
commit 920ce1b
Show file tree

Hide file tree

Showing 5 changed files with 21 additions and 21 deletions.
diff --git a/documentation/modules/ROOT/pages/02-startup-project.adoc b/documentation/modules/ROOT/pages/02-startup-project.adoc
@@ -9,10 +9,10 @@ This section shows how to create a simple Serverless Workflow using https://star
 . Open the https://start.kubesmarts.org/[Serverless Logic Web Tools] in your browser.
 
 . Select `YAML` button in the *Create* pane 
-image:02_webtool.png[alt]
+image::02_webtool.png[alt]
 
 . *Change* the workflow name with `order`
-image:02_new_swf.png[alt]
+image::02_new_swf.png[alt]
 
 . *Click* the text `Create a Serverless Workflow` and select `Serverless Workflow Example`: a simple template is generated.
 
@@ -71,7 +71,7 @@ You can easily run your first workflow in your OpenShift environment:
 
 . *Select* `Setup...`
 +
-image:02_try_openshift.png[try openshift]
+image::02_try_openshift.png[try openshift]
 
 . In the *OpenShift* setting page select `Add connection` button
 
@@ -85,7 +85,7 @@ image:02_try_openshift.png[try openshift]
 
 ... In the top right corner *select* the _username_ and the `Copy login command` entry.
 +
-image:02_oc_command.png[oc command]
+image::02_oc_command.png[oc command]
 
 ... After the login process, *select* `Dysplay token` link to get a command line that resemble the following:
 +
@@ -101,33 +101,33 @@ oc login --token=sha256~VPMhRtYqHghxlRLWD5X92lg3ZIxr0V7dYYcP5DWxJq4 --server=htt
 
 ... Finally, *select* the `Connect` button, you should see the following confirmation message:
 +
-image:02_connection_ok.png[connection ok]
+image::02_connection_ok.png[connection ok]
 
 Now that the OpenShift connection is up, you need to reopen the workflow:
 
 . Go back on the main page *clicking* on the top banner:
 +
-image:02_home.png[home]
+image::02_home.png[home]
 
 . From the left navigation menu *select* `Recent Models`.
 
 . *Select* `order` to open again the workflow designer.
 
 . *Select* again `Try on OpenShift` button and then `Upload "*order*" to Dev Mode`.
 +
-image:02_upload.png[upload]
+image::02_upload.png[upload]
 
 . Wait for the confirmation message and *select* `Go to Serverless Workflow Dev UI ↗` to open the _Dev UI_ in a new browser tab.
 +
-image:02_devui.png[Dev UI]
+image::02_devui.png[Dev UI]
 
 From *Dev UI* you can trigger a new workflow instance and inspect its execution:
 
 . *Select* `Workflow Definitions`
 
 . *Click* on the arrow button in corresponding to the `order` row.
 +
-image:02_wf-def.png[Workflow definitions]
+image::02_wf-def.png[Workflow definitions]
 
 . *Fill* in the `Start Workflow Data` edit box with the following JSON payload:
 +
@@ -149,11 +149,11 @@ You should get a confirmation message stating that your _workflow instance was t
 
 To inspect the workflow execution just triggered *select* `Go to workflow list` at the bottom of the confirmation message.
 
-image:02_started.png[Workflow definitions]
+image::02_started.png[Workflow definitions]
 
 In the _Workflow Instances_ page, *select* the first instance in the list:
 
-image:02_wf_list.png[Workflow list]
+image::02_wf_list.png[Workflow list]
 
 In this _Workflow Details_ page, you can inspect all the details of the workflow execution from the following boxes:
 

diff --git a/documentation/modules/ROOT/pages/03-inventory.adoc b/documentation/modules/ROOT/pages/03-inventory.adoc
@@ -18,7 +18,7 @@ An e-commerce company has to implement the following **order management** workfl
 
 The following picture shows an high level design: 
 
-image:high-level-flow.png[]
+image::high-level-flow.png[]
 
 :sprint-note: pass:c,q[footnote:disclaimer[A Sprint is an iteration in the Agile methodology, which aims to be time-boxed, self container and always executable.]]
 
@@ -142,19 +142,19 @@ Before connecting the workflow to an external service is a good idea to probe it
 
 .. *Select* `Try on OpenShift` button and then `Upload "*order*" to Dev Mode`.
 +
-image:02_upload.png[upload]
+image::02_upload.png[upload]
 
 .. Wait for the confirmation message and *select* `Go to Serverless Workflow Dev UI ↗` to open the _Dev UI_ in a new browser tab.
 +
-image:02_devui.png[Dev UI]
+image::02_devui.png[Dev UI]
 
 . *Trigger* a new workflow instance:
 
 .. *Select* `Workflow Definitions`
 
 .. *Click* on the arrow button in corresponding to the `order` row.
 +
-image:02_wf-def.png[Workflow definitions]
+image::02_wf-def.png[Workflow definitions]
 
 .. *Fill* in the `Start Workflow Data` edit box with the following JSON payload:
 +
@@ -190,11 +190,11 @@ Another tool for checking the workflow execution is the *Console*:
 
 . At the bottom of the _Dev UI_, *click* on the `Open` toggle.
 +
-image:03_open_con.png[open console]
+image::03_open_con.png[open console]
 
 . Among other log lines, you should spot the output of `printMessage`:
 +
-image:03_console.png[console]
+image::03_console.png[console]
 
 
 [#call-rest]

diff --git a/documentation/modules/ROOT/pages/04-longrunning.adoc b/documentation/modules/ROOT/pages/04-longrunning.adoc
@@ -12,7 +12,7 @@ From a use case perspective, the workflow has to wait for an _asynchronous_ even
 
 The following picture shows an high level design: 
 
-image:high-level-flow-2.png[]
+image::high-level-flow-2.png[]
 
 [#waitevent]
 == Wait Event Sprint
@@ -161,7 +161,7 @@ The *CloudEvent attribute* `orderid` matches the `contextAttributeName` used in
 
 Open the *_Workflow Details_* page to inspect the instance status: you should see the the workflow instance still active, waiting for the shipping event:
 
-image:04_shipping.png[Shipping Event]
+image::04_shipping.png[Shipping Event]
 
 To advance the workflow execution, you have to send another event:
 

diff --git a/documentation/modules/ROOT/pages/05-compensation.adoc b/documentation/modules/ROOT/pages/05-compensation.adoc
@@ -23,7 +23,7 @@ In our use case, we have to deal with situations where customers have to *cancel
 
 The following picture shows an high level design: 
 
-image:high-level-flow-3.png[]
+image::high-level-flow-3.png[]
 
 NOTE: Given the simplistic nature of the example, one might consider replacing compensation with a gateway followed by compensatory actions. However, it should be borne in mind that in an even slightly more complex flow, implementing compensation in imperative mode would make the implementation complex and error prone.
 

diff --git a/documentation/modules/ROOT/pages/index.adoc b/documentation/modules/ROOT/pages/index.adoc
@@ -6,7 +6,7 @@
 
 In this tutorial you will learn how to develop a workflow to address some common service orchestration challenges.
 
-image:serverless.png[]
+image::serverless.png[]
 
 [.tiles.browse]
 == Browse modules