Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Scenario:

  • Retention policy set on "Expiry Date" column. Starts a workflow that notifies a user.
  • User updates the document (and expiry date)
  • Retention policy no longer fires when the new expiry date is encountered.

I want users to be able to update their document and then receive a further email once their document next expires. However I don't want them pestered if they ignore the email.

share|improve this question
    
I'm having the same problem... Have you by chance managed to solve this? Sincirely, Oleg –  Oleg Feb 24 '12 at 10:01
    
i'm also having the same issue. Once the date is edited in the list, the retenton policy is not being executed for the 2nd time. Retention Policy and Info Management run every 5 mins. Is there a solution ? –  Raj Chahal Apr 2 '12 at 9:00
add comment

3 Answers

In my scenario I needed to monitor a site's last accessed date, but with minimum overhead (so not on every page load in masterpage..) and then after a site was not accessed for 6 months - delete it. I've done that via custom list which had only one item and a retention schedule enabled. List would be created when the site is provisioned. And the retention policy is this: run the expiration action one day after Created date, and then recurrently run it every day. So in this way I have my custom expiration action run every day, and it's doing it's checking...

Hope this helps someone

share|improve this answer
add comment

Have you set the Expiration Policy timer job to run regularly via Central Admin? The expiration date is calculated immediately when the document is updated (or when the Information Management Policy timer job is run), but the action to be performed on the item is not run until the Expiration Policy timer job is run.

share|improve this answer
    
Yup, no effect. This is repeatable in a development environment –  Neil Richards Apr 16 '12 at 13:19
add comment

You could try using Microsoft Visual Studio to write an event receiver. Every time the conditions are met (e.g. due date modified), the event receiver could stop the workflow and restart it.

Similar question on social.msdn.microsoft.com

share|improve this answer
    
SharePoint architecture calls for a retention policy which fires after an amount of time. This should not require a workflow with a wait condition. –  Neil Richards Apr 16 '12 at 13:18
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.