New in AutomatePro 9.2.1 New in AutomatePro 9.2.1: teams get the need for speed and control in their ServiceNow test automation. This AutomatePro release features improved Test authoring, scheduling, and deployment.
You can parameterize reusable test blocks, schedule by folder, and run a single plan across multiple configurations—browsers, personas, locales, even releases.
Meanwhile, AutoDeploy adds merged change plans and role elevation for safer, faster releases, and AutoDoc streamlines upgrade evidence with Test Pack selection. Moreover, the app is Store-listed as compatible with Zurich, Yokohama, and Xanadu, so you can adopt confidently and keep moving. Let’s unpack what changed, why we are excited to tune in, upgrade and turn on these new features on—today.
New in AutomatePro 9.2.1: ServiceNow Test Automation
Why this AutomatePro 9.2.1 release matters for delivery speed
Upgrades slip when tests take too long to author, maintain, and schedule. 9.2.1 attacks those bottlenecks with reusable Block Parameters, folder-level scheduling, and Test Configuration Sets that fan one plan across many scenarios—so coverage rises while effort falls. Furthermore, AutomatePro+ layers AI for text-to-test and summaries when you need even more acceleration. ServiceNow Store+1
Zurich, Yokohama, Xanadu compatibility (Store-certified)
The ServiceNow Store shows version 9.2.1, released Oct 16, 2025, and compatible with Zurich, Yokohama, and Xanadu—clear go-ahead for modern instances. ServiceNow Store
Post-upgrade quick checks (2–3 min)
- Version & engine: AutomatePro → Admin → About/Version and Engine Configuration = Latest.
- Roles & license: Confirm your AutomatePro admin/test roles and license are active.
- Sanity run: Open a small Smoke Test Pack and run it once (any browser). Confirm evidence (screenshots/logs) is attached.
What’s new & how to try it (fast wins)
| Feature | Where to find it | Why it matters | 60-second “try it” example |
|---|---|---|---|
| Block Parameters & Reuse | Tests → Visual Test Plan Editor → open a block, look for Inputs/Parameters | Stop cloning blocks for small variations; maintain once, cover more. | Edit a common block (e.g., Submit Incident). Add parameters: requester, catalog_item, priority. Replace hard-coded values with {{requester}}, etc. Save. |
| Plan-level datasets | Plans → select a plan → Data/Bindings | Run the same block across many scenarios just by changing data. | Add two rows: (Alice, Laptop, P1) and (Bob, VPN, P3). Run once—see two scenario runs and shared evidence. |
| Run-time overrides | Runs → New Run (advanced/run settings) | Tweak values per run (e.g., locale, browser) without editing tests. | Start a run, set priority=P2 and locale=fr-FR. Confirm the run uses overrides in steps/evidence. |
| Scheduling & multi-configuration | Runs → Schedules (or Plan → Schedule) | Nightly coverage; matrix runs across browsers/personas/locales/releases. | Schedule the plan nightly 1:30 AM; add configs: Chrome/Edge × US/EU persona. Save and preview the run matrix. |
| One-click results & reports (AutoDoc) | Reporting → AutoDoc (from a finished run) | Instant, accurate PDFs/KBs from passing tests; great for users & audits. | Open the last run → Generate AutoDoc → pick a “How-to” template → export PDF. |
| Upgrade Readiness Report | Reporting → Readiness/Health | Simple go/no-go; shows pass rate, failures, and focus areas. | Generate report; confirm score and top failing areas feed new stories/defects. |
| AutoDeploy gates | Deploy → Pipelines/Jobs | Safer promotions with holds, approvals, smoke checks. | Create a TEST→PROD job; add “Pause for CAB” + “Run UI Smoke” gate; dry-run to see the pause. |
10-minute “first use” script
- Parameterize one block (3 min): Open your most-used block, add inputs, swap hard-coded values for tokens.
- Bind a tiny dataset (3 min): Two rows with different users/items. Run and review both scenarios.
- Schedule & report (4 min): Set a nightly run; generate AutoDoc from today’s run and share the PDF.
Troubleshooting tips
- Don’t see a panel/button? Hard refresh / clear cache and re-check roles.
- A feature is missing? Verify license/entitlements and Engine Configuration: Latest.
- Evidence empty? Ensure the runner agent is healthy and the plan has screenshots enabled.
If you tell me the block you use most (e.g., “Request Catalog Item”), I’ll turn it into a parameterized template and a ready-to-run plan dataset for you.
AutoPlan – Automated Planning, Requirements and Design
| Feature | What it does | Why it helps | Example |
|---|---|---|---|
| Streamlines planning & design | Uses guided templates to capture requirements consistently (outcomes, fields, approvals, SLAs, acceptance criteria). | Less rework and handoffs; clear traceability from demand → story → test. | Define “Request Laptop” once—build and tests follow the exact spec. |
| Eliminates copy/paste errors with auto-docs | Converts approved tests into polished Knowledge Articles and PDFs with screenshots, timestamps, and versioning. | Docs always match the system; avoids stale guides; clean audit evidence. | After a test passes, it generates “How to Request VPN” with step-by-step images. |
| Speeds development by turning requirements into tests | One click turns requirements into automated, parameterized tests covering many scenarios. | Catches issues earlier, expands coverage fast, reduces rework. | “Submit Incident” runs across users, priorities, locales by swapping data—no cloning. |
| Boosts teamwork with one place for work | Manages backlogs, sprints, epics, stories, tests, and results in a single platform with roles and notifications. | Shared visibility, fewer tools to juggle, stronger governance. | PO tracks scope, Dev sees AC, QA runs tests, stakeholders view live reports—all linked. |
AutomatePro AutoTest
Improving AutoTest Capabilities, with improved Block Parameters to reuse, scale, accelerate.
- Build no-code tests tailored to your ServiceNow
- Expand coverage with simpler creation
- Schedule runs (continuous or on-demand)
- Keep test data/results secure in ServiceNow
- Get one-click results and reports with Parameterized Blocks.
Set inputs once (user, item, priority) and bind values in the plan or at run time. Result: fewer assets, broader coverage, faster maintenance. Define inputs (e.g., user, catalog item, priority) once in the Visual Test Plan Editor, then bind values at plan or run time. Consequently, you manage fewer assets, achieve wider coverage, and maintain tests faster.
Add parameters (from your screenshot)
- Open the Block → Inputs/Parameters.
- Click (or drag) a type from the right: String, Number, Checkbox, Choice, Reference, Output.
- Rename it (e.g.,
short_description) → click the gear to set Default, Required, or options (for Choice/Reference/Output). - Save.
What each type does (and how to use it)
| Type | When to use | What value looks like | In your steps, use token |
|---|---|---|---|
| String | Free text (short desc, comments) | e.g., Laptop issue | {{short_description}} |
| Number | Numeric fields (quantity, cost) | e.g., 3 | {{quantity}} |
| Checkbox | True/False fields | true or false | {{major_incident}} |
| Choice | Dropdowns (Priority, Category) | One of the allowed labels/values | {{priority}} |
| Reference | Lookups to a table (Caller, Requested for) | A record (often by display value or sys_id) | {{caller}} |
| Output | Capture a value to reuse later (e.g., Incident Number) | Filled by the block at runtime | {{incident_number}} (after it’s set) |
💡 Where to put tokens: anywhere the step accepts a value (e.g., “Set field”, “Click option”, “Assert equals”). Replace hard-coded text with
{{parameter_name}}.
Minimal Working Example — Create Incident (all parameter types)
Parameters to add (in Parameter Builder)
| Parameter | Type | Default / Options | Used in step (token) | Notes |
|---|---|---|---|---|
short_description | String | Laptop not connecting | {{short_description}} | Free text |
priority | Choice | 3 - Moderate (options: 1 - Critical, 2 - High, 3 - Moderate, 4 - Low) | {{priority}} | Add allowed values exactly as in UI |
caller | Reference → sys_user | Abel Tuter | {{caller}} | Use display value or sys_id per your step |
major_incident | Checkbox | false | {{major_incident}} | True/False toggle |
affected_users | Number | 1 | {{affected_users}} | Any numeric field you track (e.g., “Affected users”) |
incident_number | Output | — | {{incident_number}} (later use) | Capture number after submit |
Tip: Set Default Value, Mandatory, Active, and Order as needed. No JSON required—the builder stores advanced config.
Use tokens in your block steps
- Set Short description =
{{short_description}} - Set Priority =
{{priority}} - Set Caller =
{{caller}} - Set Major incident =
{{major_incident}} - Set Affected users =
{{affected_users}} - Submit the incident
- Capture Number → Output
incident_number - (Optional) Assert Number visible =
{{incident_number}}
Bind at run time (no cloning)
- Run A (default persona, Chrome):
priority=3 - Moderate,caller=Abel Tuter,major_incident=false,affected_users=1 - Run B (Config Set — HR persona, Edge):
priority=2 - High,caller=Beth Anglin,major_incident=true,affected_users=25
Choice / Reference / Output specifics (quick)
- Choice: Gear → add labels/values exactly as UI shows; set a default.
- Reference: Gear → pick table
sys_user; choose display or sys_id per your step. - Output: Add
incident_number; map the post-submit value into it; reuse in later steps/lists:{{incident_number}}.
Sanity checklist
- Clear names (no spaces), sensible defaults.
- Steps use tokens (not hard-coded values).
- Block saved; plan points to the latest version.
- Values bound in Plan or via Configuration Set (browser/persona/locale/release).
- Run shows chosen values in screenshots/logs; Output is populated.
Bulk list editing for plans, blocks, environments
Standardize taxonomy in minutes. Multi-edit categorization fields across list views to align tags, owners, and domains—vital for clean dashboards and smarter scheduling downstream. ServiceNow Store
ServiceNow Test Configuration Sets: one plan, many configs
Run a single plan across multiple Test Configurations—different browsers, personas, locales, or releases—without duplication. Therefore, you boost breadth while keeping authoring lean. ServiceNow Store
Folder-aware scheduling for nightly regression
Organize plans by product or domain, then schedule at the folder level. As you add plans to a folder, coverage expands automatically—no calendar sprawl. ServiceNow Store
AutoDoc Upgrade readiness automation from Test Packs
Generate Upgrade Readiness Reports scoped by successful Test Pack run selection. Executives see impact quickly; auditors get traceability from requirement to run—without extra swivel-chair work.
| Feature | What it is | Why it’s a benefit | Example |
|---|---|---|---|
| Impact scan & inventory | Automatically lists apps, plugins, customizations, and deprecated APIs likely to break in the new release. | Fewer surprises; you know what to test first. | Flags 12 custom UI Policies and a deprecated API before upgrading Washington → Xanadu. |
| Prebuilt upgrade test packs | Curated suites (smoke + regression) mapped to common ServiceNow areas. | Fast start; broad coverage without hand-building tests. | Runs “Core ITSM Upgrade Pack” covering Incident, Request, Change, KB. |
| Data-safe clone & seed | Spins up a TEST/UAT copy with scrubbed data for realistic runs. | Realistic testing without risking live data. | Clones PROD to UAT, masks PII, seeds 50 sample requests for test replay. |
| Parameterized reusable tests | One test runs many scenarios by swapping inputs (user, browser, locale). | More coverage with fewer scripts to maintain. | “Submit Incident” runs for 6 roles × 3 browsers × 2 locales. |
| ATF smoke gate + AutoTest breadth | Uses ATF for quick UI smoke; AutoTest for deeper workflows and evidence. | Safer deploys and fewer regressions. | ATF checks forms open; AutoTest validates SLAs, approvals, emails. |
| Scheduled, gated runs | Aligns runs with change windows, adds approvals/holds where needed. | Control and compliance without babysitting. | Schedule UAT suite Sat 1–3 AM; pause for CAB approval before PROD. |
| AutoDoc evidence & reports | Turns passing tests into Knowledge Articles/PDFs with screenshots and timestamps. | Instant, accurate documentation for users and auditors. | Generates “How to Request VPN” PDF from the test run results. |
| Readiness score & defect loop | Produces a simple score (pass rate, critical failures) and opens defects for failures. | Clear “go/no-go” signal; faster fixes. | Readiness = 92%; 3 P1 defects auto-created with steps to reproduce. |
AutoDeploy change plans merge and role elevation for safer releases
Unify overlapping change work with Merge Change Plans (prior conflict decisions persist). Add Elevate Role steps when stages require privileged actions. Meanwhile, improved remote lookups and richer artefacts increase transparency and auditability. As a result, deployments move faster with less risk.
| Feature | What it does (plain English) | Why it’s valuable | Example |
|---|---|---|---|
| No-code deployments | Moves approved changes from DEV/TEST to PROD without scripting. | Faster, consistent releases for any team member. | Click “Deploy” to promote update set REQ_Laptop_v3 to TEST. |
| Scheduled or on-demand | Run deployments on a timer or immediately. | Fits change windows; reduces night/weekend work. | Schedule TEST at 3:00 AM, or deploy now for a hotfix. |
| Pre/Post-deploy smoke tests | Runs quick checks before/after deploy and captures evidence. | Catches breakages early; proof for auditors. | Execute UI-Smoke-Catalog and attach screenshots to the report. |
| Change windows & blackout rules | Enforces allowed times; blocks deploys during freezes. | Prevents risky off-hours or freeze-period changes. | Allow PROD only Sat 1–3 AM; block during monthly freeze. |
| Approvals & CAB gates | Stops at approval steps until authorized. | Adds control and accountability. | Pause until CAB approves CHG012345, then continue. |
| Manual intervention points | Inserts “Hold for human review” checkpoints. | Human oversight for sensitive steps. | After TEST deploy, wait for QA Lead to click “Continue.” |
| Environment targeting & promotion | Selects targets and promotes in sequence. | Standard, repeatable paths; fewer mistakes. | DEV → TEST → UAT → PROD with the same checklist. |
| Full audit trail & reporting | Logs who did what, when, where—exports reports. | Compliance, traceability, easy retros. | Auto-email a PDF/CSV “Deployment Summary” to the team. |
| Rollback on failure | Reverts changes if checks fail. | Safer deploys; quick recovery. | If smoke fails, auto-revert update set and notify owners. |
Getting started: upgrade 9.1.0 → 9.2.1 in three steps (DEV→TEST→PROD)
- Pre-checks: confirm Store compatibility, elevate required roles, verify license registration, and set Engine Configuration → Latest. ServiceNow Store
- Update in DEV: Application Manager → Proceed to update; repair if prompted, clear cache, then run a small smoke Test Pack. ServiceNow Store
- Promote: repeat validation in TEST, then PROD; finally, generate an Upgrade Readiness Report to confirm outcomes. ServiceNow Store
The Visual Editor- Form Builder Editor
Here is an introduction of the new Visual Editor Form Builder capabilities, before and after.
| Capability | New Form Builder (Visual Editor) | Before (classic/ServiceNow-only forms) | Why it matters |
|---|---|---|---|
| Build UX | Drag-and-drop, WYSIWYG layout | Field-by-field admin forms | Faster, no-code authoring |
| Reuse across records | Reusable Form Templates assignable to many entities (Test Plan/Run, Defect, Epic, Story, Task, Sprint) | Per-form customization, hard to reuse | One template, many places |
| Governance & versioning | Central template store with version control and export/import | Ad hoc copies, manual moves | Consistent standards across envs |
| Visibility rules | Point-and-click conditions + optional callbacks | Scripted/UI policy heavy | Low-code logic; code only when needed |
| Field control | Defaults, Mandatory/Active, Order, Help, label/tag | Basic properties vary by form | Consistent data entry experience |
| Rich inputs | String, Number, Checkbox, Choice (incl. custom lists), Reference (table+query) | Limited or custom build each time | Cover most use cases without dev |
| Reference lookups | Table + filtered query, columns, popup/lookup toggles | Manual config or scripting | Precise, guided selection |
| Custom choices | Inline JSON list or pull from table/field | Script/DB setup required | Quick business picklists |
| Live preview | See changes immediately (modified = light red; deleted = faded) | Save/refresh cycles | Faster iterations, fewer mistakes |
| Data-in-form editing | Edit instance data on an entity’s Form Builder tab; auto re-render on callback changes | Switch between admin and record views | No swivel-chair; fewer errors |
| Reporting & artifacts | Fields flow into Test Run/Design Doc & State Management | Manual mapping/exports | Auto-documented, audit-ready outputs |
| Portability | Export/Import templates + instance data | Manual cloning/scripts | Reliable promotion between environments. |
| Location | Navigation Path | Purpose / Use | Who (Roles) | Notes |
|---|---|---|---|---|
| Primary (Authoring & Governance) | Admin → Configuration → Form Templates (Visual Editor) | Create, version, export/import Form Templates; manage global rules | AMP_Administrator, AMP_FormBuilder_Admin | Centralized governance; single source of truth |
| Contextual (On Records) | Entity tabs: Test Plan / Test Run / Defect / Epic / Story / Task / Sprint → Form Builder tab | View/edit instance data using the template; live re-render via callbacks | Record owners, AMP_AutoTest_Admin (as needed) | Best for day-to-day updates; respects visibility rules |
| Quick Access (Design) | AutoTest → Design → Form Templates (filtered to Test Plan/Run) | Fast access for QA authors to tweak templates used in testing | QA leads, power users | Optional shortcut; inherits admin templates |
| Portability (Move Between Env’s) | Control Console → Export/Import → Form Builder | Promote templates + instance data across environments | Release/Platform admins | Use for upgrades, clone-downs, DR drills |
FAQs (featured-snippet targets)
Where do I enable Block Parameters?
Open a Test Block in the Visual Test Plan Editor, then use the Parameters panel; bind values at plan/run time. ServiceNow Store
Do I need AutomatePro+ for AI text-to-test?
Yes—AI text-to-test and summaries are delivered by the AutomatePro+ Store app; check license and install if required. ServiceNow Store
Is 9.2.1 compatible with Zurich, Yokohama, or Xanadu?
Yes—those versions appear on the current Store page for 9.2.1. ServiceNow Store
Other New in AutomatePro 9.2.1 Resources
- AutomatePro Managed Service Value
- Configure Deployment Plan Stages :: AutomatePro Docs
- Ditch Manual Agile: Automate the Sprint with Audit-Ready Evidence
- Lloyds Banking Group Slashed Testing Time by 99% : AutomatePro
- Premiering AutomatePro 9.0.2 Breakthrough Features
