AnsweredAssumed Answered

Why this type of Rule causes duplicated Requests?

Question asked by Tilsim Geldisen on May 21, 2018
Latest reply on Dec 10, 2018 by Jennifer Britton

Like • Show 0 Likes0
Comment • 2

Hi All,

We have defined below rule that analyzes missing entitlements of accounts inside business roles.

When it finds a missing entitlement, it creates a request about that missing entitlement and tries to assign it to its user/account.

But unfortunately, this rule schedully works and it creates duplicated requests without looking at previous request completed or not

So the question is, Is there any way to prevent this rule from creating duplicated requests?

Can you have an idea?

Regards, Tılsım.

No one else has this question

Outcomes

2 Replies

Tilsim Geldisen May 24, 2018 4:46 AM
Mark Correct
Correct Answer
Santosh Replied by Ticket:

Hi Tilsim,

Thank you for contacting G&L Technical Support, my name is Santosh and I will be assisting you. Your cases is being tracked with IGL Support as case #SF-01174276.

I have gone through case description and attached print screenshot. There are no duplicate change request generated . You have schedule your rule daily so every day change request is generated based on the rule condition.It's not duplicated requests but if you want to prevent this then don't schedule rules. Run it manually . If a rule change request is taking too long to complete then rule can not campare previous change request data before run bcause rule don't know on what stage previous rule change request is running . Rule will run and generate change on scheduled time , it's not related to previous run..

Thank you,
Santosh
RSA/G&L Technical Support
Like • Show 0 Likes0
Actions
- Jennifer Britton @ Tilsim Geldisen on Dec 10, 2018 6:05 PM
  Mark Correct
  Correct Answer
  Hi, Tilsim! Did this answer your question or did you get resolution elsewhere? I have a similar question because we are running in to a similar issue, and simply NOT having the rule scheduled would miss the entire point of creating it. Also, from your screenshot these are also all on different days, so it doesn't look like you ran it multiple times on the same day and didn't wait for it to complete, causing duplicate requests. It does look like it continued to generate requests because the first request is still in Fulfillment Status, so it's not technically complete, at least not according to IMG/IGL.
  
  One thing I did find helpful was to make sure the Role Membership Rule Difference rules we have in place run daily and finished before the Missing Entitlement Rules run. I also set up separate Missing Entitlement Rules for each role (for various reasons we do have some Roles we don't want it run on) but I can't see why that difference would cause or not cause duplicate requests.
  
  The reason I did find for our duplicate requests was that it's unable to add the account, or see that the account already has the entitlement, due to our collector mapping.
  
  I hope you got your duplicates sorted out.
  Like • Show 0 Likes0
  Actions

Why this type of Rule causes duplicated Requests?

Outcomes

Related Content

Recommended Content