Need information about technical rule

[PinkyChau]

Hi,

We observed that the technical rule did not trigger for users created via import at 05:37:43 AM IST, but it did trigger for users created at 10:37:57 AM IST. Both sets of users have a start date of 2024-06-10 00:00:00. Are there any specific timing constraints associated with the technical rule?

 

[Raghu]

@PinkyChau  User above conditions satisfied all ?

[PinkyChau]

Hi @Raghu yes. its available in preview .

[Manu269]

@PinkyChau  Can you confirm if this rule is written via Advance logic option or via UI?

Try running repair to rule user mapping from Policies page.

[PinkyChau]

hi @Manu269 its advanced query.

Will fixing the rule-user mapping resolve future issues and ensure proper triggering of rules? I was reviewing the document Repairing Rule-User Mappings (saviyntcloud.com and it mentions scheduling a job for repairing. What happens if an issue occurs between the scheduled jobs?

[rushikeshvartak]

This looks like data issue. Do you see this under Execution trail ?

[PinkyChau]

hi @rushikeshvartak under execution trail it is mentioned <did not run zero day since runzeroday is set to false> <rule run is successful> but i have checked in the job its set to yes.

[This message has been edited by moderator to mask sensitive information]

[rushikeshvartak]

• Is this happening daily on same time ?
• Does anyone update configuration before job ran ? Validate audit logs

[PinkyChau]

hi @rushikeshvartak 

1.yes, job is scheduled for daily multiple times.

2.no audit logs for the job.

[PinkyChau]

hi @rushikeshvartak i am able to see another job which is full import where zero day provisioning is off in the job but time of job run is not matching with the user history.

5:37 am IST means 12:07 am UTC

[rushikeshvartak]

Validate job id in users table

[PinkyChau]

hi @rushikeshvartak job_id in user's table is showing for the job "ImportWorkdayUsers_Incremental_Global" which is expected job (zeroday provisioning was on for this).

Also, in excution trail parentid(784215) and jobid(784217) is different from user's table job_id(793021).

for parentjobid job is showing as "ImportWorkdayUsers_Incremental_Global"

and for jobid no trigger is mentioned and runzeroday is showing false

[This post has been edited by a Moderator to remove sensitive information.]

[rushikeshvartak]

Can you change schedule to 1 hr late and validate if issue exists

[PinkyChau]

hi @rushikeshvartak the same technical rule did not triggered for users created via import at 05:37:43 AM IST, but it did trigger later for the users created at 10:37:57 AM IST same day. Also its in prod so we cant change the scheduled timings.

[PremMahadikar · Accepted solution]

Hi @PinkyChau ,

One quick check: In externalconfig.properties file, can you check if the below is enabled

# Set the default Zero Day & Term User Limit
userImport.zeroDayLimit=100

This might be the cause of the issue during import. If the limit crosses 100, it will not trigger birthright technical rule.

Increase the limit to 10,000.

Don't forget to restart!

If this helps your question, please consider selecting Accept As Solution and hit Kudos

[PinkyChau]

hi @PremMahadikar Thankyou .yes it is set to 250 only and the count was 326 during that time .Sure will check with customer if they want to increase this .Thanks again for the suggestion.

[Manu269]

@PinkyChau  any idea how many users where imported during that run?

As pointed out by @PremMahadikar  we even had similar case, where the added in external config was less then the number of users imported and the birthright rule did not trigger.

Make sure to update this with right value and as needed by org.

It has requisite impact.

[PinkyChau]

326 users were imported and 250 was set in externalconfig.properties

[PremMahadikar]

@PinkyChau ,

Perfect!

If this helps, please hit Kudos and select Accept As Solution