Associations to Deployments Strategy Guide
Deployments are the replacement for Associations as you move forward with FileWave in future. Deployments allow you to set rules for content delivery just as associations do, but deployments also allow you to group “associations” into one place to edit and organize them commonly.
When using the webadmin you will notice that you can not create associations any longer, and will use deployments in their place. But, don’t worry, deployments are easy to understand and use!
How Are Deployments Different than Associations?
What Deployments are not exactly the same as associations, but they are very, very similar. You ...
What makes Deployments better than Associations?
What Deployments are new, and will replace Associations entirely eventually. But, does this make...
How to decide what is included in a single deployment?
What So deployments allow us to put together multiple payloads for deployment in an easy way and...
Combining payloads into a singular deployment based on metadata
What Every deployment has related metadata about the content being deployed. That is, HOW it sho...
Should I create one, or multiple Deployments?
What We have established in the previous article that you can combine any payloads or destinatio...
The FileWave Associations-to-Deployment Conversion Tool
What We’ve covered in other articles what types of content we might put together in a singular d...
Resolving Conflicts in Associations Conversion
What The guidance we have given in other articles is about making sure metadata matches when con...
Explanation of Clones with Deployments
What Clones are a theoretical concept in FileWave. A clone represents a symbolic link to an actu...
Deployments in FileWave Central (v15+)
What FileWave Deployments (the next generation of Associations) are now fully implemented in Fil...