Obtaining the Count numerical value from HTTP request header

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi Experts,

I have a workflow where I am retrieving access items from a certification based on reviewer using the ISC API, the results are limited to 100 at a time in order for a subsequent loop workflow to work successfully.

The HTTP request gets created as a JSON object that looks something like this:

{
  "hTTPRequest": {
    "body": [
      xxxxxxx
    ],
    "headers": {
      "X-Total-Count": [
        "643"
      ]
    },
    "responseTime": "0.881353 seconds",
    "statusCode": 200
  }
}

I am retrieving the count value from the headers using the json path expression

$.hTTPRequest.headers.X-Total-Count[0]

This returns the value “643” but as a string. Is there anyway to convert this to a number with define variable in ISC workflows?

I want to do a compare numbers to see if this number is greater than 100 and if so make another HTTP request to retrieve the next 100 items to pass to the loop workflow.

2

Hi Irshaad!
I don’t think that this can be solved with OOTB workflow tools at the moment.
A workaround would be to make a HTTP request to this public math api and do the comparison there: https://api.mathjs.org/

I hope this helps :slight_smile:

1 Like
3

Hi @Irshaad_Laher_WS,

You may try with String Compare operator in workflows to achieve this case, Find below screenshot for your reference.

image
image938Ă—529 29.2 KB

OutPut:

image
image1271Ă—393 28 KB

Find below link for more deatils: Operators - SailPoint Identity Services

2 Likes
4

Hey Oliver!

Thanks, will check this out!

1 Like
5

Hi @gogubapu

Thanks so much, will give this a go!

1 Like
6

I would be careful with using string comparison to compare numbers. String comparison compares each character from left to right as opposed to the actual value. So the string “100” will be less than the string “9”.

4 Likes
7

Thanks @colin_mckibben, I ended up with a different approach which isn’t ideal but don’t seem to have another option right now. I limit a 100 at a time on each HTTP request and before proceeding to pass it to the next workflow to loop through the results I check if there are any results returned with a compare boolean to see if the result is null.

The problem with this is I have to predefine how many time the workflow will actually attempt to check for the next 100 set of results as I can’t do a number compare against the count.

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.