Difference between revisions of "CONTEXT"
Line 4: | Line 4: | ||
| internalname = Context | | internalname = Context | ||
| inheritance = {{SYSTEMOBJECT}} | | inheritance = {{SYSTEMOBJECT}} | ||
− | | namespace = System | + | | namespace = System.ACM |
| image = [[File:SY_CONTEXT.png|220px]] | | image = [[File:SY_CONTEXT.png|220px]] | ||
| imagecaption = Context | | imagecaption = Context |
Revision as of 11:13, 23 March 2015
Context | |
---|---|
Name | CONTEXT |
Namespace | System.ACM |
Internal Name | Context |
TypeString | UBIK.Kernel.MetaClass |
RuntimeType | UBIK.Content.ACM.AdjustableRightsContext |
Purpose | Configure contexts for ACM |
Version | 2+ |
A context defines the usage (use case) of data access and the scope of object types (MetaClasses) and their properties that are available in its context. There might be different contexts scopes defined for read access and write access for the same MetaClass.
The contexts are related to an Application via the SYSREL CONTEXT relation.
Own Properties
Name | Data type | Comment |
---|---|---|
VIEW | Guid | Reference to a view defining the objects' hierarchy |
DATETIMEFORMAT | String | Configure a user specific date / time format to be used for visualizing date / time values on the client |
METADEFINITION | XML | Released MetaDefinitions are stored here |
PERSISTENTMETADEFS | bool | Store MetaDefinitions in database |