Under Review

Client Tools Should Enable Search for Condition Values

The client tools should include a way to search for existing condition values when managing or selecting conditions. 

Currently, users must manually browse a list of conditions in order to find the condition value they need, which is inefficient.

Amy S
Parents

  • Hi Amy, I got this information from Kurt Van Deun a while back. I assume this logic would work also in conditions, at least you can try.

    The search looks inside the content and the XML structure by default.  The details of the operators can be found online in:

    https://docs.rws.com/992513/75872/tridion-docs-14-sp4/search-for-content

     Examples from searches in our content:

    When you use a query like this:

    “<body>”            you get hits on the XML element <body> and occurrences in the content

     

    So looking for:

    “<properties>”  results in 51 hits

    properties           results in 30 hits (just the term properties that occurs in the text)

     

    to find only the real element <properties>, you need to create a query like the one below with and AND and NOT operator which results in 21 hits:

     

    "<properties>" AND !properties

     

    Linking it to your specific elements:

                   “<section>” AND !section            2 hits (in RWS publishing error message templates)

                   “<data>” AND !data                      0 hits

Comment

  • Hi Amy, I got this information from Kurt Van Deun a while back. I assume this logic would work also in conditions, at least you can try.

    The search looks inside the content and the XML structure by default.  The details of the operators can be found online in:

    https://docs.rws.com/992513/75872/tridion-docs-14-sp4/search-for-content

     Examples from searches in our content:

    When you use a query like this:

    “<body>”            you get hits on the XML element <body> and occurrences in the content

     

    So looking for:

    “<properties>”  results in 51 hits

    properties           results in 30 hits (just the term properties that occurs in the text)

     

    to find only the real element <properties>, you need to create a query like the one below with and AND and NOT operator which results in 21 hits:

     

    "<properties>" AND !properties

     

    Linking it to your specific elements:

                   “<section>” AND !section            2 hits (in RWS publishing error message templates)

                   “<data>” AND !data                      0 hits

Children
No Data