Difference between revisions of "CONTEXT"
| Line 9: | Line 9: | ||
| version = 2+ | | version = 2+ | ||
}} | }} | ||
| − | |||
A defined context defines the usage (use case) of data access. A context knows all its object types ([[MetaClasses]]) and the [[properties]] (columns) that are available in its context. | A defined context defines the usage (use case) of data access. A context knows all its object types ([[MetaClasses]]) and the [[properties]] (columns) that are available in its context. | ||
There might be different contexts scopes defined for read access and write access for the same MetaClass. | There might be different contexts scopes defined for read access and write access for the same MetaClass. | ||
| Line 16: | Line 15: | ||
[[Category:System MetaClasses]] | [[Category:System MetaClasses]] | ||
| + | [[Category:Application Context Management]] | ||
Revision as of 18:56, 11 December 2013
 Context |
|
|---|---|
| Name | CONTEXT |
| Namespace | System.ACM Custom.ACM |
| Internal Name | Context |
| TypeString | {{{typestring}}} |
| RuntimeType | {{{runtimetype}}} |
| Purpose | Configure contexts for ACM |
| Version | 2+ |
A defined context defines the usage (use case) of data access. A context knows all its object types (MetaClasses) and the Properties (columns) 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 for a given ACM are defined by using a Relation (“CONTEXT”). Applications know their related ContextObjects.
