Difference between revisions of "IDMARKERSCANQUERY"
(→See also) |
|||
| Line 25: | Line 25: | ||
== See also == | == See also == | ||
| − | * [[ | + | * [[QUERY]] |
| − | * [[ | + | * [[QUERYITEM]] |
[[Category:Metaclasses]] | [[Category:Metaclasses]] | ||
Revision as of 13:50, 23 March 2015
 IdMarkerScanQuery |
|
|---|---|
| Name | IDMARKERSCANQUERY |
| Namespace | System.IdMarkerScanQuery |
| Internal Name | SystemObjects.IDMARKERSCANQUERY |
| TypeString | UBIK.Kernel.MetaClass |
| RuntimeType | UBIK.Kernel.IdMarkerScanQuery |
| Purpose | Configure queries for objects with id markers |
| Version | 2.2.3+ |
Contents
Basics
Id marker scan queries are used for fetching a list of ContentClasses identified by different scan codes (ID Marker, Barcode, QR Code) from the database. All of these objects have to implement the classification SYSCLS OBJECTWITHIDMARKER in order to be found as the query result. The id marker scan query itself inherits functionality from Query, implements the classification interface SYSCLS IDMARKERSCANQUERY and can be used in different scenarios to identify objects by scan codes:
- data fetching (n records)
- finding a single or a set of recordset(s)
- used as definition of root nodes in a View
FilterClass
The FilterClass is a reference to the root node where all the matching content is beeing compared with the query criteria. The root node itself does not need to fullfill the classification SYSCLS OBJECTWITHIDMARKER as all derived MetaClasses are recursively checked for implementing the classification interface. All the matching content then is aggregated to one query result.
 | When selecting the query root node, please consider that possibly a huge amount of derived MetaClasses must be recusively checked for implementing the classification interface! Using a FilterClass that directly implements the interface reduces the processing time to a minimum! |
Filter Criteria
The filter criteria of an IdMarkerScanQuery basically consists of an ID Marker, a Barcode or a QR Code. If these code search criteria are logically combined with AND if provided together (e.g. QR Code AND Barcode). On the other hand providing only one of these scan code values, the content is matched to the specified code type (e.g. Barcode) only.
