Client relevance of action

got it…

q: rows of statement ("WITH CTE AS ( SELECT A.IssuedTime as 'IssuedTime' , CASE WHEN INSTR(A.[ActionName], '- retry') " & "= 0 THEN A.[ActionName] ELSE SUBSTR(A.[ActionName], 0, INSTR([ActionName], '- retry')) END AS 'SoftwareName', SUBSTR(B.State, INSTR(B.State, ':s=') + 3, INSTR(B.State, ':pr=')-INSTR(B.State, ':s=')-3) as 'Status' , REPLACE(SUBSTR(B.State, INSTR(B.State, ':relevant=') + 10), ':', '') 'Relevant' FROM ACTION_HISTORY A INNER JOIN ACTION_STATE_HISTORY B ON A.ActionID = B.ActionID WHERE A.IssuerName = 'ede_rest_admin' AND (A.ActionName LIKE '%25\_I%25' ESCAPE '\' OR A.ActionName LIKE '%25\_U%25' ESCAPE '\') " & "AND A.Script = '' ) SELECT MAX(A.IssuedTime) 'IssuedTime' , A.SoftwareName 'SoftwareName' FROM CTE A INNER JOIN (SELECT SoftwareName FROM CTE GROUP BY SoftwareName HAVING COUNT(1) > 1) B ON A.SoftwareName = B.SoftwareName GROUP BY A.SoftwareName") of sqlite database of file "ActionHistory.db" of folder "__Global" of data folder of client

@cmcannady said he ran across patch content that was failing because of this same issue.

Historically, we used to use ‘rope’ for such cases to keep things efficient: https://developer.bigfix.com/relevance/reference/string.html#rope-string-rope

Though I’m not sure if it still applies.

Example:

Q: length of (rope ("Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test " & "Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test " & "Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test Test "))
A: 1230

cc: @AlanM

However, the only thing you can do with a rope is get its length or convert it back to a string :slight_smile:

So if you need to pass it to something like rows of statement <string> you’ll have to keep it as a string

Greetings all. The associated PMR that @masonje referred to is #66551,082,000

This PMR was opened because of SLES 11 patch content from the BigFix sync site that’s failing. When I dug into the issue I was able to identify that the BESClient QNA was truncating one of the fixlet’s relevance statements. This has been confirmed by Dave Langridge on 12/27.