Workflow - Do the value field of 'Verify Data Type' operator And access to manage field of 'Manage Access' action support variables?

[nhassan (Noor Hassan)]

Hi All,

I’ve setup a workflow using the following steps as shown in the attached screenshots.

1: Identity attributes changed (trigger)
2: Define Variable (this is ‘Text’ data field for application name e.g Akamai)
3: Get Access (get all entitlements of the triggerd identity)
4: Verify Data Type

• Without using step2 i.e define variable, I know this value works fine e.g $.getAccess.accessItems[?(@.type == “ENTITLEMENT” && @.name =~ /Akamai.*/i)]
• But if I use step2 i.e define variable, this value doesn’t seem to be working e.g $.getAccess.accessItems[?(@.type == “ENTITLEMENT” && @.name =~ /$.defineVariable.*/i)]

5: Manage Access (remove access where entitlement name start with Akamai)

• Access to Manage
  • Without using step2 i.e define variable, I know this value works fine e.g $.getAccess.accessItems[?(@.type == “ENTITLEMENT” && @.name =~ /Akamai.*/i)]
  • But if I use step2 i.e define variable, this value doesn’t seem to be working e.g $.getAccess.accessItems[?(@.type == “ENTITLEMENT” && @.name =~ /$.defineVariable.*/i)]

The reason I want to use define variable is, so we can easily replicate the same workflow for another application by just changing the define variable step accordingly instead of changing the value field of verify data type operator and access to manage field.

So, do the value field of ‘Verify Data Type’ operator And access to manage field of ‘Manage Access’ action support variables?

Thanks!

[Bassem_Mohamed]

Hi @nhassan, I was testing this during the last couple of days but it seems that the operator “=~” accepts a regular expression and it’s hard to define a variable name in that regular expression. I believe you need to use this json filter: $.getAccess.accessItems[?(@.type == “ENTITLEMENT” && @.name =~ /Akamai.*/i)]
Thanks

[nhassan (Noor Hassan)]

Hi @Bassem_Mohamed

Thanks for confirming this.

So, it means we can’t use variable in the value field as this operator “=~” accepts a regular expression.

I will update the json filter accordingly for each application workflow.

Thanks