Difference between revisions of "METACLASSSCOPE"
| Line 3: | Line 3: | ||
| title = MetaClass Scope | | title = MetaClass Scope | ||
| name = METACLASSSCOPE | | name = METACLASSSCOPE | ||
| − | | internalname = | + | | internalname = SystemObjects.{{PAGENAME}} |
| namespace = System.ACM.Scopes | | namespace = System.ACM.Scopes | ||
| image = [[File:SY_METACLASSSCOPE.png|220px]] | | image = [[File:SY_METACLASSSCOPE.png|220px]] | ||
Revision as of 11:26, 23 March 2015
 MetaClass Scope |
|
|---|---|
| Name | METACLASSSCOPE |
| Namespace | System.ACM.Scopes |
| Internal Name | SystemObjects.METACLASSSCOPE |
| TypeString | UBIK.Kernel.MetaClass |
| RuntimeType | UBIK.Content.ACM.MetaClassScope |
| Purpose | Configure context scopes for MetaClasses |
| Version | 2.1.13+ |
A MetaClassScope specifies the published meta data (MetaClass and MetaProperties) which should be accessible on the mobile device. Further, it is possible to configure the permissions granted on those objects on the mobile.
The system tries to load the most accurate MetaClassScope object, where the MetaClass of the current object serves as filter criterion. If the system can not directly locate a proper MetaClassScope it searches up the inheritance hierarchy to find the most suitable.
Own Properties
| Name | Data type | Optional | Comment |
|---|---|---|---|
| METACLASS | Guid | no | Reference to the according MetaClass |
Classifications
If a MetaClass implements a certain classification the MetaClassScope must publish all required MetaProperties as declared by the classification. Only then the classification is known on the mobile client.
Icons
For deploying MetaClass specific icons it is necessary to create an own MetaClassScope for each MetaClass. Otherwise, the system will always deliver the icon of the most suitable MetaClassScope fitting a parent's MetaClass.
