Jump to: navigation, search

Difference between revisions of "CONTEXT"


(Created page with "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 it...")
 
Line 1: Line 1:
 +
{{MetaClassInfoBox
 +
| title = Context
 +
| name = CONTEXCT
 +
| internalname = Context
 +
| namespace = System.ACM
 +
| image = [[File:SY_CONTEXT.png|220px]]
 +
| imagecaption = Context
 +
| 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.   
 
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 defined for read access and write access for the same MetaClass.
Line 5: Line 16:
  
 
[[Category:UBIK]]
 
[[Category:UBIK]]
 +
[[Category:UBIK System MetaClasses]]

Revision as of 11:39, 20 June 2013

IC METACLASS.gif Context
Name CONTEXCT
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 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.