When you're in Configuration Console working on a particular item, sometimes you may have have two user fields, a list view, and a form all together. All of those components (or however many components make up one development item) can be grouped together with the same tag. When we're looking at bundles then, it's basically a collection of tags - a tag is a collection of configurations, and a bundle is a collection of those tags. This becomes useful when it comes time to deploy or release these into a separate environment. There are also snapshots, which basically is a copy of all of those configurations in that bundle at a certain point in time.
So you have a bundle, which is for your deployment or release, and then you've got a snapshot. These are what create the zip file that you pick up and move to another environment. As we look at the entire workflow of how this works together, your developers are essentially creating configurations and adding the tags as they go. Once you have a bundle, then you can define it by selecting the tags that are associated with whatever data is being prepared to move to another environment.
When everything is ready and the configurations are done, we create our snapshot of that bundle to export from our source or development environment. Running the export utility drops it into the FTP site, whether that's the import delivered or your own FTP site, it handles it along whatever guidelines your system is configured. After this is complete, we move it to the target environment and import the snapshot using an import utility from that FTP site. Once it's in there, we will go through a validation step to ensure that no errors occurred during this process. Finally, we will apply that snapshot and push those configurations into your live or target environment.
The ability to bundle tags of a certain configuration together is probably one of our favorite features of the Web UI Configuration Console. Tune in next week to learn how to manage tags without feeling overwhelmed.