deploy reminder added

Author: dmarrazzo

documentation/modules/ROOT/pages/03-inventory.adoc

@@ -261,6 +261,16 @@ NOTE: The rest service is invoked with two _arguments_, a dummy `supplier-id` (`
 [#test-rest]
 == Test the external REST service
 
+*Deploy* the  workflow latest updates:
+
+. *Select* `Try on OpenShift` button and then `Upload "*order*" to Dev Mode`.
++
+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]
+
 In order to test the REST call you have to *trigger* a new workflow instance with the following payload:
 
 [.console-input]

documentation/modules/ROOT/pages/04-longrunning.adoc

@@ -133,6 +133,16 @@ To _start_ the workflow and subsequently _advance_ it, you have to inject two *t
 * `OrderEventType`
 * `ShippingEventType`
 
+Make sure that the workflow latest updates are *deployed*:
+
+. *Select* `Try on OpenShift` button and then `Upload "*order*" to Dev Mode`.
++
+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]
+
 The Dev UI offers a convenient web form to inject _CloudEvents_ in the Serverless Workflow runtime:
 
 . *Open* the `Workflow Definitions` page.

documentation/modules/ROOT/pages/05-compensation.adoc

@@ -130,6 +130,16 @@ In this section, we are going to test that the workflow is able to resume the ex
 * `ShippingEventType`
 * `CancelEventType`
 
+*Deploy* the  workflow latest updates:
+
+. *Select* `Try on OpenShift` button and then `Upload "*order*" to Dev Mode`.
++
+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]
+
 Start a new workflow instance:
 
 . *Open* the `Workflow Definitions` page.