METACLASSSCOPE
 MetaClass Scope |
|
|---|---|
| Name | METACLASSSCOPE |
| Namespace | System.ACM.Scopes Custom.ACM.Scopes |
| Internal Name | MetaClassScope |
| TypeString | {{{typestring}}} |
| RuntimeType | {{{runtimetype}}} |
| 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.
Contents
Configuration
MetaClassScope
The Metaclass property of an instance references to the according MetaClass (see Create a new MetaClassScope).
MetaProperties on Relational Object
| Name | Data type | Comment |
|---|---|---|
| Initial value | Any | configure specific initial values |
| Priority | Integer | set a priority value, e.g. used in combination with the Measurement Task Classification |
| Write enabled | Boolean | property value can be changed by the mobile user |
| Visibility | Integer | set the visibility of the property |
| Sort order | Integer | set how the property should be sorted |
Priority
| Value | Comment |
|---|---|
| >120 | Property is shown in the pop-up dialog if the object is classified as SYSCLS TASK |
Visibility
| Value | Comment |
|---|---|
| Visible | Property will always be shown on the mobile device |
| Hidden | Property will only be shown on the mobile device if ShowSystemProperties is set to true |
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.
