Every skipped record, triaged.
Phyllis works through the skipped-record list and recommends keep, merge or revert for each one — with the reason, cited to the record.
ServiceNow supports the current and previous family release, so every instance upgrades at least once a year. Phyllis takes the slow part — skipped records, regression tests, the release — off your team’s plate.
Triage the skipped records from the Australia upgrade on acme-dev.@ for records · / for commands
Phyllis works through the skipped-record list and recommends keep, merge or revert for each one — with the reason, cited to the record.
She builds and runs ATF for what the upgrade touched, so the evidence exists before the sign-off meeting does.
Upgrade readiness is an assessment like any other — scored, cited, and it ends in a report.
Fixes and tests batch into a release and move to your test instance from chat. Production stays on your Deployments page.
Hundreds of checks across every category — and unlike the native engine, Phyllis self-heals findings on your approval.
Read the use casePhyllis builds and extends complete custom applications — any data model, automation or access model — grounded in your live instance and staged for your approval.
Read the use casePhyllis builds and extends your entire integration layer — any connection, credential or retry rule — grounded in your live instance and staged for your approval.
Read the use caseNo — it works on top of it. Phyllis reads the upgrade history and skipped-record log, recommends a disposition for each record with the reason, and builds the tests and release around it.
Not from chat. She prepares and releases to test and UAT on your approval; production is promoted from your Deployments page under your change process.
It runs as an accelerator and ends in a scored report — a document you can share with people who have never opened Phyllis.
The everyday work — backlog, fixes, questions and health — done in your instance and scanned after every change.
Explore RunITSM, HRSD, CSM and every product in between — planned, built, tested and ready to promote.
Explore Implement| Finding ↓ | Records | Severity | Remediation |
|---|---|---|---|
| CIs without a servicecmdb_ci_server | 212 | Map to application services | |
| Duplicate server CIscmdb_ci_server | 87 | Reconcile on serial number | |
| Stale discovery sourcecmdb_ci | 1,340 | Retire or rediscover | |
| Class not in CSDM 5cmdb_ci_appl | 46 | Move to the business application | |
| Missing ownercmdb_ci_service | 19 | Assign a managed-by group |
cmdb_ci_server · no cmdb_rel_ci to a service · 212 rowsCMDB, tech debt, performance, licences and AI readiness — each ends in a report you can hand over.
Explore Assess