Changes

Versioning

32 bytes added, 19:57, 21 June 2016
no edit summary
'''Note:''' Naming versions with clear and appropriate titles and descriptions will great assistance when using Versioning. Clearly name the baseline version so that it is differentiated from the future versions (ex. Baseline General Application). It may be useful to name application and form versions based on their period name (ex. 2016 Q1 General Application).
 
'''Note:''' You may want to capture fields-sets from the Level 1, Level 2, and Level 3. In this case you will repeat the steps above and create additional "Version Objects" line to capture any additional objects, activities, or transactions.
 
'''Note:''' To change the current version, click on the dropdown menu and select the new version you would like to activate, then click the "Activate" button, and finally click the '''Save''' button at the bottom of the window.
 
Notice the '''Version''' field added next to the '''Field Class''' field. The '''Version''' field contains the name of the version of the application or form that you are currently editing. It is this field that allows you to switch between the different concurrent versions that are available. Here is where you will switch between the "Baseline" application version, the current application version, and the new application you are building and testing.
 
 
===Deleting fields in Versions===
Deleting fields from versions that are not the baseline, will only remove those fields from the specific version you are editing and not other versions.
 
 
===Editing fields in Versions===
:'''Note:''' Toggling between different versions from this page will allow you to easily flip between the existing form and your modified version.
 
:5. Click on the '''+''' icon to add a '''New Field'''
:6. Add all fields required to create the new field. For details on creating custom fields click '''[[Creating Custom Fields|here]]'''.
 
===Adding new field to existing Version===
Add a all new field that has been added to the baseline to an existing version by updating the Versions snapshot.  This will update the field-sets that comprise the selected Version and will include any newly added fields added to the baseline since the last snapshot.
See the section above titled: '''Take a Snapshot/Create a baseline''' for details on taking a snapshot.
 
[[Image:CopyToOldVersion1.png]]
 
This is available against all UTA custom field lists, but only appears once at least one field has been selected.
[[Image:CopyToOldVersion2.png|700px]] 
If you select some custom fields and click on the '''Copy to Older Version''' button then you are presented with the Copy to Older Versions screen.
[[Image:CopyToOldVersion3.png|700px]] 
Users select the Version that the field, or edits, should be added to from the Version drop-down list.
Users must then click on the Submit button, and should a confirmation message to indicate that the changes have been applied.
[[Image:CopyToOldVersion4.png|700px]]
Smartstaff, administrator
4,478
edits