Changes
/* Getting it to the mobile client */
* Add the scope to the list of all scopes of your ACM context.
* Add the criterion instance ("SecurityClearanceCriterion") to the list of infrastructure objects.
* The new criterion must also be reflected on the dynamic selective list scope, because we need it for the offline query aspect of this feature: Add the meta property "MP_SECURITY_CLEARANCE" to the DynSL scope "QCS_DYN_SL". The reason for this is, that the DynSL is an offline query and requires a property to contain the criterion value. This value is resolved using the DynSL criterion.
{{Hint|Multiple criteria with different dependencies are supported. It is also possible to omit the dependency class restriction, so the closest object with the dependency property (ignoring the meta class) is used as dependency.}}
{{Hint|Dependency objects are looked up in the parent hierarchy of the object with the DynSL property. The closest "ancestor" with the correct class and a matching property is chosen as dependency object (and its matching property as dependency property). If an object has multiple parents, there can be multiple closest matching dependency objects - this can lead to a larger amount of selectable items, because the results for all dependency objects are accumulated. }}
[[Category:Client|Configure Dynamic Selective Lists]][[Category:How-To|Configure Dynamic Selective Lists]][[Category:Studio|Configure Dynamic Selective Lists]][[Category:Web service|Configure Dynamic Selective Lists]]
== Releasing the ACM meta definitions ==
