Changes
/* Goal 4: Define a dependency property */
In any case, we require somebody to blame for this decision. After all, "Hugo" could feel left out and send a complaint to management, so we better have a scapegoat.
The goal of this section is to create something so we can justify why "Denise" and "Bob" can be possible values, but "Hugo" isn't. Also, for the DynSL to work, the mobile client requires this information as well.
Our line of argumentation will be: the department has a specific requirement for items to be selectable, so the department rules are the reason only "Denise" and "Bob" are qualified.
{{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 ==
