Difference between revisions of "SYSCLS DYNAMIC SELECTIVE LIST CRITERION"
(→MetaProperties) |
(→MetaProperties) |
||
| Line 11: | Line 11: | ||
== MetaProperties == | == MetaProperties == | ||
| + | |||
| + | | ||
| + | |||
| + | | ||
| + | |||
| + | | ||
| + | |||
| + | | ||
| | ||
Revision as of 13:54, 30 November 2021
 Selective list item criterion system classification |
|
|---|---|
| Name | SYSCLS_DYNAMIC_SELECTIVE_LIST_CRITERION |
| Inheritance | SYSCLS ROOT |
| Namespace | System.Classification.Lists |
| ID | {413F34A9-762A-42BC-A5F5-BB8A6EE7B160} |
| Purpose | Classify criteria for dynamic selective lists |
| Version | 3.6.1+ |
MetaProperties
| Name | Data type | Comment |
|---|---|---|
| DYNAMIC_SELECTIVE_LIST | Guid | The dynamic selective list this criterion belongs to. |
| IS_MULTI_VALUE_STRING | Boolean | Does the dependency property contain multiple keys separated by ";"? |
| DEPENDENCY_CLASS | Guid | The kind of object do the items depend on - can be null. |
| DEPENDENCY_PROPERTY_NAME | String | The name of the property influencing what items should be available. |
| QUERY_CRITERION_NAME | String | The name of the offline query criterion corresponding to this object. |
| IGNORE_NULL | Boolean | Should null dependency property values be ignored (TRUE) or should only items with null keys be found in case the dependency value is null (FALSE)? |
Usage
The purpose of this classification is to define a criterion for a dynamic selective list for the client. In combination with a Dynamic Selective List Classification implementation, a dynamic selective list can be configured for a scoped meta property.
One dynamic selective list criterion describes how a offline query criterion is used to find dynamic selective items. It connects the dependency value to the offline query criterion of a dynamic selective list.
For example, if you want to have a dynamic selective list presenting a list of cars, you could select the dynamic selective items (cars in this case) by manufacturer. Depending on property value telling you the manufacturer, only matching cars should be listed.
Let's say on every car object, we have a property "manufacturer", by which we could filter the cars conveniently. Then we'd need to configure a query criterion (or just a meta property) on the dynamic selective list searching for cars by this "manufacturer" property.
The dynamic selective list criterion should tell us the name of that query criterion. Now, all we need to do is find out what manufacturer we are talking about. That's where the dependency property comes into play.
The dependency property should contain the value we are filtering for. On the dynamic selective list criterion, you can describe the name of that property. You can also describe the query criterion used to find the items, so the value and the criterion are connected.
The correct object containing the dependency property value is looked up in the ACM hierarchy, so the closest parent (relative to the object where the user should be able to see the dynamic items) with that property will be used and its value will be applied to the offline query when evaluating the dynamic selective list.
It's also possible to configure a lot of additional details, which is implied in the comments of the meta properties table above.
