Update trigger and deploy tutorials

sap-tutorials · Sep 30, 2024 · 0a59b99 · 0a59b99
1 parent e0c3ace
commit 0a59b99
Show file tree

Hide file tree

Showing 22 changed files with 86 additions and 318 deletions.
diff --git a/tutorials/build-apps-deploy/build-apps-deply.md b/tutorials/build-apps-deploy/build-apps-deply.md
@@ -40,99 +40,60 @@ As of the writing of this tutorial, you could only deploy to an Cloud Foundry or
 ---
 
 
-### Build app
+### Create build configuration
 1. Open the **Launch** tab.
 
 2. Select **Open Build Service**.
 
     ![Build service](build1.png)
 
-    The following is displayed, with buttons to configure and start the build in the bottom left.
+    The following is displayed, where you can create a build configuration (a set of properties to describe how you want your app to be built) and to deploy it.
 
     ![Build home page](configure1.png)
 
-1. Click **Build**.
+3. Click **Create Configuration**.
 
-    ![Click Build](build1a.png)
-
-2. Select **MTAR**.
-
-    Select the most current runtime version.
-
-    Enter a version for your app, for example `1.0.0`.
-
-    ![Settings](build2.png)
-
-3. Click **Build**.
-
-The build may take a a little while(20 minutes or so) so you may want to skip to the next tutorial. If you refresh the page, the status will change from `created` to `queued` to finally `delivered`.
-
-![Build status](build3.png)
-
-### Deploy app
-Before deploying, you must have a build showing as `delivered`.
-
-![Delivered status](deploy1.png)
-
-1. Click **Deploy MTA**.
-
-    The first you deploy, you will get the following to sign in to Cloud Foundry so you can deploy the app.
+    Select **SAP Build Work Zone**.
+
+    ![Create configuration](build1a.png)
 
-    ![Authorize](deploy2.png)
+2. Enter **StandardWZ** for the configuration name, and click **Create**.
 
-    >If you have rights to Cloud Foundry on more than 1 BTP tenant, you will need to choose the environment. Otherwise, the environment will automatically be chosen. 
+    ![Start to create configuration](build2.png)
 
-2. Click **Authorize BTP Deployments**.
+    This creates a build configuration.
 
-    You will get a dialog for signing in to the deployment environment (Cloud Foundry).
+    ![Configuration created](build2a.png)
 
-    ![Origin key](originkey.png)
 
-    >Since SAP Build Apps requires a custom identity provider (or, IDP, the service that lets you sign into to BTP), you will sign in with the custom identity provider. To do this, you must provide the code for the specific provider.
 
-3. Enter your custom IDP origin key in the input box – which for many workshops, will be `am86fwfbe-platform` or `sap.custom` – and then click **Sign in with alternative identity provider**.
-
-3. Once signed in, select the Cloud Foundry organization to deploy the app to.
+### Build the app
+1. Click the 3 dots on the configuration, and select **Build**.
 
-    >**For SAP Build workshops**, this will `Work Zone Training _training-emea-z3ktmhk1`.
+    ![Click build button](build3.png)
 
-    ![Select org](deploy4.png)
+2. Enter `1.0.0` for the version number, and click **Build**.
+
+    ![Start build](build3a.png)
 
-    >The deployment is always to the default space of the organization.
+    The build will start.
 
-4. Click **Deploy MTA**.
+    ![Build started](build3b.png)
 
-    ![Deploy MTA](deploy5.png)
+    After about 5 minutes, the status will change from **Building** to **Done**.
 
-    The screen will show a running list of log messages ... this could take about 2 minutes.
 
-    ![Log messages](deploy6.png)
 
-    Once it is done, you will get a screen like this:
 
-    ![Alt text](deploy7.png)
 
-    The name of the app is at the end of the URL, for example, above in the picture, `ag3278`.
+### Deploy app
+Before deploying, you must have a build that completed successfully, which then shows a **Deploy** button.
 
-    >**IMPORTANT:** As of the writing of this tutorial, the link in this screen did not work.
-    >
-    >Generally the link will be in this format:
-    >
-    >`https://<tenant subdomain>.launchpad.cfapps.eu10.hana.ondemand.com/<app name>.<app name>-<version>/page.Page1.html`
-    >
-    >The app name is generally in the format `ag1234`. So an example URL is:
-    >
-    >`https://mysubaccount-f5ytahk1.launchpad.cfapps.eu10.hana.ondemand.com/ag5633.ag5633-1.0.0/page.Page1.html`
-    >
-    >In any event, you can get the correct link in the BTP cockpit, as long as you have the app name in the link, such as above `ag5633`.
+1. Click **Deploy**.
 
-### Run app
-1. Open your subaccount's cockpit.
+2. Select the endpoint for your SAP BTP tenant.
 
-2. Go to **HTML5 Applications**, and find your app.
+    Select the organization and space, and click **Continue**.
 
-    ![HTML5 Applications](run1.png)
 
-    Click the application link (save this link if you later want to embed the app in SAP Build Work Zone).
 
-    You should now see your application.
diff --git a/tutorials/build-apps-deploy/build1a.png b/tutorials/build-apps-deploy/build1a.png
diff --git a/tutorials/build-apps-deploy/build2.png b/tutorials/build-apps-deploy/build2.png
diff --git a/tutorials/build-apps-deploy/build2a.png b/tutorials/build-apps-deploy/build2a.png
diff --git a/tutorials/build-apps-deploy/build3.png b/tutorials/build-apps-deploy/build3.png
diff --git a/tutorials/build-apps-deploy/build3a.png b/tutorials/build-apps-deploy/build3a.png
diff --git a/tutorials/build-apps-deploy/build3b.png b/tutorials/build-apps-deploy/build3b.png
diff --git a/tutorials/build-apps-deploy/configure1.png b/tutorials/build-apps-deploy/configure1.png
diff --git a/tutorials/build-apps-workflow-trigger/bind-input1.png b/tutorials/build-apps-workflow-trigger/bind-input1.png
diff --git a/tutorials/build-apps-workflow-trigger/bind-input2.png b/tutorials/build-apps-workflow-trigger/bind-input2.png
diff --git a/tutorials/build-apps-workflow-trigger/bind-toast.png b/tutorials/build-apps-workflow-trigger/bind-toast.png