Filtering by Supported and Excluded Item Types
Each instance of Webflow connector in UWL administrative UI allows a list of supported and excluded item types to be set. You can enter both supported and excluded item types as a list.
.The following two sections define how filtering is approached regarding the two different scenarios for fetching UWL items from back-end systems.
Assume that you have three sets of item types:
-
Set A comprises the supported item types defined for each connector level.
-
Set B comprises the item types defined for each UWL View using the XML configuration.
-
Set C comprises the item types enumerated in the excluded item types defined for each connector.
Filtering in a Snapshot Scenario by Supported and Excluded Item Types
- Filtering by Supported Item Types
In a snapshot scenario, UWL will fetch the intersection of set A and set B. Only the items belonging to item types defined in both sets are read from the back end and transferred to the UWL internal cache.
Example
User has defined X, Y and Z item types in their connector list of supported item type definitions (set A). User has defined Y and Z item types in their current View XML definition (set B). When the respective view is being loaded, UWL will fetch items belonging to Y and Z item types to the UWL internal cache. This is because Y and Z belong to both set A and set B.- Filtering by List of Excluded Item Types
In a snapshot scenario, UWL will fetch the relative complement of C in the intersection of set A and set B.
(A ∩ B) \ C
In other words, UWL will exclude all items from set C from the item types that are defined in both sets A and B. Then these items will be fetched from the back end and transferred to the UWL internal cache.
Example
User has defined X, Y and Z item types in their connector list of supported item type definitions (set A). User has defined Y and Z item types in their current View XML definition (set B). User has defined Y and W in the list of excluded item types (set C). When the respective view is being loaded, UWL will fetch items belonging to Z item type to the UWL internal cache. This is because Y and Z belong to both set A and set B, and Y is subtracted because of its existence in set C.Filtering in the Delta Pull Scenario by Supported and Excluded Item Types
- Filtering by Supported Item Types
In the Delta Pull scenario, UWL fetches all item types belonging to set A. UWL Delta Pull is a scheduled job running regularly regardless of UWL View definitions. It is not possible to bind item types defined for each view level to Delta Pull jobs.
Example
User has defined X, Y and Z item types in their connector list of supported item type definitions. Regardless of any UWL View definitions when the Delta Pull job for a particular WebFlowConnector is being executed, all belonging to the item types X,Y and Z will be fetched to the UWL internal cache.- Filtering by List of Excluded Item Types
In this scenario, UWL fetches all items that belong to the relative complement of C in A.
UWL excludes all items from set C from the item types defined in set A. Then the Delta pull job fetches all item types belonging to the resulting item type list.