Escape character for Session Relevence

Content Authoring
1

Does anyone know what the escape character is for ; (semicolon)? I know you can use %22 for “” and is there any place that has all the escape characters?

2

These aren’t really “escape” characters, they’re “percent-encoded”. These are just from the ASCII table, in hexadecimal. The ASCII code for doublequote is 34 in decimal or 0x22 in hexadecimal, so %22 = ".

The table is at http://www.asciitable.com/ . Based on this, the character for semicolon (;) should be %3b

1 Like
3

You shouldn’t need to escape ; in session relevance as far as I know, but you could be having issues depending on how you are using the session relevance with HTML.

I’d need to know a bit more how you are using the character and what you are displaying it within and how it is causing issues.

Things can be slightly different if you are using HTML inspectors or not, or if you are using it within WebReports or a Dashboard or Console Debugger or REST API.

4

Here is what I am trying to pass the rest api

https://ROOT:52311/api/query?relevance=(name of item 1 of it, number of elements of intersection of (relevant fixlet set of item 1 of it; item 0 of it) as string ) of (set of source fixlets of components of component groups of bes fixlets whose (baseline flag of it AND name of it = %22WinBaseLine2012R2\NewDeployment%22), members of bes computer group whose (name of it= %22AutoBaseLine%22))

But getting the following

<Query Resource="(name of item 1 of it, number of elements of intersection of (relevant fixlet set of item 1 of it">

<Result/>

<Error>This expression could not be parsed.</Error>
5

This isn’t an issue where you need to escape ; for the sake of Session Relevance, but you need to encode it for the sake of a REST API call, which is not quite the same thing, though it could be that %3b would work.

If you are doing this on the command line, then it could be the command line interpreter that is causing the problem, or it could be that the ; character isn’t being encoded correctly to be included in the URL, causing it to break the query.

6

That worked … Thank you …

1 Like
7

Technically @JasonWalker figured out the escape character. I believe this worked because relevance uses the same escape sequence as URLs, so it was actually converted back to a semicolon before being evaluated, otherwise it wouldn’t have worked.

8

Thank you Jason… That worked…

1 Like
9

Here is a video showing how to put text into Code Blocks on the forum to prevent it from messing up the formatting:

1 Like
10

Sir, you must Pin This!

1 Like