v2.1.7+Submitting multiple workflows

The Submit multiple workflows wizard provides a guided, step-by-step process for submitting workflow instances into the current plan.

This feature supports complex workstreams, including the ability to include or exclude specific instances, resolve successor dependencies, include draft definitions, and modify instance priority prior to submission.

The ability to submit multiple workflows simultaneously addresses critical operational requirements that a single-item submission cannot meet. This feature is designed to enhance efficiency, reduce manual errors, and ensure the integrity of complex application environments.

Operational advantages of multiple workflow submission
On-demand application deployment
Instead of manually running an entire application, you can trigger the complete flow on demand. This ensures that every component of the business service is updated in the plan simultaneously.
Automated dependency resolution
Manual overrides often struggle with complex scheduling rules. The wizard automatically calculates and resolves successor dependencies. It understands the relationship between the workflows and ensures that they are injected into the plan in the correct logical order, preserving the integrity of the flow.
Draft submission support
You can use the wizard to submit draft versions directly into the plan. This flexibility removes the requirement for a definition to be in a finalized state before it can be used for plan-based activities. This cross-lifecycle support ensures that the most current logic is always available for submission, regardless of its formal status in the database.
Prerequisites
To submit workflows, you must have list, display, and submit security permissions to access the definitions and perform submission actions.
Accessing the Submit multiple workflows wizard
To open the Submit multiple workflows wizard, perform the following steps:
  1. From the welcome page of the UI, click Monitor.
  2. Expand the item selection menu on the upper-left of the Orchestration Monitor, and select Workflow from the list.
  3. In the upper-right corner of the Orchestration Monitor, click Submit and select Workflow.
The Submit multiple workflows wizard opens and you can start the workflows selection and submission process. Below, you can find the name and the description of each step of the wizard.
Step 1 - Select definition
View the list of workflow definitions available for submission, including those currently saved as drafts.
From the results table, select one or more workflow definitions to submit, then click Next to identify downstream dependencies.
Step 2 - Include successors
Review the workflows definitions selected in the first step and choose which one should include its successor dependencies.
Attention: The following limits apply to the submission of multiple workflows:
  • A maximum of 250 items—including workflows and their successors—in a single action.
  • A maximum depth of 25 levels for nested workflow dependencies.
Including successors ensures the integrity of the workload by identifying downstream workflows that depend on the selected items. By resolving these dependencies during the submission phase, you prevent gaps in the plan and ensure that logically linked workstreams continue to run in the correct sequence.
Click Next to review the expanded list of dependencies.
Step 3 - Select workflows
Review the combined list of originally selected workflows and their successors. Successor workflows are identified by the Successor label.
Click Next to define when the instances should run.
Step 4 - Choose submit time
Define the start criteria for the instances. Choose among the following options:
  • Now: Submits the instances for immediate run into the current plan. Use this option to start the workflow processing as soon as possible.
  • Specify date and time: Defines the submission time. Use this option to manually set the start time for the workflow instances, regardless of their defined run cycles. You can specify a start date that occurs in the past. The end date of the range must be less than or equal to the end date of the current plan.
Click Next to review and refine the individual instances generated for the selected time range.
Step 5 - Select instances

Review the instances generated from the previous step. Instances are grouped by their parent workflow name.

  • View instance details: Expand a workflow to view the workstation and scheduled start time for each individual instance.
  • Bulk selection: Select the checkbox next to a workflow name to include all its instances in the submission. Clear the checkbox to exclude the entire group.
  • Granular selection: Select the checkbox next to a specific instance to include it in the submission. Clear the checkbox to exclude only that specific instance.
You have two options:
  • Review and Submit: Skips directly to the final summary to confirm the submission of the selected instances.
    Note: After clicking Review and Submit, you cannot return to previous steps. For more information, see Step 7 - Review and Submit .
  • Next: Proceeds to Step 6 - Edit properties to modify the attributes of individual instances before they are added to the plan.
Step 6 - Edit properties
Modify the properties of workflow instances before submitting them. You can modify the priority of the instance and edit instance variables.
You can apply changes using one of two methods:
  • Granular selection: Select a specific instance from the list and click Edit. The Properties panel opens on the right, enabling you to edit the properties of the selected instance.
  • Bulk selection: Select one or more instances from the list, or select the main selection checkbox above the workflow instances table to select all instances. Click Edit properties to open the Properties panel and modify the properties of all the selected instances simultaneously.
Editing and overriding variables at submission
From the Variables section of the Properties panel you can quickly add or override variables across many instances simultaneously in a single step.
Important: Overrides applied at this step of the wizard are ad-hoc and temporary. They affect only the specific workflow instances being submitted and do not alter the original workflow definition.
  • Add or override individual variables: Click Add (+) to define a new variable by specifying its Key and Value. If the Key already exists, the value provided here temporarily overrides the existing variable value for the submitted instances.
  • Reference or override a variable table: In the Variable table field, reference an existing variable table. If the instances already have an assigned variable table, the newly selected variable table temporarily overrides the previous assignment for this submission.
Any instance that differs from its original definition is automatically flagged with a Modified label. You can use this label to verify your changes before final submission.
Click Next to proceed to Step 7 - Review and Submit.
Step 7 - Review and Submit

Perform a final audit of the submission list to verify that all instances, scheduling settings, and property modifications are correct before committing them.

  • Manage the view: Use the Expand all and Collapse all buttons to show or hide all workflow instances within the table simultaneously. To view or hide details for a specific instance, click the individual workflow row.
  • Organize data: To facilitate the review of large submissions, you can sort the table by workflow name, folder, or workstation. Sorting is particularly useful for verifying that modified priorities have been applied consistently across different environments.
  • Final validation: Review the summary columns to ensure the configuration aligns with your requirements.
Click Submit to finalize the review and commit the configured workflows. A status notification is displayed to confirm that the submission action has been processed.
Note: The notification confirms the successful processing of the submission action. To verify that the individual workflow instances have been successfully committed, monitor their status in the Orchestration Monitor.