Skip to content

Tenant Notes

Tenant notes provide an organization-scoped operational record for migrations, skipped work, validation results, and other support decisions. They keep this context with the tenant instead of relying on external chat history or database comments.

Access

Tenant notes are available only to platform ROOT and SUPPORT users.

  1. Open Organizations.
  2. Open the organization's Edit page.
  3. Select Tenant Notes.

The page shows each note's summary, category, status, details, source reference, and last-updated time in UTC. Tenant administrators and ordinary tenant users cannot access this view.

Attribute-query migrations

Create or update a tenant note whenever catalog attribute data or Dynamic Valid Values definitions are migrated. Record:

  • which attributes and items were normalized;
  • which canonical lookup definitions were created and tested;
  • whether obsolete item AttributesJSON values were cleared;
  • any validation counts or limitations;
  • why a legacy SQL/XML definition was skipped or retained.

Skipped legacy XML may remain read-only for forensic context, but runtime execution stays disabled. A note does not activate a legacy query or replace the canonical lookup definition.

Status guidance

  • Resolved — migration and validation completed.
  • Skipped — no safe canonical replacement could be validated; explain why.
  • Open — follow-up work is still required.

Include a source reference when one is available, such as a migration checklist, support case, or deployment record. Do not store passwords, API keys, connection strings, or other secrets in tenant notes.