Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

substring_index in Technical Rule

Regular Contributor
Regular Contributor

Hi Team,

I am looking to use substring_index function in technical rule to achieve a requirement. But getting invalid condition error. Idea is to use the value from the substring_index to lookup on a defined dataset.

Is substring_index allowed in technical rule, please share your views.


Saviynt Employee
Saviynt Employee

Hi @Amar_Simha 

Could you please share the query which you are using in Technical rule advance query.

 Technical and User Update rules use the HQL query in Advanced Config. Therefore, you must enter the query in Advanced Config in the HQL format and use the HQL class name instead of the table name. 

Obtaining the attribute details from tables other than the Users table for the Advanced Config query...

Also you can use the supported attributes only. Please refer below for the list of supported attributes.

Creating Technical Rules (

Please check the logs to confirm if the substring_index is supported. 


Dhruv Sharma


@Amar_Simha we have implemented this with below use case :

We have some users with '001#015#1' as cp12. 

We're making a technical which states:

If the users have '001#015#1' as customproperty12, we want to create an account and add access on an endpoint to the entitlement  with '015' as value in customproperty1. 

When we setup the technical rule, we use the SAVCustomQuery in the action object: 

SAVCUSTOMQUERY::ev.customproperty1= substring_index(substring_index('${user.customproperty12}','#',2),'#',-1)

Manish Kumar
If the response answered your query, please Accept As Solution and Kudos

Regular Contributor II
Regular Contributor II

any idea if SAVCUSTOMQUERY works for enterprise roles as well? or is it limited to entitlement_values only? 

As long as object exposed you should be able to use.

Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Ok,thanks. None of the documentation talks about roles in SAVCUSTOMQUERY. So just wanted to see if anyone has done this successfully for roles as well. As I understand entitlements and roles both objects are exposed in rules. 

Hi @shibinvpkvr 

Can you try with SAVCUSTOMQUERY::ev.entitlement_value like 'RoleName%  and see if it works.


Dhruv Sharma