Difference between revisions of "Versioning - Why?"
Paul Dimerin (talk | contribs) |
|||
| Line 5: | Line 5: | ||
| − | Versioning offers a quick and easy way to add, edit and delete fields in applications and forms whenever you need, without changing the content of previous versions or requiring a test to production (T2P) environment | + | Versioning offers a quick and easy way to add, edit and delete fields in applications and forms whenever you need, without changing the content of previous versions or requiring a test to production (T2P) environment. |
Revision as of 15:20, 1 May 2015
|
This article will explain why this feature is a benefit to your organization. |
In the most basic terms, Versioning gives you the ability to manage change within your Level One and Level Two objects in any of your SmartSimple UTAs. For example, Grants Managers can create multiple versions of any application, while Claims Managers and IMEs can use Versioning to revise claims forms.
Versioning offers a quick and easy way to add, edit and delete fields in applications and forms whenever you need, without changing the content of previous versions or requiring a test to production (T2P) environment.
Versioning means you also have the ability to store multiple versions of the same list of fields in one location, giving you the ability to test and use a new version before it goes live.
Versioning starts with a core field set that contains all fields from all applications and forms, allowing you to choose what you want for any new version you’re creating. You can add as many fields as you wish to your master copy.
When you’re ready to create a new version of a form or application, Versioning takes a “snapshot” of the your core field set. A snapshot is a copy of all the custom fields and their settings, and will be used as the starting point of your new version.
