Some patterns do not result in No Action Required

[AM]

Hello

I would like to know the mechanism of No Action Required under what conditions.
I conducted the following verification regarding No Action Required.

[Validation Assumption]
Role1: Contains Entitlement1 only

[Validation 1: "No Action Required"]
① Role1 is granted to User1 from UI and Add Access Task is processed in Job
=>Role1 is granted to User1.
② Role1 is granted to User1 by Policy
③ Pending Task is generated
④ Run Provisioning Job
=>Move to Complete Task as No Action Required

[Validation 2: Not "No Action Required"]
① Entitlement1 is assigned to User2 by Request, and the Task of Add Access is processed by Job
②Role1 is granted to User2 from UI
=>A Complete task called No Action Required is suddenly generated, and Role1 is associated with User2
③ Role1 is assigned to User2 by Policy
④ A Pending Task is generated
⑤ Execute the Provisioning Job
=> and No Action Required do not occur, and task processing fails

Validation 2 does not result in No Action Required even though the user already has Role1.

[Question]
Under what conditions is it processed as No Action Required?
What does Saviynt refer to to determine that it is No Action Required?

I would like to understand the mechanism because I am afraid of this kind of thing happening while running Saviynt.

Regards,

[NM]

@AM in validation one was the entitlement already assigned to user profile.?

[AM]

Hi @NM 

> in validation one was the entitlement already assigned to user profile.?

No.

[NM]

@AM and by policy you mean rule?

[AM]

Hi @NM 

>and by policy you mean rule?

Yes.
Trigger the User Update Rule by changing a custom property. The User Update Rule then kicks the Technical Rule.

[Raghu]

@AM 

1.Already group assigned to respected account , again re-adding it will come status "No Action Required".

2.May be accoutn have group in target system ? check it once ?

3.check PROVISIONINGTRIES got cmplted , so you clear number and move task to pending , re-run chekc it

SELECT '1' AS ARSTASKS__STATUS,'0' AS ARSTASKS__PROVISIONINGTRIES, A.TASKKEY AS ARSTASKS__PRIMARYKEY FROM ARSTASKS A WHERE A.TASKKEY in ('XXX');