In the previous recipe, you've become familiar with how you can provision most common expiration policies on your libraries with PowerShell. In some cases, more unique scenarios call for more complex solutions.
In this recipe, we'll take a look at some of the scenarios where you need to use custom action executed when the trigger for the expiration is set off.
We'll see how you can kick off a custom workflow performing one of the common actions related to document and record retention. The benefit of using PowerShell in this scenario is mainly around the flexibility when defining multiple policies on many libraries.
Let's see what is involved in using PowerShell to define custom actions for a retention ...