Auto-close RITMs not approved within 30 days

Tracey Wilmot
Tera Contributor

Currently, we are running a report on a daily basis to check for unapproved requests and manually marking them as Closed Incomplete if the request is not approved within 30 days.  We are looking for a way to automate this.

I think I need to setup a Scheduled Job but I'm not sure what the content of the script should be.  Any help would be greatly appreciated.

Many thanks
Tracey

1 ACCEPTED SOLUTION

Yes, you can trigger an email here. Refer to screenshot below from the above code which I have shared:

find_real_file.png

So just after gs.log line you can use below syntax to trigger your notification:

gs.eventQueue('Event Name',children,recipeint1, recipient2);

//Replace recipeint1 & recipeint2 should be the user object to whom you want to send the email to. 
Also Event Name need to be configured by navigating to "Registry" module and then use it here.

 

Then go to Notification module and use Trigger as Event is fired and select the same event name and make sure to check below parameter as True in Whom to receive tab:

Parm1

Parm2

Send to Event Creator

 

Then finally define the Notification content.

Regards,

Shloke

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

View solution in original post

18 REPLIES 18

Community Alums
Not applicable

The best "out of the box" way to resolve this is to add a 'Due Date' to the approvals. 

This will allow you to either auto approve or auto reject based on a timeframe. 

Thanks Mike.  OOB is always best for me 🙂  We have many different workflows, would I have to go into each one and add a 'due date' to each approval?

We are looking to apply this to every single request item.

Many thanks

Tracey

Community Alums
Not applicable

Hi Tracey, 

Yes, you'd need to put this on each approval. It then allows you to have different timeframes on request types, and allow some to auto approve and other auto reject. 

I'd suggest a way to deploy this would be to start with the high frequency items first, and add it as a new standard to your request management process, so that any new approvals your teams are building, always include a due date. 

Until this is completed, you can get anyone with the admin or approval admin role to amend these records using "update all" and you can reject them that way

find_real_file.png

Doing this you will be presented with a blank form, where you can include the rejection reason, and set the state to rejected.

Mike

Community Alums
Not applicable

I've just realised, in the above screenshot I've included all approvals older than 30 days, not just requests.. more conditions required!