HowTo:Configure Dynamic Selective Lists - Revision history

NWE: /* Known issue workaround: Not ignoring NULL criteria doesn't work */

2022-04-07T14:30:50Z

‎Known issue workaround: Not ignoring NULL criteria doesn't work

NWE: /* Known issue workaround: Not ignoring NULL criteria doesn't work */

2022-04-07T14:30:33Z

‎Known issue workaround: Not ignoring NULL criteria doesn't work

NWE at 14:28, 7 April 2022

2022-04-07T14:28:52Z

NWE: /* Getting it to the mobile client */

2022-01-17T14:55:03Z

‎Getting it to the mobile client

NWE: /* Getting it to the mobile client */

2022-01-17T11:00:35Z

‎Getting it to the mobile client

NWE: /* Getting it to the mobile client */

2022-01-12T13:47:03Z

‎Getting it to the mobile client

NWE: /* Getting it to the mobile client */

2022-01-11T17:03:26Z

‎Getting it to the mobile client

NWE: /* See also */

2022-01-03T17:59:28Z

‎See also

NWE at 17:45, 3 January 2022

2022-01-03T17:45:48Z

NWE: /* Goal 5: Add a criterion to connect the dots */

2022-01-03T12:03:23Z

‎Goal 5: Add a criterion to connect the dots

@@ Line 178: / Line 178: @@
 // do this for both the dependency property as well as the item's criterion property
 var val = base.MY_PROPERTY;
-return val ?? "NULL"; // this is the same as as saying, 'If the value is not null, use it. Else, use whatever I wrote after the "??" operator'
+return val ?? "NULL"; // this is the same as saying, 'If the value is not null, use it. Else, use whatever I wrote after the "??" operator'
 </source>

@@ Line 178: / Line 178: @@
 // do this for both the dependency property as well as the item's criterion property
 var val = base.MY_PROPERTY;
-return val ?? "NULL"; // this is the same as as saying, 'if the value is not null, use it, else, use whatever I wrote after the "??" operator'
+return val ?? "NULL"; // this is the same as as saying, 'If the value is not null, use it. Else, use whatever I wrote after the "??" operator'
 </source>
@@ Line 190: / Line 190: @@
 <!-- DO NOT REMOVE THIS -->{{Template:HowTo/End}}<!-- DO NOT REMOVE THIS -->
 ==See also==

@@ Line 36: / Line 36: @@
 * Add the "DynSL" instance to the infrastructure list of your ACM context.
-[[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 2: Create items for the Dynamic Selective List ==
@@ Line 103: / Line 103: @@
 {{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 ==
@@ Line 140: / Line 140: @@
 {{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 ==
@@ Line 166: / Line 166: @@
 You can configure Dynamic Selective Lists to allow much more complex scenarios. For example, you can remove the restriction for the dependency class on the criterion. You can define the target object as the dependency object, too, so it depends on a different property of itself. You can even specify multiple criteria, potentially with different dependency objects. It is also possible to define multiple properties with dynamic selective lists depending on each other successively.
 <!-- = Studio = -->

@@ Line 96: / Line 96: @@
 * 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!
 So now, we've created a dependency property telling us why some of our items can be selected and some of them can't.
@@ Line 101: / Line 102: @@
 {{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.}}
 == Goal 5: Add a criterion to connect the dots ==

@@ Line 122: / Line 122: @@
 Now that we have documented our security clearance criterion, we just have to tell the client.
 * For this purpose, create a meta class scope "MCS_DYN_SL_CRITERION" for the meta class "MC_DYN_SL_CRITERION".
 * All the meta properties described above should also be added to the scope.
 * Add the scope to the list of all scopes of your ACM context.

@@ Line 29: / Line 29: @@
 === Getting it to the mobile client ===
 Next, we want to make sure the mobile client receives your DynSL.
-* Create a new [[QUERYSCOPE|query scope]] for the DynSL. Let's call it "QCS_DYN_SL" for example.
+* Create a new [[QUERYSCOPE|query scope]] instance for the DynSL. Let's call it "QCS_DYN_SL" for example.
-* Assign the DynSL instance to the new query scope.
+* Assign the DynSL instance to the new query scope by dragging the DynSL instance onto the "QUERY" field of the scope instance.
 * Add the [[SYSCLS_OFFLINE_QUERY|Offline Query Classification]] to the scope.
 * Add the [[SYSCLS_DYNAMIC_SELECTIVE_LIST|Dynamic Selective List Classification]] to your scope as well.
 * Add the "QCS_DYN_SL" to the scope list of your ACM [[CONTEXT|context]].
 * Add the "DynSL" instance to the infrastructure list of your ACM context.
 == Goal 2: Create items for the Dynamic Selective List ==

@@ Line 171: / Line 171: @@
 * [[HowTo:Configure_the_ACM]]
 * [[HowTo:Make_an_Object_appear_on_the_Mobile_Client]]
 [[Category:Client|Configure Dynamic Selective Lists]]

← Older revision		Revision as of 12:03, 3 January 2022
Line 125:		Line 125:

	{{Hint\|A criterion property (like "MP_SECURITY_CLEARANCE" in our example) on the Dynamic Selective Items also has to appear on the Dynamic Selective List scope, because technically, an offline query is used in the background. It's recommended to read the details about [[Offline_Query_(UBIK_WinX)\|Offline Queries]] to understand this.}}		{{Hint\|A criterion property (like "MP_SECURITY_CLEARANCE" in our example) on the Dynamic Selective Items also has to appear on the Dynamic Selective List scope, because technically, an offline query is used in the background. It's recommended to read the details about [[Offline_Query_(UBIK_WinX)\|Offline Queries]] to understand this.}}
		+
		+	{{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 ==		== Releasing the ACM meta definitions ==