To use Vlookup table in workflows

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

Hi ,

Can anyone suggest how to use Vlookup table transform in Workflow. As per my requirement i have to check key and get value in workflow based upon dynamic input.

is there any possiblity to gey key , value pairs and use in the workflow/.

appreciate your assistance.

Thank you,
Yagnasri

2

Hi @guttays,

Could you please provide more context regarding this requirement?

3

Hi @sidharth_tarlapally ,

Requirement i am checking is similar get
Usecase1: entitlement/role value based on the Location value . We have key and value pairs for this scenario so planning to use Lookup transform and delimited source[ Delimited source is like new key-value pairs will be added according to business requirement].

Can you please suggest how to use this as any

4

Hello @guttays

No it is not possible to use in the define variable step a lookup transform.

Regards,
Pablo

5

@guttays

Got it.

While we can’t use transforms directly within workflows, here’s an approach that could help achieve your use case:

HTTP Action
Use an HTTP request to fetch accounts from the source where the accountId is mapped to the location (assuming you’ve mapped location as the account ID in the source).

Make the below API call in the Action

{{baseUrl}}/accounts?filters=sourceId eq "source ID of the delimited file" and nativeIdentity eq "location"

This will return the account attributes (such as entitlement/role values) associated with the matched location, which you can then use in the subsequent steps of the workflow.] Sample response of above API call will look like :

[
    {
       
        "sourceId": "03cd8cd795694d81b9ef257343771dd9",
        "sourceName": "Location-Role Mapped Source",
        "identityId": "9078692f7ee84120a4c42c6487077145",
        "attributes": {
            "location":"india",
          "roles":["testrole1","testrole2"]
        },
        "modified": "2025-04-17T10:50:11.030Z"
    }
]

to use the roles attribute value you can use $.hTTPRequest.body[0].attributes.roles

Hope this helps !

Thanks
Sid

6

Thank you @sidharth_tarlapally it’s working. Appreciate your quick suggestion.

One more Suggestion regarding the Data Segmentation. I have created Segment and added users & entitlements to it , published the Segment. But still i can see all other users are able to see the entitlements even i restricted from Data segmentation. any Idea?

7

@guttays

What is the user level of the Identities that you tried to test the visibility with ?

8

We verified with Admin users and non-Admin users also @sidharth_tarlapally but that is visible to all users.

9

make sure the segment is published and enabled

10

++

Enabling Data Segmentation

Identity Security Cloud org admins can use the system features UI to enable or disable data segmentation for your implementation. This feature is disabled by default, meaning that users’ access to records is always global.

  1. Go to Admin > Global > System Settings.
  2. Select System Features from the left navigation.
  3. Select the Data Segmentation checkbox.
  4. Select Save.

When data segmentation is disabled, you are still able to use the UI and edit segments. However, even published and enabled segments do not affect user access unless the data segmentation feature is enabled in the system settings.

When data segmentation is enabled, it controls users’ record level access. Any records that were previously restricted on a given source by a sub-administrator user level, such as role sub-admin and source sub-admin, are no longer restricted.