Recently, I had a requirement for a list where the approval email should time out after 2 weeks and resend for three occurrences. I successfully used a do until loop to achieve that.
However, in testing, I discovered that the first email (the one that had timed out) still allowed the user to click on the Accept or Reject button, type Comments, and click Submit. I was expecting that email to be frozen (more like what happens in a first to approve type of approval) so that the user would easily be able to tell that approval was timed out. True, if they completed the next approval email (the active one), it wouldn't matter. But I worry that they might skip it thinking they had already completed it.
Is that default approval timeout behavior? I'm trying to decide if I handle this with user training or if there is another programmatic way to deal with this. Thanks in advance for any insight.
