Difference between revisions of "CONTEXT"
| Line 11: | Line 11: | ||
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 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. |
The contexts for a given [[ACM]] are defined by using a [[relation]] (“CONTEXT”). | The contexts for a given [[ACM]] are defined by using a [[relation]] (“CONTEXT”). | ||
Applications know their related [[ContextObjects]]. | Applications know their related [[ContextObjects]]. | ||
Revision as of 06:43, 26 June 2013
 Context |
|
|---|---|
| Name | CONTEXT |
| Namespace | System.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.
A context aggregates a range of context scopes and serves as configuration object for the hierarchy and object structure published to the mobile application
