Release notesFeature announcements

Platform 6.5.0 feature announcement

Platform 6.5 introduces FlowAI, the agentic layer of Itential Platform, plus Work Center, a purpose-built interface for operators managing workflows that require human intervention.

For a complete list of features, enhancements, and bug fixes, see the Platform 6.5.0 release notes.

FlowAI

FlowAI connects AI reasoning to deterministic, governed infrastructure automation. It gives teams the ability to design, deploy, and monitor agents that reason through complex goals and take action through existing automation assets, producing structured, auditable outcomes without sacrificing operational control.

You build agents in Agent Builder, where you define each agent’s purpose, instructions, LLM model, and tool access. Tools include Platform workflows, adapter and integration APIs, Gateway services, Lifecycle Manager actions, Compliance Plans, and other agents.

Agent Projects provide RBAC-controlled boundaries and serve as the unit of portability across environments. Agent Sessions give operators a chronological execution trace for every agent run, including reasoning steps, tool calls, and linked jobs, with the ability to pause, resume, and cancel sessions from a unified view.

  • Agent Builder: Define an agent’s purpose, instructions, LLM model, and tool access.
  • Tool access: Connect agents to Platform workflows, adapter and integration APIs, Gateway services, Lifecycle Manager actions, Compliance Plans, and other agents.
  • Agent Projects: RBAC-controlled boundaries that serve as the unit of portability across environments.
  • Agent Sessions: A chronological execution trace for every agent run, with the ability to pause, resume, and cancel sessions.

FlowAI requires a separate purchase and is available for customers running Platform 6. For details, see FlowAI overview.

Work Center

Work Center gives operators a single place to manage workflows that require human intervention. The Work Center queue surfaces all jobs with pending manual tasks in one view, with filters for assigned, unassigned, and all items.

When an operator opens a job, they see a full task timeline, the current active task, and everything needed to make an informed decision. Work Center also introduces Quick Form, a new manual task type that renders any JSON array as an interactive table for structured, per-row operator input.

Work Center is included with Platform 6.5 for all customers. A FlowAI purchase is not required. For details, see Work Center.

Gateway Manager DB import and export

Gateway Manager 1.1.1 exposes Gateway 5 database import and export as API-callable methods, available via the Itential Platform API, workflow tasks, or directly from the Gateway Manager UI. Teams can trigger configuration imports and exports programmatically without embedding iagctl in their pipelines. Both JSON and YAML formats are supported, and Git-sourced imports are available through the Platform API.

For details, see the DB Import/Export documentation.

What else shipped in Platform 6.5

  • Async task support: Workflow Engine now supports a new async task type, allowing long-running external systems to call back to the Workflow Engine on completion rather than blocking or polling.
  • Compliance Plan events: Configuration Manager now emits start and complete events for Compliance Plans, consistent with Lifecycle Manager Resource Actions. External systems can trigger workflows off Compliance Plan execution without relying on job events.

Requirements

  • Platform 6.5 or later
  • Gateway 5.5 or later — required for Extensible Secrets Management and FlowAI tool execution
  • Gateway Manager 1.1.1 or later — required for DB Import/Export and FlowAI tool execution

FlowAI requires a separate purchase and Platform 6.5 or later.

Customer action required

Customers migrating to NSO 6.7 who use doProvision with the legacy flags-based options format may see task failures, since NSO 6.7 now expects commit options in a structured object format. Customers staying on NSO versions earlier than 6.7 are not affected.

If you’re migrating to NSO 6.7, update your doProvision workflow inputs from the legacy array format:

1"options": ["dry-run=cli"]

to the new structured object format:

1"options": {
2  "dry-run": {
3    "outformat": "cli-c",
4    "reverse": ""
5  }
6}