S
Simpleasyty
Help Center — Schema reconciliation and processes
GETTING STARTED
IntroductionQuick start
CREATE A SCHEMA
Create a schema from a templateCreate a schema from scratch
SCHEMA TEMPLATES
Security Risk RegisterISO 27001 Document ControlSOC 2 Evidence RegisterPolicy ManagementThird-Party RiskData ClassificationApplication PortfolioControlled DocumentArchitecture Decision RecordInformation Asset RegisterBusiness Continuity RegisterGDPR Processing Activity
IMPORT
Import a JSON or YAML schema packageImport Page Properties
FIELD TYPES
Schema field typesText fieldsNumber fieldsYes / No fieldsSingle choice fieldsDate / Time fieldsEmail fieldsURL fieldsConfluence reference fieldsList fieldsField group fields
MANAGE SCHEMAS
Manage schemasIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair metadata
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
STORAGE & PRIVACY
Data residencyStorage in ForgeRetention and deletion
COMPLIANCE
Compliance workflowsMetadata, history and revisions
ADMINISTRATION & TROUBLESHOOTING
Import and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports

ADMINISTRATION & TROUBLESHOOTING

Schema reconciliation and processes

Apply schema changes responsibly when metadata already exists.

Review impact

When a definition change affects saved metadata, the update flow previews its impact and can ask for decisions before it is saved.

Track background work

The Processes tab shows reconciliation and cleanup jobs. Schema deletion hides the schema immediately and schedules removal of its SQL data, retained metadata history and known matching macros on affected pages.

Why reconciliation exists

Changing a schema does not silently rewrite every saved document. The update flow previews the impact of a definition change so an administrator can understand which metadata need validation, repair or reindexing.

After save, background reconciliation processes work through affected metadata. The Processes view is the place to monitor that work instead of assuming a large update is immediate.

Deletion and cleanup

Deleting a schema hides it immediately and schedules removal of its SQL data, retained metadata history and known matching macros on affected pages. Follow cleanup progress in the Processes tab. Review the impact carefully: deleting a schema is different from hiding a capture macro on one page.