Changes

:: {{Icon-Menu}} <br />2. Under the heading '''Configuration, '''select '''Global Settings.''' 

:: [[File:New smartversion.png|800px|border]]<br />5. The New Version form will be displayed. Fill out the fields of this form. 

insert:: {| class="wikitable"<br />|-<br />'''Version ID'''<br />>-<br />'''Name'''<br />>-<br />'''Description'''<br />>-ConditionSSLogic <br />'''Condition'''<br />SSLogic if applicable.<br />>}<br />* You must fill out at least the Name and Description fields the '''Name '''and '''Description '''fields to save a new version. <br />* Naming versions with clear and appropriate titles and descriptions will be of great assistance - clearly name the baseline version so that it is differentiated from the future version. For example, Baseline  '''Baseline General Application. It  '''It may be useful to name the application and form versions based on their period name, as well (ex: 2016  '''2016 Q1 General Application)'''.  6. When done, click the '''done,Save ''' click the Save buttonbutton.  

Once you have created and '''Saved ''' a new version, the page will reload to display the date and time stamp of the creation/modification, the name of the creator/modifier, and the '''Version Objects '''section. Through the '''Version Objects '''section, we will take the snapshot that comprises the baseline field-set for this version.>

:: [[File:New forms for smartversioning.png|800px|border]]

:: [[File:Smartversion select entity.png|130px|border]]

:: [[File:Smartversion are you sure.png|500px|border]] 

:: [[File:Smartversion created.png|800px|border]] 

 ===Finding the Current Version Version===Having followed the steps from the previous section, you have enabled '''Versioning '''just enabled Versioning onto your system and created your first snapshot. By default, your '''Current Version Current '''is your your '''baseline. baseline '''version. You can verify the current version used in your system at any time by following the steps below.: 

2. Click on the UTA settings icon - the '''gear icon '''- which will allow you to enter into '''Configuration Mode. ''' :: [[File:Gear icon.png|200px|border]]

:: [[File:Smartversion current version.png|500px|border]]'''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.

'''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.==Custom Fields and VersioningOnce Versioning==Once Versioning is enabled against a UTA object, then the list of Custom Fields will include be an indication of the "Active Version" at the top alongside a Version combo box.The'''Version'''

The individual Custom Field Setting page will also include be an indication of the "Active Version" at the top alongside a Version combo box.There will also be a

There will also be a '''Set'''button to allow users to [[Versioning#Editing_fields_in_Versions|edit fields]] in a specific version, and a '''Diff''' button to allow users to [[Versioning#Compare_fields_in_Versions|compare fields]] in one Version with another version.

Deleting ===Editing fields in VersionsIt is very important that you always double-check the version that you are editing.Versions=== '''Always be careful'''  when deleting fields from the baseline version. Deleting fields from the baseline will delete those fields from all associated applications and forms. Any new snapshots that are taken afterwards will not include the deleted fields. Also deleting fields from baseline will remove your ability to reference those fields and their values removing the ability to use the previously stored values.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 Versions1: 1. Navigate to the desired UTA2UTA: 2. Click on the UTA Settings icon3icon: 3. Click on the appropriate Level 1, 2, or 343: 4. Click on the '''Custom Fields" link5link: 5. From the '''  Version ''' dropdown option, select the Version that you will be editing6editing: 6. Click '''  Set ''': 7. Make any required changes to the version your are working on (remember that these edits will only affect the current version you are editing, unless you are making changes to the baseline version.Compare fields in Versions1. Navigate to the desired UTA2. Click on the UTA Settings icon3. Click on the appropriate Level 1, 2, or 34. Click on the '''  Custom Fields" link.5. Select the versions to be compared from the 2 drop-downs.6. The screen should automatically refresh and show the custom field settings for the 2 versions side-by-side.    

Creating a new fieldBest practice for creating new fields are to add them to the baseline version first. This makes the new field available to all versions once an update snapshot is taken.1. Navigate to the desired UTA2. Click on the UTA Settings icon3. Click on the appropriate Level 1, 2, or 34. Click on the '''Custom Fields" link5. 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 all new field to existing VersionAdd 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.Add / update individual fields to Older VersionSometimes a user may wish to apply a new custom field to an older version, or to apply changes made in single field, without taking a snapshot that would apply unwanted updates in other fields to the old version.The '''  Copy to Older Version ''' option will allow users to do this.[[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:CopyToOldVersion_3.png|700px|border]]Users select the version (or versions) that the field, or edits, should be added to from the Version drop-down list.If this is a brand new field then it will automatically be added to the selected Versions.If the field already exists on the selected versions then updates will only occur if users select the '''  Update

See the section above titled: ''' option from the Take a Snapshot/Create a baseline'''for details on taking a snapshot.

''' setting===Add / update individual fields to Older Version===Sometimes a user may wish to apply a new custom field to an older version, or to apply changes made in single field, without taking a snapshot that would apply unwanted updates in other fields to the old version. If users leave it as '''

Toggling between different versions from this page will allow you to easily flip between the existing form and your modified version[[Image:CopyToOldVersion_3.Activating a new Version1. Navigate to the desired UTA2. Click on the UTA Settings icon3. Click on the appropriate Level 1, 2, or 34. Under the UTA Properties section, locate thepng|700px|border]]

If this is a brand new field.5. From then it will automatically be added to the dropdown options select the version you wish to make activeselected Versions.6. Click on the

If the field already exists on the selected versions then updates will only occur if users select the '''ActivateUpdate'''option from the '''If field already exists''' setting. If users leave it as '''Ignore''' then the changes will not be applied.

button.7. Click '''Save'''  . '''Note:'''  Once an application or form is made active all new submissions will be completed and associated with the current version. Past submissions will retain their original version information.Batch updating records to VersionsTo update many different applications and forms to a new version, first start by creating the new version, then use the batch update feature to update as many applications and forms as desired.1. Navigate to the desired UTA2. Add a check mark to the check box for each application and form you want to bulk update [[Image:Batch_update_version_checkmark.png|600px|link:]]  3. Click on the '''Batch Update'''  icon [[Image:Batch_update_iconCopyToOldVersion4.png|link:700px]]  4. From the '''Update version to:'''  drop down field, select the new version5. Select the '''Batch Update'''  button [[Image:Batch_update_window.png|600px|link:]]  Conditional Versioning '''Conditional Versioning'''  allows for a customized version of an application or form to be displayed to specific users based on conditions you set.Conditions can include (but are not limited to):

 Conditions can also be based on the individual fields that make up an application or form. Any field can be the basis of a condition.Each Version has a Condition field. In the example below the condition looks at Country field value entered against the current users profile, and will only display the current version if the Country is not set to Canada.

 ==Also See==