View Issue Details

IDProjectCategoryView StatusLast Update
000858110000-004: ServicesSpecpublic2023-03-22 18:11
ReporterAlexander Allmendinger Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version1.05.02 
Fixed in Version1.05.03 RC1 
Summary0008581: ContentFilter example 1 and example 2 is showing a not allowed filter
Description

Example 1:
The WhereClause in the Example 1 - Table B.1 - ContentFilter example is creating 5 ContentFilterElements. The ContentFilter is creating the ContentFilters in the order
[0] AND ([1],[4])
[1] Or ([2],[3])
[2] EQUALS(a,b)
[3] InLIst (c,d,e)
[4] Like (f,g)
But according to specification Part 4 "An index is considered valid if its value is greater than the element index it is part of ..." which results in the created WhereClause being invalid.
The order needs to be changed e.g. into:
[0] Like (f,g)
[1] EQUALS(a,b)
[2] InLIst (c,d,e)
[3] Or ([1],[2])
[4] AND ([3],[0])
Note: Elements 0,1,2 could also be ordered differently ...
Example 2:
Similar in Table B.2 - ContentFilter example where the order needs to be changed as well. A valid order would be:
[0] OfType (a,b)
[1] InView (c)
[2] InView (d)
[3] Or ([1],[2])
[4] AND ([3],[0])
Note: Elements 0,1,2 could also be ordered differently ...

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008571 closedArchie Miller CTT UA Scripts A and C Exclusive CUs specify an invalid WhereClause 

Activities

Paul Hunkar

2023-01-13 18:18

developer   ~0018492

example 3 also has the same problem - probably should review all examples

Matthias Damm

2023-03-20 04:34

developer   ~0018900

The example is right and complies with the definition "An index is considered valid if its value is greater than the element index it is part of ..."

[0] AND ([1],[4])
[1] Or ([2],[3])
[2] EQUALS(a,b)
[3] InLIst (c,d,e)
[4] Like (f,g)

In example, AND has two ElementOperands with index=1 and index=4
Both are part of element index 0.

Therefore both values (1, 4) are greater than 0.

This is how all applications that I know implement the filter and this is the only way they can work.

Jim Luth

2023-03-22 18:11

administrator   ~0018975

Agreed to no fix in Dallas meeting. Alex will double check and reopen if necessary.

Issue History

Date Modified Username Field Change
2023-01-12 14:52 Alexander Allmendinger New Issue
2023-01-12 14:52 Alexander Allmendinger Relationship added related to 0008571
2023-01-13 18:18 Paul Hunkar Note Added: 0018492
2023-03-20 04:34 Matthias Damm Assigned To => Matthias Damm
2023-03-20 04:34 Matthias Damm Status new => resolved
2023-03-20 04:34 Matthias Damm Resolution open => no change required
2023-03-20 04:34 Matthias Damm Fixed in Version => 1.05.03 RC1
2023-03-20 04:34 Matthias Damm Note Added: 0018900
2023-03-22 18:11 Jim Luth Status resolved => closed
2023-03-22 18:11 Jim Luth Note Added: 0018975