Catalog Reference

Catalogs exchange reusable document resources between Suite installations. The functional setup is described in Catalogs.

Exchange model

A catalog package contains versioned resources such as templates, stencils, themes, assets, and related metadata. The current exchange model uses catalog schema version 4.

Catalog consumers should track:

The catalog source.
The selected resource version.
Whether a local copy was changed after import.
The fingerprint or comparison result used to detect changes.

Versioning

Use semantic versioning for shared resources. Patch changes should be safe corrections, minor changes should add compatible behavior, and major changes should be reviewed before automatic adoption.

Operational guidance

Do not treat catalog import as a production deployment. Import first, review the resulting templates and dependencies, then publish and deploy through the normal release flow.