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

I have a document library with a property that can be set to three different values:

Pending - > Delete after 90 days
Delete - > Delete immediately
Completed - > fire a workflow that moves items to a location outside of SharePoint

The problem is one of the threee status values can be selected at any time, in any order. I am trying to figure out if the correct behaviour can be triggered with custom retention policies.

I can set up a retention stage for the first two options with a custom retention policy and a delete action, and a second stage for the "Completed" option linked to a workflow. However, if set the property to "Completed" upon the first upload, I would think I would never reach the second stage. I am wondering if there is a way to have multiple stages at once.

share|improve this question
add comment

1 Answer

up vote 2 down vote accepted

I don't think a retention policy would necessarily be the route to take here. It seems as if all of this scould be accomplished with a singular workflow that evaluates the status of the column and takes the desired action as you have specified.

You have 2 immediate actions based on the status of the coulmn, delete or move. Those could be immediately handled via an onchange workflow. You could then have an IRM retention policy that looks at the created plus 90 days and if the status is pending, delete it via workflow. Any other status wouldn't make it to that point and would be deleted by the on change workflow or relocated.

share|improve this answer
    
This is similar to one of the solutions my supervisor suggested, but we had a second retention policy triggering the immediate workflow, which is both unneeded and also introduces staging problems. Would a workflow or event handler be better for the immediate actions? –  xdhmoore Dec 13 '11 at 21:12
    
Either would be suitable, a workflow would be a shorter "development cycle". THat'll be up to the specifics of your environment and organization though. –  PirateEric Dec 13 '11 at 21:14
    
Thanks, this definitely helped clear up my foggy thinking! I this that is what we will end up doing (via workflow), except handling "delete" and "pending" in the same policy, and setting a now + 24 hour limit for the "delete" items in case of accidental deletes. –  xdhmoore Dec 14 '11 at 21:30
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.