Creating a Service Plan audit
Edits applied
- Prose rename: "Manage and Deploy Service Plans" → "Manage and Deploy Asset Service Plans" (1 occurrence, prose nav instruction). Catalog entry is "Manage and Deploy Asset Service Plans" (Service Plans 1 category).
- Recipe fix:
ClickMenu "Manage and Deploy Service Plans"→ClickMenu "Manage and Deploy Asset Service Plans"to match the catalog-confirmed name. - Alt text update: "The Manage and Deploy Service Plans screen" → "The Manage and Deploy Asset Service Plans screen" to match the renamed menu.
- Prose rename: "Create a new Service Plan for an Asset" → "Create a New Asset Service Plan for an Asset" (1 occurrence, prose nav instruction). Catalog entry is "Create a New Asset Service Plan for an Asset" (Maintenance > Servicing).
- Recipe fix: bare ID
<!-- robot: pm-new-service-plan-dialog -->→<!-- robot: manual - New service plan dialog requires asset selection in the asset editor context; not reachable from sidebar navigation alone -->. This screenshot shows asset service data inside the Asset Editor — inherently a transient state requiring a specific asset.
Flagged for human review
- "Manage Service Plans" menu name in prose (line 22): Prose says "the Manage Service Plans option in the Manage Service Processes screen". Catalog has "Manage Service Plans" under Service Processes category, which confirms this is a page-action on the Manage Service Processes screen. The prose is accurate; no change needed, but flagging for awareness.
- "Service Plans Menu > Generate All Work Orders" (line 13 of overview.md): Cross-reference — this file references the Service Plans menu. In creating-a-service-plan.md line 29, "use the Service Plans menu and button above the Manage screen" — the "Service Plans" page-action menu exists per catalog (Service Plans Menu category). No issue, but the button name is not catalog-verified.
Notes
- The bare ID was on the first screenshot (asset service data before creating a plan). Correctly marked manual since it requires editing a specific asset.