View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008571CTT UA Scripts1 - Script Issuepublic2023-01-04 17:252023-05-12 15:29
ReporterAlexander Allmendinger Assigned ToArchie Miller  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version1.03.501 
Summary0008571: A and C Exclusive CUs specify an invalid WhereClause
Description

The WhereClause constructed is creating 3 ContentFilterElements with the desire of (a == b) AND (c == d). The script is creating the ContentFilters in the order [0] AND, [1] EQUALS (a,b), [2] EQUALS(c,d). 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 into [0]EQUALS(a,b), [1]EQUALS(c,d), [2]AND(Result[0],Result[1])

This issue has been observed in the following CUs:

  • ExclusiveLimit
  • ExclusiveLevel
  • ExclusiveDeviation
  • ExclusiveRateOfChange
  • NonExclusiveLevel
  • NonExclusiveLimit
  • NonExclusiveDeviation
  • NonExclusiveRateOfChange
TagsNo tags attached.
Files Affected

Relationships

related to 0008581 closedMatthias Damm 10000-004: Services ContentFilter example 1 and example 2 is showing a not allowed filter 

Activities

Archie Miller

2023-01-09 20:03

administrator   ~0018442

I don't see how the existing logic is incorrect. In fact the where statement is ccreated directly out of the example in Table B.1 in Part 4, in which the And Statement is the initial element.

Alexander Allmendinger

2023-01-12 14:54

developer   ~0018462

ContentFilter Examples in the Part 4 are not following the normative part of the specification and have the wrong order of the elements. Mantis issue has been created for Part 4 (see related) to fix the Examples in the informative annex.

Matthias Damm

2023-03-20 04:36

reporter   ~0018901

The examples are right and also the script is right

[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.

Paul Hunkar

2023-05-12 15:29

administrator   ~0019362

agreed in call no change required

Issue History

Date Modified Username Field Change
2023-01-04 17:25 Alexander Allmendinger New Issue
2023-01-04 17:37 Alexander Allmendinger Summary A and C ExclusiveLimit specifies an invalid WhereClause => A and C Exclusive CUs specify an invalid WhereClause
2023-01-04 17:37 Alexander Allmendinger Description Updated
2023-01-09 20:03 Archie Miller Note Added: 0018442
2023-01-12 14:52 Alexander Allmendinger Relationship added related to 0008581
2023-01-12 14:54 Alexander Allmendinger Note Added: 0018462
2023-01-13 18:16 Paul Hunkar Assigned To => Archie Miller
2023-01-13 18:16 Paul Hunkar Status new => assigned
2023-03-20 04:36 Matthias Damm Status assigned => resolved
2023-03-20 04:36 Matthias Damm Resolution open => no change required
2023-03-20 04:36 Matthias Damm Note Added: 0018901
2023-05-12 15:29 Paul Hunkar Status resolved => closed
2023-05-12 15:29 Paul Hunkar Note Added: 0019362