What's New in Now Assist for Creator: Australia Early Access Release
Table of Contents
Articles Hub
Want to see all of our articles related to Now Assist for Creator?
Now Assist for Creator: Hub
Overview
The first Australia Store release is here. If you've been following along since Zurich, you know Build Agent started as an IDE-focused tool for pro developers working in Fluent. This release expands where Build Agent runs, what it can build, and the models powering it.
Requirements: Australia Early Access family release. (With the exception of some of the skill updates noted below.)
Here's what's shipping on March 12th.
Build Agent in ServiceNow Studio
This was the most requested change we heard after Zurich: "I don't work in IDE. When is this coming to Studio?"
The short answer: NOW.
Why this matters: Previously, Build Agent was restricted to the ServiceNow IDE, primarily catering to professional developers familiar with that setup. However, App Owners, Business Analysts, Platform Admins, and Citizen Developers—those who create and manage much of what runs on ServiceNow—typically work in Studio. Forcing them to switch from Studio to IDE for AI-assisted development disrupted their workflow, removed them from their familiar environment, and required extra effort to reconcile changes. This inconvenience discouraged many Studio users from utilizing Build Agent's capabilities.
What's shipping: Build Agent is now available in ServiceNow Studio with the same core capabilities: planning, conversational development, and build. If you've used Build Agent in IDE, you'll feel at home. If Studio is your primary environment, you no longer have to choose between your familiar workspace and AI assistance. Build Agent tracks your changes in Update Sets so you can deploy through traditional platform paths (update sets, app repo, pipelines, source control).
The conversational interface makes it accessible to a broader range of builders, though familiarity with ServiceNow concepts like tables, roles, and scopes will help you get the most out of it.
The screenshots tell the story better than I can: you can build a complete application (tables, roles, ACLs, seed data, flows) all from a conversation in Studio. The planning tool shows you exactly what Build Agent intends to create before it executes, so you're not surprised by what ends up in your instance.
[Screenshot: Build Agent in Studio showing Group Coffee Ordering app with detailed plan]
Interviewing and planning are worth calling out. Build Agent can interview you to clarify requirements before it starts building: "What roles need access? Should checkouts create incidents when overdue? Do you need cross-scope writes to the global Incident table?" It takes your initial idea ("I need an app to track equipment loans") and helps you think through details you might not have specified. Then it generates a plan showing exactly what it intends to create. You review, adjust, and approve before anything gets built.
Updated AI Models
Build Agent now supports Claude Opus 4.6 and Claude Sonnet 4.5, upgraded from Claude 4 Sonnet, leveraging our partnership announcement with Anthropic.
Why the models matter: Complex development tasks (building applications with multiple tables, security models, flows, and UI) require multi-step reasoning. The model needs to plan, execute, validate, and maintain coherence across extended conversations. The upgraded models handle these interdependent decisions more reliably, with better code quality and performance, particularly for longer sessions where earlier context informs later steps.
Global Scope and App Support
Build Agent now works beyond scoped applications (your custom apps) to support global scope, where platform-wide tables like Incident, Problem, and Change live.
The context: A significant portion of ServiceNow development is customizing and extending out-of-the-box applications (Incident, Problem, Change, and the like) rather than building net-new apps from scratch.
Previously, Build Agent was limited to scoped applications, isolated from the platform's core tables.
What's shipping:
Global scope editing. Build Agent can now operate in global scope alongside scoped apps. You can add fields to Incident, Problem, Change, and other OOB tables, then extend them with business rules, client scripts, ACLs, and other supported metadata.
Cross-scope work. Build Agent can create flows and business rules that interact across scope boundaries, and manage cross-scope privileges. Complex multi-scope integrations may still require iterative work across multiple conversations and manual verification, but the foundational capabilities are there.
Discovery. Build Agent can query and discover existing metadata: find all business rules on Incident, inspect table schemas, or audit what's deployed in a scope before making changes.
Supported metadata types include ACLs, ATF tests, flows, business rules, client scripts, lists, system properties, roles, scripted REST APIs, tables, and UI pages. Customizations requiring other metadata types may have limited or no coverage.
A concrete example: The screenshot shows an Asset Checkout App, a custom scoped application that writes to the global Incident table. Build Agent created a scoped app that automatically generates Incidents when IT assets become overdue. That's cross-scope write access, configured entirely through Build Agent.
[Screenshot: Asset Checkout App using a Workspace Dashboard showing overdue items with related Incident record]
Build Agent Goes Platform Native
This is the bigger story for developers who've been waiting to use Build Agent for real work.
The problem we heard: "Build Agent is a solid start for scripts and business rules, but when can I get broader support for ServiceNow platform components?"
Fair point. This release significantly expands metadata coverage.
What's shipping: Build Agent now supports 35+ metadata types across 11 domains. Some metadata types require SDK 4.2.0 or 4.3.0+. Here's what that actually means:
Server-Side Logic
Business Rules, Script Includes, System Properties, JS Modules. The foundational scripting layer most developers start with.
Client-Side Logic
Client Scripts, UI Policies, Catalog Client Scripts. The browser-side behavior that makes forms actually work the way users expect.
User Interfaces
This is where it gets interesting. Build Agent can now create:
- React-based UI Pages using the Fluent DSL (custom interfaces built with React)
- Platform form configuration: Views, View Rules, UI Policies, UI Actions, built-in Formatters (Activity streams, Process Flows, Checklists), and form layout via section and element configuration
- Platform list configuration: Lists with column ordering and aggregates, List Controls for role-based button visibility
- Application Menus and Modules for the navigator
- Workspaces with dashboards, list views, and detail forms
Two paths to UI: React UI Pages for custom interfaces that go beyond platform forms, or Platform Views and UI Policies for native form and list behavior configured declaratively. Build Agent supports both.
Automation
Workflow Flows and Email Notifications. Create and edit flows with triggers, actions, and flow logic via natural language.
[Screenshot: Asset Checkout App examining a flow created using Build Agent and adding a new Dashboard for examining IT assets statuses and active incidents]
Service Catalog
Record Producers, Catalog Items, Variables and Variable Sets, Catalog UI Policies. If you're building request-based workflows, this is core coverage.
Data Modeling
Tables and Columns, Relationships, Seed Data and Records. Build Agent can scaffold your data model and populate it with starter data.
Security
ACLs, Roles, Data Filters, Cross-Scope Privileges, Security Attributes. This is critical for production apps. Build Agent now generates the security layer alongside everything else.
Integrations
Scripted REST APIs, LDAP/External connections, Data Sources.
Testing
11 ATF test categories: Form, Server, REST, Catalog, Email, App Nav, Reporting, and more.
DevOps Workflow
Search and Discovery, Build and Validate, Deploy to Instance.
Data Management
Import and Transform sets.
Why this matters for your workflow: For many common application patterns (tables with security, forms with automation, catalog-driven workflows), Build Agent can now deliver complete, deployable results. Complex scenarios may still require manual configuration, but the gap between "AI-assisted prototype" and "production-ready app" has narrowed significantly.
Fewer handoffs between AI-assisted and manual configuration. Consistent patterns across deployments. Less rework.
Additional Agent and Skill Updates
Beyond Build Agent, this release includes a new agent, an enhanced skill, and a brand new skill. Note the different family release requirements below.
Module Generation Agent (Australia EA required)
Creating app menus and modules means navigating multiple configurations: lists, forms, dashboards. Each module needs individual setup.
Module Generation Agent lets you describe the modules you need in natural language. It handles table, view, and role lookup automatically. Example prompts and a collapsible AI panel provide guided entry points for new builders. Faster module creation, lower barrier to entry.
Catalog Item Generation: Edit and Iterate (Zurich Patch 7+)
Catalog admins spend most of their time iterating on existing items, not building from scratch. Re-generating entire catalog items to make small changes wastes time and loses customizations.
This release adds:
- Edit Existing Catalog Items: Add variables, tweak UI policies, or overwrite items conversationally
- Multi-Action UI Policies: Define one condition with multiple actions. Now Assist auto-generates descriptions
- Creation Mode Choice: Choose between Now Assist or manual creation when starting new items
- Item Settings Configuration: Conversational config of Access, Fulfillment, Portal settings, and Location values
Iterative refinement without re-generating from scratch. End-to-end catalog item setup without leaving the conversational interface.
Theme Builder: Theme Assist (Zurich Patch 7+)
Creating branded themes requires design expertise most admins don't have. Manual theme configuration is time-consuming and inconsistent.
Theme Assist generates themes from text or image prompts within the Create a theme wizard. Upload a brand image or describe your style, and Theme Assist generates a complete theme with color palette recommendations.
Admins can quickly generate branded themes without design expertise. Consistent visual identity across portals and workspaces.
Getting Started
Requirements:
- Australia Early Access family release (required for Build Agent and Module Generation Agent)
- Zurich Patch 7+ for Catalog Item Generation and Theme Assist
- Now Assist for Creator subscription
- Free Build Agent trial available via the Store and PDIs.
Available: March 12th, 2026 (Australia Store Release 1)
What's Next
Looking ahead, we're focused on several themes:
Zurich backports. Some Australia capabilities will be backported to Zurich in upcoming patches. Stay tuned for specifics.
Continued metadata expansion. Converting additional platform components to Fluent, broadening what Build Agent can create and modify.
Interoperability via MCP. Expanding Model Context Protocol integrations so Build Agent can work with external tools and development workflows.
Search and semantic search. Improving how Build Agent finds and understands existing instance metadata before generating new artifacts. The goal: less duplication, more context-aware output.
Custom prompts and additional context. Giving builders more control over how Build Agent behaves, including custom prompt configurations tailored to team patterns and preferences.
Test coverage automation. Reducing the gap between building and testing. AI-assisted ATF test generation tied to the artifacts you create.
App lifecycle improvements. Previewing capabilities around understanding update sets and generating release notes automatically.
UI Builder Agent enhancements. Continued improvements to knowledge and community content integration, surfacing more relevant guidance in context.
And one more thing worth teasing: Build Agent building agents. Imagine your own custom app with its very own Now Assist panel. More to come.
Conclusion
We're genuinely excited about the future of Now Assist for Creator. Every release brings us closer to a vision where the platform gets out of your way and lets you focus on what matters: building what you actually want to build. Whether that's automating a workflow that's been on your backlog for months, extending a core process to finally work the way your team needs, or prototyping an idea that's been stuck in your head, we want Build Agent and the full portfolio of Now Assist for Creator skills to be the accelerant that makes it happen.
Try it on something real. Build an app you've been putting off. Extend an existing workflow. Let us know what works and what doesn't in the comments. That feedback directly shapes what we prioritize next.
And we'd love to hear your success stories. What have you built with Build Agent? What workflows has Catalog Item Generation or Flow Generation helped you ship faster? Drop a comment below and share with the community. Your wins inspire others, and honestly, they inspire us too.
If you found this guide helpful, consider sharing it with peers or teams. If you like this type of content, please mark the article "Helpful", and leave us your topic ideas in the comments.
Check out the Now Assist for Creator: Hub for more resources.
