LCS logic errors

Identity Security Cloud (ISC) ISC Discussion and Questions
21

And that’s confirmed on the Account Attribute?

22

Yes sir, I use VS Code primarily for editing transforms since it’s simpler than Postman

23

Can I recommend changing your or operators to || and and operators to &&

24

Confirmed, yes sir. This is one of the Identities that is incorrectly in the terminated LCS.

image
image1839×151 8.71 KB

I have a lookup transform that is taking the employeeStatus and replacing A with Active so I can get a quick and easy picture in the Search menu as well. You can see that they all have Active (A) employeeStatus

image
image922×725 4.1 KB

25

Hi Kannan, I tested this, and unfortunately, it produced the same results

26

When you preview against an Identity in VS Code, do you get no errors, it just returns terminated for those users?

27

@j_place I’m afraid you lost me at

So something like this is what your suggesting?

#elseif($employeeStatus == 'T' and not ($termReason == '555' or $termReason == 'TRO'))terminated
28

Hi Derek. That’s it, yes.

29

PS - I guess youre also going to need requiresPeridicRefresh as true as well

30

Hi @pillar224 - Ok, last thought. Can you check for trailing/leading spaces on the employeeStatus account attribute for your failing users.

32

Thank you for all your attention to this matter. I wrapped the employeeStatus function in a trim transform

"employeeStatus": {
            "attributes": {
                "input": {
                    "type": "accountAttribute",
                    "attributes": {
                        "attributeName": "employeeStatus",
                        "sourceName": "UKG Pro (HR)"
                    }
                }
            },
            "type": "trim"
        },

On top of that I changed the final else if statement as per your recommendation, and unfortunately, those same 27 Identities are still being put in the terminated LCS.

#elseif($employeeStatus == 'T' and not ($termReason == '555' or $termReason == 'TRO'))terminated#end"

I’m going to add a periodicRefresh flag also. That won’t solve this immediate situation (which I know you weren’t suggesting it would) because I been manually processing the changes under the identity profile each time I’ve updated the transform. I’m going to be asking SailPoint in our meeting tomorrow, I’ll let you know how that goes.

Thank you again,

33

So I previewed it just now against one of the identities, and it returned an active LCS. I thought that’s weird, why is it right when I preview it in VS code and not in the tenant. You know what it was? (and yes, I’m mad at myself for not realizing it till now :stuck_out_tongue: ) I had previously manually set their LCS to terminated so I just had to delete their Identity and recreate it… :melting_face: