Changes
/* Getting it to the mobile client */
* Since our items have gained a security clearance now, we also have to send it to the client. Add the new meta property to the scope "MCS_DYN_SL_ITEM".
* Of course, we also want to have our department on the client. Also, the department should be a root object, and our test object "InstanceWithDynSL" should be below that department in the content hierarchy on the client. We trust you know how to achieve this!
* The department scope "MCS_DEPARTMENT" should also have the new meta property "MP_REQUIREMENT" as a scoped meta property.
So now, we've created a dependency property telling us why some of our items can be selected and some of them can't.
{{Hint|The dependency object specifying the value influencing the selectable items must be either the target object (the one with the DynSL property), or anywhere above it in the hierarchy.}}
[[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]]
== Goal 5: Add a criterion to connect the dots ==
