Platform : Platform apps : Concepts : Metadata
Metadata
Metadata is used to uniquely identify an app. Metadata is available at various levels in the domain model.
App metadata
Metadata
Description
Comment
App UUID
UUID that uniquely identifies an app across all Planon instances.
Only for Planon internal references.
• Stored in database.
• Can be used in Planon caches.
Used in the App license.
Used to identify apps during installation. Since a UUID uniquely represents an app, we can handle name changes, in theory.
Partner Identifier
Sub-concepts:
• customer
• department
Uniquely identifies a Partner.
Is a combination of the customer (name), and partner (for partners) or apps (for customers that build their own apps), concatenated with a dot (.).
Restrictions
• Limit to [a-z0-9] (minimum 3, maximum 50)
• Exactly one dot (.)
Public references
• Visible in the AppCenter TSI.
• Visible in Planon configuration (TSI).
• Visible in URLs.
App Name
Describes an app. Managed by Partner.
* 
Unique in the scope of a Partner Identifier.
The app name can change; the consequences are for the app developer.
This affects the app upgrade.
* 
Soft references to the namespace will not be updated. However, they can be detected by looking up the App UUID.
Restrictions
• Limit to [a-z0-9] (minimum 3, maximum50)
• No dots (.)
Public references
• Visible in the AppCenter TSI.
• Visible in Planon configuration (TSI).
• Visible in URLs.
Module name
Metadata
Description
Comment
Module name
Describes an app module. Managed by Partner.
The Module name can change, but is unlikely to; consequences are for the app developer.
This will affects the app upgrade.
* 
Changing the module name will result in app settings being lost.
Restrictions
• Limit to [a-z0-9] (minimum 3)
• No dots (.)
Publish references
• Visible in the AppCenter TSI.
• Visible in Planon configuration (TSI).
• Visible in URLs.