Welcome
What's new
The What's new section tracks the capabilities delivered across each HCL Universal Orchestrator release, organized by version, so you can navigate directly to the features relevant to your deployment.
Version 2.1.7
In version 2.1.7 of HCL Universal Orchestrator, workflow submission gains dependency-aware batching, in-plan task customization, and bulk nop/draft control; a database-first Library, a new chatbot channel, automatic AI agent task context propagation, and a notification banner round out the release.
Workload management with bulk nop control
Streamline your scheduling environment by setting one or more tasks or entire workflows as operational or non-operational in the database.

What's new
The What's new section tracks the capabilities delivered across each HCL Universal Orchestrator release, organized by version, so you can navigate directly to the features relevant to your deployment.
- Version 2.1.7
  In version 2.1.7 of HCL Universal Orchestrator, workflow submission gains dependency-aware batching, in-plan task customization, and bulk nop/draft control; a database-first Library, a new chatbot channel, automatic AI agent task context propagation, and a notification banner round out the release.
  - Library: manage from the database
    With the Library, you can now browse and edit any item definition directly from the database, for fast day-to-day changes across your automation environment. You can also run workflow or task definitions.
  - Chatbot channel: Slack
    With the Slack channel, you can now reach your AI agent chatbot from an enterprise messaging platform your team already uses — with the same identity verification as Telegram.
  - Multiple workflows with dependencies submission
    You can now submit multiple workflows simultaneously, significantly reducing the time spent on manual sequencing and dependency management.
  - Successors & nested workflows submission
    When you select a workflow to add to the plan, you can now include all its successors automatically.
  - Customizing and rerunning tasks in the plan
    Gain greater flexibility and control over your submitted workload by manually rerunning tasks directly from the plan. After a task completes with a final status, you can customize and rerun the task by using either the existing task definition or another definition.
  - Configuring tasks dynamically in the plan
    Gain greater adaptability and control over your workload by modifying a submitted job before it starts running.
  - Workload management with bulk nop control
    Streamline your scheduling environment by setting one or more tasks or entire workflows as operational or non-operational in the database.
  - Effortless control of your workflow status
    Manage your workflows in the database quickly and securely by modifying the draft or non-draft flags of multiple workflows simultaneously.
  - Notification banner: UI announcements
    With the new notification banner, you can now warn users of upcoming maintenance or downtime before they run into it.
  - Deploying HCL Universal Orchestrator on premises
    You can deploy the HCL Universal Orchestrator instance on premises to establish an isolated network and accommodate environments without cloud infrastructure.
  - AI agent task context propagation
    With automatic task context propagation, you can now build workflow tools that react to the AI agent task and parent workflow that triggered them — with no extra configuration.
  - Multi-agent collaboration with the Agent-to-Agent protocol
    The Agent-to-Agent (A2A) protocol introduces a standardized contract for HCL Universal Orchestrator AI Agents, allowing external agent clients to discover capabilities and execute complex workflows efficiently.
  - What's new in UnO Agentic AI Builder
- Version 2.1.6
  In version 2.1.6 of HCL Universal Orchestrator, workflow orchestration gains inline scripting, conditional run logic, and a live monitoring canvas; Docker and Podman deployment, Telegram channel support, and Agentic AI Builder updates round out the release.
- Version 2.1.5
  In version 2.1.5 of HCL Universal Orchestrator, discover new personal setting preferences, the Search tab in the Graphical Designer, and the integrated JSONata editor for expression testing.
- Version 2.1.4
  In version 2.1.4 of HCL Universal Orchestrator, you can explore new orchestration capabilities including cross-plan dependencies, run cycle groups, dashboards, IMAP email events, endpoints, and a major expansion of the Agentic AI Builder.
Getting started with HCL Universal Orchestrator
HCL Universal Orchestrator is a cloud-native workload orchestration and scheduling platform built on Kubernetes. Its microservices-based architecture enables the centralized orchestration of multi-cloud and hybrid environments from a single point of control.
Deploying and Administrating
Deploy, connect, and administer HCL Universal Orchestrator on your own infrastructure, or start immediately with a hosted SaaS environment where the service provider manages all platform operations.
Administering multitenancy
Configure and administer a HCL Universal Orchestrator multitenant environment.
Using the UI
The UI is the HCL Universal Orchestrator interface, from which you can design your scheduling environment and monitor every process.
Orchestrating
Orchestrate anything with HCL Universal Orchestrator.
Orchestrating from Mobile
You can use your mobile devices to manage quickly and easily your whole HCL Universal Orchestrator environment.
Monitoring
Take your environment under control.
Using REST API
Use REST APIs to easily integrate workload scheduling capabilities with external products and solutions.
Uno AI Pilot
Welcome to the HCL Universal Orchestrator AI Pilot documentation. This resource is designed to guide you through everything you need to know about using UnO AI Pilot effectively. You will find detailed instructions, feature overviews, and helpful tips to ensure you get the best experience with UnO AI Pilot.
UnO Agentic AI Builder
Troubleshooting
Recover your environment if any issue occurs.
Notices

Workload management with bulk nop control

Streamline your scheduling environment by setting one or more tasks or entire workflows as operational or non-operational in the database.

Streamline your scheduling environment quickly and easily. You can now use both the UI and Orchestration CLI model commands to smoothly set one or more tasks or entire workflows as operational or non-operational in the database.

Whether you need to temporarily skip a notification task due to a sudden service outage or bypass a set of tasks during system maintenance, this feature saves you time and effort. By setting a task to non-operational (nop), you temporarily disable it without having to delete it or alter your complex dependency chains.

With this granular control feature, you can take advantage of:

Flexible bulk operations: Apply the command at the workflow level to automatically update all the tasks contained within that workflow. If you apply the command to multiple workflows, the action is executed on all tasks within all the workflows returned by your query. Alternatively, specify an individual task name to apply the setting precisely to that specific task.

Smooth workflow continuity: After the command runs, the specified tasks change to the CANCEL PEND status. If a task contains standard dependencies, they are automatically released so that your successor tasks can launch without delay. For added safety, if a dependency is conditional, the condition must still be verified as true before any successors can run.

Targeted security control: Enforce the principle of least privilege with ease. A specific security permission, NOOPDB, enables administrators to grant users the exact access they need to set objects as operational or non-operational. This ensures your environment remains secure, as users do not need broader MODIFY access (which allows changing all object properties) just to perform this targeted action.


nop: The model option to set one or more tasks or one or more workflows in the model to non-operational mode. It temporarily disables one or more tasks in one or more workflows without changing their dependencies. For more information, see nop/unnop.
	unnop: The option to return one or more workflows in the model to operational mode. For more information, see nop/unnop.

For more information, see nop/unnop.