DT3 version 3.9.8 pro-edition
rules BEFORE safed:
rules AFTER safed:
This means it is never possible to create nested rules.
Am I doing something wrong or is this a special feature ?
DT3 version 3.9.8 pro-edition
rules BEFORE safed:
rules AFTER safed:
This means it is never possible to create nested rules.
Am I doing something wrong or is this a special feature ?
Why are you trying to create sub-sub-sub-sub-criteria like this?
Not all criteria are predicates of others.
because I must collect different documents out of different groups which are different tagged (which is intended for logical reason).
The order of the Any/All conditions at the same level actually doesnât matter and therefore the conditions on both screenshots are technically identical. What exactly do you want to achieve but doesnât work as expected?
> IF tag = 2024 AND
> (IF (group = Gas) AND
> tag = Rechnung AND
> tag = Q? ). <-- any other criterum
> OR
> (IF (group = NK_2024) AND
> tag = Rechnung AND
> tag = NK_Abrechnung AND
> tag = Heizung)
>
> THEN ...
sorry, didnât work:
Group = Gas and NK_2024 exists.
in Group Gas: several documents with tags â2024â + âRechnungâ existis (in subfolder of Gas)
in Group NK_2024: serveral images with tags â2024â + âHeizungâ exists.
Whatâs wrong ?
Function âMatchesâ â âenthältâ (in German). Script in this case never find an matching group name !
Only âequalâ â âistâ works.
The smart ruleâs conditions match items that have both the desired name and tags. But according to your description only groups match the name whereas documents match the tags and therefore no item matches all conditions.
One possibility might be to disable the exclusion of groups from tagging (see File > Database Properties). Afterwards you could replace e,g. Name is Gas with a Tag is Gas condition to find the documents having the desired tags in the group Gas
tagging groups is not my favorite.
But I found a solution for myself by deleting the group comparison and partially adjusting the tags of the individual documents.
I think itâs a good idear to think about expanding DTâs command set to include âorâ conditions and to correct the not working âmatchâ at least in German.
The Any setting is actually OR. What exactly does not work when using matches?
checked it again: the problem with âmatchesâ came from the (combination of the) queries, not from the keyword. Solved.