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

Technical rule not triggering

Ivan5533
Regular Contributor
Regular Contributor

Hello all,

We are seeing that there is a technical rule (birthright and detective) that is not triggered when a new user is created from SAP import. As you can see the user matches the condition and the rule trail shows those attributes populated.

Can you check it to see what could be happening? The technical rule works properly when importing from CSV.

As a Workarround we have thought about creating a user update rule that triggers with new users from import and call this technical rule.

JOB:

Ivan5533_0-1713956481751.png

Technical rule:

Ivan5533_1-1713956522890.pngIvan5533_2-1713956624670.png

Ivan5533_0-1713957382204.png

 

 

Rule trail:

Ivan5533_8-1713957059467.png

Ivan5533_3-1713956662769.pngIvan5533_4-1713956704419.png

Ivan5533_6-1713956777865.png

Ivan5533_7-1713956987675.png

**The failed rules are user update rules that send a mail and are failing on purpose, so it is not related, as you can see the trail does not detect the technical rule.

 

 

7 REPLIES 7

rushikeshvartak
All-Star
All-Star

Do see any errors in logs


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

There are no related errors, the only error is the user update rules that send the mail (which fails on purpose). Also, as I say, it works from CSV, it seems that it does not detect the technical rules, is it possible that we have failed to enable something at the endpoint/security system level?

Kind regards,

Ivan

How many users are getting imported is there any limit set on external config / job level


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

Ivan5533
Regular Contributor
Regular Contributor

Hello all,

After opening a ticket to support the error is a bug in version 23.11 and has been solved by upgrading the version.

Thank you very much for your help.

Ivan

Do u have jira number


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

Jira Ticket #:SS-7130

Kind regards,

Ivan

I dont find same in latest release notes 


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