Icon

00.Orchestration - Exercise

The workflows in this workflow group create a complete, deployable application for collecting and analyzing user feedback.

Below is a summary of the orchestration schema, together with workflow services eventually called by a workflow. Notice that each workflow has a different execution triggerer (in green).

Error Execute failed: 422 Execution context "xyz" not found when executing on KNIME Hub

  1. Open the remote workflow in KNIME Analytics Platform

    1. Connect to the Hub

    2. Navigate to the space where you have uploaded the workflow (note the cloud icon in the tab)

    3. Double click to open the remote workflow locally

  2. Open the Call Workflow Service node and make sure that a valid execution context is selected

    • If you cannot select the execution context, it means that you have opened the local workflow, not the remote one

  3. Save and overwrite the workflow and try again the execution

TROUBLESHOOTING ERROR 422 (PULL)

Data Analysis

Step 1. Deployment and orchestration

  1. Upload the Part 5b - Orchestration folder to KNIME Hub. Reset the workflows before upload.

  2. Configure Workflow Schedules:

    • 02.Feedback Analyzer everyday at 12:00 (note that this workflow calls 03. Generate Daily Recap Report after a waiting time of 30 seconds)

    • In Advanced settings, select the User execution scope, and create the deployment

  3. Test: Manually trigger daily report creation: Configure the above for an immediate execution of 02.Feedback Analyzer. During waiting time, manually execute 04.Email unsubscribers update. A new report is created in the Daily Reports folder.

  4. In case of Error 422, see Troubleshooting annotation.

Part 5 - Best Practices

Exercise 02 Orchestration

Learning objective: In this exercise, you'll learn how to configure and orchestrate multiple workflows interacting with each other.


Workflow description: The workflows in this folder create a complete, deployable application for collecting and analyzing user feedback.

  • The data collection is perfomed by 01.Form Data App.

  • Once a day 02.Feedback Analyzer reads the latest feedback and appends its sentiment prediction. This information, along with user data, is collected in a pdf report for the system admin by 03.Generate Daily Recap Report.

  • Meanwhile, 04.Email Unsubscribers Update takes care of updating the list of users who opt out of receiving emails.


Below is a summary of the orchestration schema, together with workflow services eventually called by a workflow. Notice that each workflow has a different execution trigger (in green). You'll also find the instructions to the exercise in the yellow annotation.

Data Collection

Workflow 2

Sentiment Predictor.
Calculate sentiment of given feedback

04. Email Unsubscribers

Update
Update list file.

Workflow 1
Form Update

Save form new entries.

02. Feedback Analyzer

Append sentiment to latest feedback

Workflow 3

Daily Recap Report

Create feedback report.

USER INTERACTION (Data App)
CALLER WORKFLOW
(01.Form)
EXTERNAL CALLER
(several times a day)
SCHEDULE
(once a day)
CALLER WORKFLOW
(02.Feedback_An.)
CALLER WORKFLOW
(02.Feedback_An.)
WAIT..
(04.Email unsubs.
list update)
01.Form Data App

Collect user information and feedback via interactive form.

Nodes

  • No nodes found

Extensions

  • No modules found

Links