Icon

Restrict Execution Contexts

<p>Restrict or lift execution context restrictions with version labels.</p><p>Version labels link information to specific versions of components or workflows. For instance, they can indicate that a particular workflow has passed quality control. They can also enforce workflow execution restrictions, ensuring that a production execution context, for instance, only runs workflows that have successfully passed quality control.</p><p>This data app allows you to restrict execution contexts by enforcing the presence of specific version labels. As a result, users can only execute workflow versions that have the designated label assigned within the specified execution context.</p><p>You need to be a global admin to restrict execution contexts.</p>

URL: Documentation https://docs.knime.com/latest/business_hub_workflow_validation_guide/index.html?src=workflow-description#restrict-execution-context

1. Prepare data

Connection, execution contexts, and labels.

2. Data App

Uses the same page in a recursive loop to make use of the "Next" Button.

Restrict Execution Contexts

• Business Hub 1.13 and above with Executor versions 5.3.3 and above

• Analytics Platform versions 5.3.3 and above with connection to a Business Hub 1.13 and above

Done each iterationto capture changes
List Existing Requirements
Sole component withvisuals
Restrict Execution Context
Use REST Endpoints
Set Requirement
Shows only if somethingwent wrong
Prepare data
Avoid recursiveloop to fail when:-No EC are available-No Labels are available
CASE Switch End
Loop to make the "Next"button work on the last page
Recursive Loop Start
... until the data apptab is closed.
Recursive Loop End

Nodes

Extensions

Links