Why does the "Next Run Date" field not change?

[lonesoac01]

Hello all,

    I am curious of why the "Next Run Date" field does not seem to change.  I deactivated and re-activated the Archive rule and the date stayed the same.  Can anyone provide some clarity on this mystery?

Thank you.

[Community Alums]

Hi @lonesoac0 ,

"Next run Date" populates automatically.

No doubt a develop can force the due dates to be manually defined - but I cannot see a logic that would maintain this: if you had a 4th facility how would you do for staggered reviews all within one quarter.

From a process point-of-view: the way you write it now, it sounds like this access review is a task that takes few days to perform for one person, hence only one facility each month can be reviewed. Since Audit Management is part of all IRM packages, wouldn't it be easier to perform those as part of Engagements within an Audit plan? The Results of those Engagements via Test Plans (Test Templates on the CO) would also impact the Control just like an Indicator would. Engagements also give you the flexibility to move things around due to holidays or sickness - unlike Indicator dates that will just create Indicators 24/7/365 (in your case the 10th of every month no matter what).

The Indicators are meant to monitor 10s, 100s or 1000s of Entities in one go, every month or every quarter++ and not staggered. An manual indicator is also not meant to perform a long checklist of things, but simply confirm that the checklist was performed (in this current use case).

Mark my answer correct & Helpful, if Applicable.

Thanks,

Sandeep

[lonesoac01]

Sandeep,

   I can understand the part of your response of: ""Next run Date" populates automatically." but then you start talking about facilities and access reviews.  Did you accidentally put two responses to two different posts in this one?

[lonesoac01]

I know that the field is supposed to be updated automatically, but WHY is it clearly showing a really late date and not something this year?