Using variables in relevance for property

I have a long relevance for creating a property. Actual the relevance looks in a csv (better a crlf) file using
"line 11 of file"… as statement. This is used several times in the whole relevance.

As the file syntax has changed to lines containg a key:value format I have to change relevance as well.

Using
"following text of first “=” of lines whose (it starts with “<KEY”) of file “” works pretty fine.

Question now: is it possible to assign the output of above statement to a variable instead of having the same statement several times in relevance ?

Hope I was able to point it out clear enough :thinking:

If you are creating a BigFix property in a BigFix analysis you cannot use variables.

If you are running an action that does something to create the data you are reading with a property, you can use variables.

1 Like

Thanks for your fast reply which confirmes my assumption. Hope IBM will improve in the future.

To be fair, how many times can you possibly reference the same statement in a single analysis? If it’s more than 2, I generally just copy the relevance into a word processing program or the fixlet debugger and use text replace functions to update complex relevances.

If you’re always replacing like for like, this approach should work just fine. While I agree that parameters might be useful for extremely long relevance statements, you might want to avoid those kinds of statements in analyses as the time the client needs to evaluate such statements could be detrimental to the performance of the agent.

I had about 4 different statements applying 2-4 times in relevance. Of course, editing with notepad++ was done pretty fast.

Just for better overview which information from file is used it would be fine to have it in the head of relevance.