Submitting multiple job streams

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

This feature supports complex workflows, 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 job streams 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 job stream 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 job streams and ensures that they are injected into the plan in the correct logical order, preserving the integrity of the workflow.
Draft submission support: The wizard enables you 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.
Run cycle precision: You can apply the run cycles defined in the definition to your submission. For even greater control, define a specific time interval, for example, from 10:00 to 15:00, to filter which instances are generated and submitted.

Prerequisites

To submit job streams, you must have list, display, and submit security permissions to access the definitions and perform submission actions in the plan.
Both HCL Workload Automation and the Dynamic Workload Console must be at least V10.2.7.

Accessing the Submit multiple job streams wizard

To open the Submit multiple job streams wizard, perform the following steps:

In the Dynamic Workload Console, expand the Monitoring and Reporting menu and select Orchestration Monitor.
In the upper-right corner of the Orchestration Monitor, click Submit and select Job stream.

The Submit multiple job streams wizard opens and you can start the job streams 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 job stream definitions available for submission, including those currently saved as drafts.

From the results table, select one or more job stream definitions to submit, then click Next to identify downstream dependencies.

Step 2 - Include successors

Review the job stream 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 job streams:

A maximum of 250 items—including job streams and their successors—in a single action.
A maximum depth of 25 levels for nested job stream dependencies.

Including successors ensures the integrity of the workload by identifying downstream job streams 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 workflows continue to run in the correct sequence.

Click Next to review the expanded list of dependencies.

Step 3 - Select job streams

Review the combined list of originally selected job streams and their successors. Successor job streams are identified by the Is 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 three options:

Now: Submits the instances for immediate run into the current plan. Use this option to start the job stream processing as soon as possible.
Specify date and time: Enables you to define the submission time. Use this option to manually set the start time for the job stream 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.
Use run cycle: Applies the scheduling logic defined in the job stream definitions. When you select this option, specify the date range in the calendar widget to determine the start times for the instances. You can specify a past start date to generate instances based on previous run cycle. 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 job stream name.

View instance details: Expand a job stream to view the workstation and scheduled start time for each individual instance.
Bulk selection: Select the checkbox next to a job stream 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 priority of the job stream instances before they are submitted to the plan. You can apply this change using two methods:

Granular selection

Access property editing: Select a specific instance from the list and click Edit. A configuration pop-up opens.
Adjust priority: Within the properties pop-up, modify the Priority of the instance to determine its processing precedence in the plan.

Bulk selection

Access property editing: Click Set priority. A configuration pop-up opens.
Adjust priority: Within the properties pop-up, modify the Priority to set a uniform value across all instances simultaneously.

Any instance that differs from its original definition is automatically flagged with a Modified label. This enables you to verify your changes before the 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 to the plan.

Manage the view: Use the Expand all and Collapse all buttons to show or hide all job stream instances within the table simultaneously. To view or hide details for a specific instance, click the individual job stream row.
Organize data: To facilitate the review of large submissions, you can sort the table by job stream 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 job streams to the plan. A status notification appears to confirm the submission action has been processed.

Note: The notification confirms the successful processing of the submission action. To verify that the individual job stream instances have been successfully added to the plan, monitor their status in the Orchestration Monitor.