Update Rules not triggering for Case Conversion of Saviynt Attribute Value when updated from Import

[ReshamDas]

Hi,

We observed that when the value of an attribute in Saviynt profile of a user is updated to the same value, but with a case conversion (eg. lastname value of Mcdowell getting updated as McDowell, or displayname getting updated from JOHN Mcdonald to John McDonald) from CSV import/through user import job execution, this update is not being shown in the 'User Update History' tab of this user, as well as no User Update Rules are getting triggered. As a result, there is a data discrepancy between Saviynt and downstream applications fed by data from Saviynt, as most user attributes are case-sensitive.

In addition, we tried to do same case-based value updates on user attributes through the Saviynt UI. In this case, we observed that it worked perfectly, as the attribute update details showed up as a fresh entry in the 'User Update History' tab, and also the user update rules got triggered, pushing the new attribute value from Saviynt to downstream applications.

Hence, kindly suggest a solution for this issue, as it is necessary to allow case-sensitive changes in user attributes to show up in the 'User Update History' tab, as well as should trigger rules, to move the data downstream.

Here's a similar forum post I found here mentioning the same issue, however it contains no solution and it is blocked, hence creating this new forum post.

[rushikeshvartak]

Case conversion is not considered as change in attribute currently. Please submit idea ticket

[ReshamDas]

Update: This matter had been raised with Saviynt team, and they have identified the issue as below:-

When the RuleRun got triggered through CSV, the system did not detect the case update as a valid change:

HanaRule 18 is what should have been triggered, as it does when the case conversion update happens from UI update. Here's the log analysis from when case conversion happened from Import update, in which case HanaRule 18 was not triggered:-

{"logtime":"2024-06-24 19:45:02,071","thread":"quartzScheduler_Worker-19","level":"DEBUG","class":"services.SaviyntCommonUtilityService","log":"Hanarule fetch query is :: select hr from HanaRule hr where hr.status=0 

{"logtime":"2024-06-24 19:45:02,076","thread":"quartzScheduler_Worker-19","level":"DEBUG","class":"services.SaviyntCommonUtilityService","log":"hanaRuleMap--[SAVHANARULE#1:[com.saviynt.hana.HanaRule : 10], SAVHANARULEDETECTIVE#1_false:[com.saviynt.hana.HanaRule : 10], SAVHANARULE#2:[com.saviynt.hana.HanaRule : 14, com.saviynt.hana.HanaRule : 11, com.saviynt.hana.HanaRule : 15, com.saviynt.hana.HanaRule : 18], SAVHANARULEDETECTIVE#2_false:[com.saviynt.hana.HanaRule : 14, com.saviynt.hana.HanaRule : 11, com.saviynt.hana.HanaRule : 15, com.saviynt.hana.HanaRule : 18], SAVHANARULE#2_5:[com.saviynt.hana.HanaRule : 11, com.saviynt.hana.HanaRule : 18], SAVHANARULE#2_4:[com.saviynt.hana.HanaRule : 14, com.saviynt.hana.HanaRule : 15], 10###ACTN:[com.saviynt.hana.HanaRuleAttribute : 285], 11###ACTN:[com.saviynt.hana.HanaRuleAttribute : 290, com.saviynt.hana.HanaRuleAttribute : 291], 14###ACTN:[com.saviynt.hana.HanaRuleAttribute : 288, com.saviynt.hana.HanaRuleAttribute : 289], 15###COND:[com.saviynt.hana.HanaRuleAttribute : 271, com.saviynt.hana.HanaRuleAttribute : 272, com.saviynt.hana.HanaRuleAttribute : 273, com.saviynt.hana.HanaRuleAttribute : 274], 15###ACTN:[com.saviynt.hana.HanaRuleAttribute : 275], 18###COND:[com.saviynt.hana.HanaRuleAttribute : 298, com.saviynt.hana.HanaRuleAttribute : 299], 18###ACTN:[com.saviynt.hana.HanaRuleAttribute : 300]]

{"logtime":"2024-06-24 19:45:02,158","thread":"quartzScheduler_Worker-19","level":"DEBUG","class":"rulerun.RuleRunService","log":"No data found for processing

{"logtime":"2024-06-24 19:45:02,158","thread":"quartzScheduler_Worker-19","level":"DEBUG","class":"rulerun.RuleRunService","log":"End runRules processing for job id 152105

Saviynt engineering team is working on it to resolve this bug, so that HanaRule 18 is triggered for case conversion update from user import.

[rushikeshvartak]

Please share jira id and targeted version if any

[ReshamDas · Accepted solution]

Hi @rushikeshvartak,

Just received the update from Saviynt team that this is a known issue and has been fixed in the latest release. 

Version Release: 24.7
Jira Ticket #:CSO-5825

[ReshamDas]

Update: This issue has been resolved and tested on the latest build of Saviynt version 24.7