`visible flag` problem with Session Relevance feedback - REST API

Content Authoring
1

I have been vexed trying to debug some session relevance that seems to work perfectly in the console debugger but not through the REST API and it was driving me crazy. I tried a million different things before I figured out the problem.

This session relevance will work ONLY in the console debugger, but NOT with the REST API:

number of bes fixlets whose(visible flag of it)

This will always return 0 in session relevance when used with the REST API. It will generally return a pretty big number through the console. I’m fairly confident that this is because the REST API lacks the console context that would allow it to know which fixlets are locally hidden by the current operator in the console.

The real problem here is that it should instead return an error message about the context problem, or it should just work, even if it actually returned more results than expected, it would at least be something.

This isn’t the only problem, it actually gets weirder:

First, you should know that globally visible flag of it works the same way for both the REST API session relevance and the console debugger session relevance. This is actually the relevance I meant to use but I mistakenly used the above which confounded me.

The even weirder part is that number of bes fixlets whose(NOT visible flag of it) actually returns 2 different values depending on if you are using the REST API session relevance or the Console debugger session relevance.

Because visible flag of it didn’t work at all with the REST API, I expected NOT visible flag of it to have the exact same problem. Instead what happens is that NOT visible flag of it and NOT globally visible flag of it are identical when used through the REST API, but not when used through the console debugger session relevance. When you use NOT visible flag of it through the console, it actually gives you the results for all locally hidden content, but it does not include the count of the content that is globally hidden. If you use NOT globally visible flag of it in the console, it always returns 0, which, in a way, is the opposite of the REST API.

CC: @AlanM

1 Like
2

I am having the same exact issue and have not been able to figure it out either.

We are running 9.5.1

The relevance works fine in the presentation debugger. The REST API returns an empty result and the error “Singular expression refers to nonexistent object.”

The query that I am running is:

(id of it, name of it | “”, name of site of it | “”, globally visible flag of it, source of it | “”, source id of it | “”, source severity of it | “”, category of it | “”, exists default action of it, type of it | “”, download size of it | 0, source release date of it as string | “” as string, content id of default action of it | “”, visible flag of it) of relevant fixlets whose(globally visible flag of it = True AND name of it as lowercase does not contain “superseded”) of bes computers whose (id of it = 1755142)

If I remove “, visible flag of it” from the query then it works fine in the rest API. It always works fine in the presentation debugger.