Workflow Approval Rule - If-Else - No response

Hi Craig

Can we have a screenshot of the Customized Action buttons? Specifically, so we can see the "Action Type" for "Keep Account" and "Delete Account"?

Hi Stu. 

Here is a screenshot. I have no idea at the moment if i have set them up right as its the first time i am trying to do something based on what was selected. 

Something you might already be aware of, but just keep in mind that with a Reject response, Active Roles will completely discard the request and terminate the workflow. Control is not turn back over to the workflow to then do something in the event a Reject action is selected.

Thanks Richard. I am sure i read something about that a long time ago and why i set both the Keep and Delete buttons to Complete. i have no idea right now if it will actually do what i expect though 

Hi. 

So just to update. The Keep Account and Delete Account buttons are working . Keep just extends the accountexpiry but 21 days and delete at the moment just moves the account to a deprov OU. 

So the section i am trying to work out is the no responce . I am open to suggestions on this. 

I need to either capture that the responce was cancelled or Keep or Delete account was not selected in X days.

The Keep Account and Delete Account buttons

The approval time limit setting

Do you have a VA where you are tracking when the Request was initiated?  If yes, my thought was that you could have an automation workflow that looks for "queued" accounts (appearing in an MU based on the fact that they have a deletion request date) and then sends a notification to say that such and such an account deletion request was ignored?

Do you have a VA where you are tracking when the Request was initiated?  If yes, my thought was that you could have an automation workflow that looks for "queued" accounts (appearing in an MU based on the fact that they have a deletion request date) and then sends a notification to say that such and such an account deletion request was ignored?

Hi Johnny, No, I don't have a VA for when the request was initiated, but I am happy to explore this. 

This has given me an idea of the same track I think you are going down. 

I already have a script that checks to see if the user account is 14 days into its 21-day life. If it is at 14 days, the script sets a Boolean to VA to TRUE, which is kicking off the workflow in this post. 

I could get it as you say to stamp another VA with the date and time the request was made. Then create a MU with the accounts that have that date and time and then have a different workflow that runs once a day.  if the date and time in the VA is greater than one day, for example, then do something in the workflow like disable the user. 

Then in this workflow in this post if someone clicks Keep Account then it removes the value from the VA with the request time. I think that may work 

I will give this ago