Mapping and Visualization

Map Builder

High-complexity builder flow that should move after the core platform patterns are proven.

Migration wave 4Planned

Source coverage

Current widget sources

/mapbuilder.html, /mapbuilder2.html

The app shell can use this manifest metadata to drive routes, entitlements, audit policies, and the eventual migration checklist for each tool.

Capabilities

Execution pattern

previewbackupdryRunlongRunningJob

Permissions

RBAC contract

tool.map-builder.viewtool.map-builder.portal-readtool.map-builder.dry-runtool.map-builder.portal-write

Migration checklist

What to build for this tool

  • Extract LogicMonitor request logic into the shared client layer.
  • Move tool state and validation into typed React modules.
  • Wrap mutating actions with preview, backup, and audit hooks where required.
  • Attach route protection using the permissions declared in the manifest.

Next action

Implementation handoff

This page is intentionally metadata-driven. As we port each tool, the manifest becomes the contract between navigation, authorization, audit, and execution.

Return to platform overview