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

Multiple condition not working in User Update Rule

Saviynt_Savvy
Regular Contributor
Regular Contributor

Hi All,

I am using 3 different attributes in the User Update Rule where by updating any one of the attributes should trigger a Technical rule which further triggers "Add Account" and "Add Access" Tasks.

When I update any of the User attributes, I don't see the User Update Rule/Technical Rule get triggered in the "User Update History" and I see no Pending tasks generated.

User Update Rule:

Trigger Actions When: Trigger when User is updated from UI.

Saviynt_Savvy_0-1714724755552.png

Technical Rule:

Saviynt_Savvy_1-1714724926571.png

But If I use any one of any of the 3 attributes in the User Update Rule, then I see the User Update Rule and Technical Rule getting triggered in the User Update History and generating the pending tasks.

User Update Rule (with only one attribute in Condition)

Saviynt_Savvy_2-1714725179418.png

I am using the version 24.2. Also able to trigger the User Update rules through the 'Advanced Config'.
Please suggest whether the User Update rule and Parenthesis were correctly mentioned or required to make any settings or changes in the Global Configuration.

Thanks & Regards,
SaviyntSavvy

7 REPLIES 7

Raghu
Valued Contributor III
Valued Contributor III

@Saviynt_Savvy  use below and modiy check braces 

Raghu_0-1714728174021.png

 

 


Thanks,
Raghu
If this reply answered your question, Please Accept As Solution and hit Kudos.

PremMahadikar
Valued Contributor
Valued Contributor

Hi @Saviynt_Savvy ,

In case the above solution isn't working. Please share the logs.

Also try the below code in Advanced Config

(a.email like '%freshservice%' and (##a.email isupdated##)) or (a.departmentname='MNG' and (##a.departmentname isupdated##)) or (a.title='Manager' and (##a.title isupdated##))

 

If you find the above response useful, Kindly Mark it as Accept As Solution and hit Kudos

Hi @PremMahadikar ,
As I mentioned in the post, I'm able to trigger the rules through advanced configuration, but not through normal configuration.
Any suggestion why the normal configuration is not working.

Thanks & Regards,
SaviyntSavvy

@Saviynt_Savvy ,

I replicated the same (24.1v). The rule is getting picked up in the logs, but errored out!

The issue is not with double or single braces! 

This is bug! Please raise a Freshdesk ticket on the original request. 

With normal configuration this is working in v24.4 so either upgrade or use advanced configuration 


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

Hi @rushikeshvartak@PremMahadikar , @Raghu .

Now I have upgraded to version 24.5.
I have configured the below User Update Rule to trigger an Update Account Task.

Saviynt_Savvy_3-1716687644079.pngOnce I updated the Location attribute for the user, in the User Update History, I see ONLY the above rule got triggered as shown below.

Saviynt_Savvy_1-1716687251336.png
But in the Pending Tasks, along with the Update Account Task, I see "Remove Access Tasks" generated through the below Technical Rule (Enabled - Remove Access if Birthright fails, NOT Detective).

Saviynt_Savvy_2-1716687531796.png

In the above Technical Rule, I do not have the location attribute in condition, but it still got triggered and created the 'remove access' tasks.

Saviynt_Savvy_4-1716689533840.png

NOTE: 
The Observation
is, when I don't have the LOCATION attribute in the Technical Rule, how could it even triggers the Birthright Rule.
One more observation I have made is, the Technical Rule has 5 attributes in it's condition. But when I limit the condition to only 3 or less than 3 attributes, then the Technical Rule won't trigger the "Remove Access" tasks.

Could you please suggest why the Technical Rule got triggered when it doesn't have the LOCATION attribute in its Condition.

Is it a bug! or should reconfigure the User Update Rule or Technical Rule.

Thanks & Regards,
SaviyntSavvy

Reconfigure rule with advanced query and proper parenthesis (brackets)


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