Quote:
Originally Posted by bigstyx  a) saving a policy package via File ==> Save as
b) creating a database via File ==> Database Revision control |
a) Creates a copy of your active policy with a new name
b) Creates a copy of your active policy as it currently stands within the policy. Think of it as a document revision control: (example)
1) You save a revision and name it 'pre-marketing deployment'
2) Make all of your policy changes and push policy
3) Let's say it breaks something horribly for argument sake
4) Make a new revision - let's call it 'post-marketing deployment'
5) Since you are in a bind, you can recall the 'pre-' revision and push to get you running again
6) Then you can load the post revision again and correct your mistakes
push and test again, yada yada...