Reference: model
The following options can be specified for an model tag:
Name | Required | Details |
---|---|---|
| required | Unique identifier for this model. Used anywhere that code needs to reference the object. |
| required | Human-readable label for the object. Used wherever it is displayed to a user. |
| optional | Specify whether a model is |
sensitive
classification
sensitive
classificationFor apps that process personal data, you can classify a data model as sensitive. This ensures minimal data retention periods in order to comply with regulations like the EU's GDPR. If a model is marked as sensitive
, all audit logs entries of objects of that model type will be deleted after 30 days. For example, if a sensitive
object gets created, the audit log entry will be deleted 30 days after the creation date. If the object gets updated or deleted, the audit log entry for the update will get deleted 30 days after the update date.
We also store a backup of the audit log for an additional 30 days, which means that the data will be completely deleted after 60 days.
If the model's classification is set as standard
, or isn't specified, all audit log entries for that model will be deleted after 3 years plus 30 days of backup window.
Nested Tags
The following can be placed inside a model
tag:
Nested Element | Details |
---|---|
| A field (property) of the object. |
| Defines relationships between objects. If you are specifying a one-to-many relationship between objects, and this model is one of the "many" objects that belongs to another model, you need to specify a |
| Defines relationships between objects. If you are specifying a one-to-many relationship between objects, and this model has many objects of another model that belong to it, you need to specify a |
| Defines an index for the model. For details, see App Indexing. |
| Defines how an object should be displayed to the user by default (for example, in a list). See XML String Formatting for details on the format. |
Last updated