AnnotationClass
Provides a namespace mechanism to prevent clashes of Annotation names, especially if they are generated from other systems where we cannot control the naming. For example, VMware provides a mechanism for custom attributes that we replicate.
erDiagram
AnnotationClass ||--o{ Annotation : "AnnotationClassID"
Fields
| Field |
Type |
Description |
| AnnotatedObjectName |
string |
Name of the annotated object (table) |
| Created |
datetime |
Date/Time the class was created |
| DefaultVisible |
boolean |
Default visibility in grids for new annotations of this class |
| DefaultVisibleInColumnChooser |
boolean |
Default visibility in grids column chooser for new annotations of this class |
| Guid |
guid |
A unique identifier set by the creator of the annotation. Cannot be changed after creation (Name can be changed). Use the GUID in combination with AnnotatedObjectName when referencing annotations in custom queries. |
| ID |
numeric |
Internal ID for the AnnotationClass entity (Primary Key) |
| Name |
string |
Name of the annotation class |
Referenced by
| Table |
Column Name |
Description |
| Annotation |
AnnotationClassID |
Annotations can be used to store user-defined attributes of a source system with any OctoSAM entity. Not to be used to store system defined attributes of source systems (extend the schema to hold such attributes). Annotations are not used for internal data logic within OctoSAM, but can be referenced in custom queries and reports. |