Difference between revisions of "METACLASSSCOPE"
| (3 intermediate revisions by 2 users not shown) | |||
| 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]] | ||
| Line 14: | Line 14: | ||
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. | 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. | ||
| − | + | If an object is published to the client the {{Web Service}} tries to load the most accurate MetaClassScope corresponding to the object's MetaClass. If no MetaClass scope for exactely that MetaClass can be located the system looks up the inheritance hierarchy (regarding the data model) if it can find a suitable one. | |
== Own Properties == | == Own Properties == | ||
| Line 22: | Line 22: | ||
|- | |- | ||
| METACLASS || Guid || no || Reference to the according MetaClass | | METACLASS || Guid || no || Reference to the according MetaClass | ||
| + | |- | ||
| + | | DELETE_CONFIG|| Integer || no || Possibility to configure the delete behavior when a instance of the defined MetaClass gets deleted via the ACM (Web Service) | ||
|} | |} | ||
| + | |||
== Classifications == | == Classifications == | ||
| Line 29: | Line 32: | ||
== Icons == | == 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. | 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. | ||
| + | |||
| + | == Delete Configuration == | ||
| + | The Delete Configuration gives the possibility to configure whether an instance of the configured MetaClass may be deleted via ACM. | ||
| + | |||
| + | {| class="wikitable" width=50% | ||
| + | |- | ||
| + | ! width=30% | Setting !! width=70% | Description | ||
| + | |- | ||
| + | | NotDeleteable || Deletion of an instance of the configured MetaClass via the WebService is not supported | ||
| + | |- | ||
| + | | RemoveFromOwner || Deletion of an instance is possible via the WebService. The instance will be removed from its owner (the relation/reference will be deleted) but the instance itself will not be deleted from the database. | ||
| + | |- | ||
| + | | Deleteable || Deletion of an instance of the configured MetaClass via the WebService is not supported and the deleted object will get totally be removed from Ubik (will get deleted in the database). | ||
| + | |} | ||
| + | |||
== See also == | == See also == | ||
* [[HowTo:Assign an Icon to a MetaClass]] | * [[HowTo:Assign an Icon to a MetaClass]] | ||
| − | [[Category:Context scope]] | + | [[Category:Context scope|METACLASSSCOPE]] |
| − | [[Category:Metaclasses]] | + | [[Category:Metaclasses|METACLASSSCOPE]] |
Latest revision as of 12:17, 29 September 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.
If an object is published to the client the Web Service tries to load the most accurate MetaClassScope corresponding to the object's MetaClass. If no MetaClass scope for exactely that MetaClass can be located the system looks up the inheritance hierarchy (regarding the data model) if it can find a suitable one.
Own Properties
| Name | Data type | Optional | Comment |
|---|---|---|---|
| METACLASS | Guid | no | Reference to the according MetaClass |
| DELETE_CONFIG | Integer | no | Possibility to configure the delete behavior when a instance of the defined MetaClass gets deleted via the ACM (Web Service) |
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.
Delete Configuration
The Delete Configuration gives the possibility to configure whether an instance of the configured MetaClass may be deleted via ACM.
| Setting | Description |
|---|---|
| NotDeleteable | Deletion of an instance of the configured MetaClass via the WebService is not supported |
| RemoveFromOwner | Deletion of an instance is possible via the WebService. The instance will be removed from its owner (the relation/reference will be deleted) but the instance itself will not be deleted from the database. |
| Deleteable | Deletion of an instance of the configured MetaClass via the WebService is not supported and the deleted object will get totally be removed from Ubik (will get deleted in the database). |
