Jump to: navigation, search

Difference between revisions of "CONTEXT"


Line 16: Line 16:
 
{| class="wikitable" width=50%
 
{| class="wikitable" width=50%
 
|-
 
|-
! width=30% | Name !! width=30% | Data type !! Comment
+
! width=30% | Name !! width=20% | Data type !! width=10% | Optional !! Comment
 
|-
 
|-
| VIEW|| Guid || Reference to a view defining the objects' hierarchy
+
| VIEW|| Guid || no || 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
+
| DATETIMEFORMAT  || String || yes || 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
+
| METADEFINITION || XML|| yes || Released [[MetaDefinitions]] are stored here
 
|-
 
|-
| PERSISTENTMETADEFS || bool || Store MetaDefinitions in database
+
| PERSISTENTMETADEFS || bool || yes || Store MetaDefinitions in database
 
|}
 
|}
  
 
[[Category:System MetaClasses]]
 
[[Category:System MetaClasses]]
 
[[Category:Application Context Management]]
 
[[Category:Application Context Management]]

Revision as of 13:25, 16 December 2013

IC METACLASS.gif Context
Name CONTEXT
Namespace System.ACM
Custom.ACM
Internal Name Context
TypeString {{{typestring}}}
RuntimeType {{{runtimetype}}}
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.

Specific Properties

Name Data type Optional Comment
VIEW Guid no Reference to a view defining the objects' hierarchy
DATETIMEFORMAT String yes Configure a user specific date / time format to be used for visualizing date / time values on the client
METADEFINITION XML yes Released MetaDefinitions are stored here
PERSISTENTMETADEFS bool yes Store MetaDefinitions in database