Provisioning transaction Modify

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Hello Experts,

Can you please help me on below issue.

IdentityIQ will retry the same transactions, even if they were provisioned previously. In the attached image, I refresh 364683 four times. The first refresh was the hire event, but the three subsequent refreshes were all trying to do the same thing. any idea how to fix this issue. is there any configuration changes required or is this expected behavior.

Thanks

Provisioning transaction
Provisioning transaction1750Ă—2350 183 KB

2

Hi @niket345,

how many event have you on this identity?

3

Hello @enistri_devo Only one event is triggered. that is Hired

4

Hi @niket345,

what are all the options enabled in refresh task?

Regards,
Arun

5

image
image1423Ă—782 23.8 KB

image
image1475Ă—598 19 KB

Attached identity refresh task with enabled.

6

I refer to Event page on identity. Do you have more joiner event?
image

Also, check the “needsCreateProcessing” flag for your identities. Joiner will always be triggered if the value is true for this flag

7

Hi @niket345,

The same refresh task is being executed four times with the selected options?

8

Hi @niket345,

I would suggest to create one more refresh task and enable below 2 options.

  1. Refresh Assigned, detected roles and Promote additional attributes
    2.Provision assignments

Regards,
Arun

9

@enistri_devo Yes that’s correct> hire event is triggered when needsCreateProcessing is true.

But question is after triggered Hire event for this identity. we refresh the identity, I see it’s trying to provisioning again with Filtered channel. Is it expected behavior or any way to exclude this things.

10

Yes. We have similar Refresh task for identity.

11

@Arun-Kumar okay let me do this way.

also what would be happened if I add nofiltering is true from the Identity Request initialize workflow

12

but needsCreateProcessing is still there after the refresh? if yes, delete it

13

@enistri_devo No. there is no “needsCreateProcessing” in the identity.

1 Like
14

Please check if any web services are being used in the LCM workflow during the hiring process, and whether they are taking a long time to respond. We’ve observed that the Joiner workflow is triggering twice, if any service is causing a delay processing in workflow. Additionally check also “needsCreateProcessing”.

15

@tsandeepsW I have observed that Joiner event is not triggering twice or doesn’t have needsCreateProcessing.

Can you please confirm that is this expected behavior from the SailPoint product.

16

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.