Changes

||[[Image:How.png|50px|link=|50px]]||This article will explain '''how''' you can implement this feature for use on your SmartSimple system.

==Overview=='''Versioning''' greatly * Greatly reduces the work required to manage the changes that occurs occur in forms and applications. Versioning accomplishes this by allowing the creation of concurrent versions of applications and forms all using a common set of underlying fields. The result allows for the easy * Easy creation, modification, and testing of forms pre-launch. Other benefits include the preservation prior to going live * Preservation of past forms ' values and appearance, allowing admins [[Global User Administrator|System Administrators]] to view previous form versions in their original format.

Before '''Versioning''' making and testing changes to applications and forms could <pre> You must be cumbersome, and to ensure a smooth transitions many organizations deployed whole testing environments user with SysAdmin privileges to manage these events. These environments allowed organizations the ability to build new applications and forms, and thoroughly test them before promoting the changes into the live production environment. Although '''Versioning''' does not eliminate the need for testing environments, organizations who regularly change or update requirements on applications can now manage this process within configure the '''Versioning''' feature setsetting in your system.</pre> 

==Getting '''Versioning '''works by first capturing all of the underlying fields that make up an application or form - this total set of fields is the '''"baseline." '''The baseline set of fields contains all of the fields in all application and form versions. The first step in using '''Versioning '''is to create a new "version" - this process includes giving that version a '''Name, Description, '''selecting the '''Application Name '''and '''Entity '''that contains the Most Out field-set, and taking a '''Snapshot '''of Versioning Webinar==the field-set which creates the '''baseline. '''

Versioning works by first capturing all of the underlying fields that makes up an application or form2. We call this total set of fields Under the heading '''"baseline"'''. The baseline set of fields contains all fields in all application and form versions. The first step in using Versioning is to create a new version. This process includes giving the version a name and descriptionConfiguration, selecting the  '''Application Nameselect ''' and Global Settings.'''Entity''' that contains the field-set, and taking a snapshot of the field-set which creates the baseline. Follow the details steps below to create the baseline.

:1Any existing versions that have already been created in your system may be listed here. Under If you want to edit these, simply click the '''pencil icon '''to the Configuration menu left of each version name. To create a new version, however, click on the '''Global Settings+ icon '''::[[Image:configurationmenuarcadiaon the top left.png|link:|200px]] 

:4==Getting Started and Taking a Snapshot/Creating a Baseline==Versioning works by first capturing all of the underlying fields that makes up an application or form. We call this total set of fields the '''"baseline"'''. The baseline set of fields contains all fields in all application and form versions. The first step in using Versioning is to create a new version. This process includes giving the version a name and description, selecting the '''Application Name'''and 'New Version''Entity' window is displayed'' that contains the field-set, and taking a snapshot of the field-set which creates the baseline.::[[Image:create_a_new_versionFollow the details steps below to create the baseline.png|link:|500px]]

Once you've created : 5. Give the Version a new VersionName and Description, the when done click '''Version ObjectsSave''' section is displayed. This section allows you to select the '''Application NameNote:''' Naming versions with clear and '''Entity''' appropriate titles and take a Snapshotdescriptions will great assistance when using Versioning. The snapshot captures all fields contained in Clearly name the baseline version so that it is differentiated from the selected future versions (ex. Baseline General Application). It may be useful to name application and form or application to the newly created versionversions based on their period name (ex. The baseline is also created by taking a snapshot2016 Q1 General Application).

==Finding '''Note:''' You may want to capture fields-sets from the Current 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.

:1. Navigate to ==Finding the desired UTACurrent Version==:2You have enabled Versioning and created your first snapshot. Click on By default your Current Version is the UTA Settings icon:3baseline version. Click on You can verify the Level 1 tab:4. In the '''UTA Properties''' section locate current version at any time by following the '''Current Version''' field.::[[Image:Current_version.png|link:]]steps below:5. The current version is displayed.

The '''Version''' combo box 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.

[[Image:Select_custom_field_version2017.png|link:|900px|border|link:]]

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.

[[Image:Single_custom_field_version2017.png|link:|900px|border|link:]] 

It is very important that you always double-check the version that you are editing. '''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 versions that are taken afterwards will not include the deleted fields. Also deleting fields from baseline , will only remove your ability to reference those fields from the specific version you are editing and their values removing the ability to use the previously stored valuesnot other versions.

 :1. Navigate to the desired UTA:2. Click on the UTA Settings icon:3. Click on the appropriate Level 1, 2, or 3:4. Click on the '''Custom Fields" link:5. From the '''Version''' dropdown option, select the Version that you will be editing: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.

 :1. Navigate to the desired UTA:2. Click on the UTA Settings icon:3. Click on the appropriate Level 1, 2, or 3:4. 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.  [[Image:Diff_custom_field_version2018.png|link:|900px|border|link:]]

Best 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 UTA:2. Click on the UTA Settings icon:3. Click on the appropriate Level 1, 2, or 3:4. Click on the '''Custom Fields" link: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]]'''. 

 Add all new field that has been added to the baseline to an existing version by updating the Versions snapshot.

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.  The '''Copy to Older Version''' option will allow users to do this.

This is available against all UTA custom field lists, but only appears once at least one field has been selected.

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.

Users must then click on the Submit button, and should a confirmation message to indicate that the changes have been applied.

:1. Navigate to the desired UTA:2. Open the desired application / form :3. From the Version dropdown option, select the version you with to view.[[Image:Viewing_changes_to_version.png|800px|link:]]

:4. Click '''Set'''

:'''Note:''' Toggling between different versions from this page will allow you to easily flip between the existing form and your modified version.

 :1. Navigate to the desired UTA:2. Click on the UTA Settings icon:3. Click on the appropriate Level 1, 2, or 3:4. Under the UTA Properties section, locate the '''Current Version''' field.:5. From the dropdown options select the version you wish to make active.:6. Click on the '''Activate''' 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.  

:1. Navigate to the desired UTA:2. Add a check mark to the check box for each application and form you want to bulk update:[[Image:Batch_update_version_checkmark.png|link:|600px]]   :3. Click on the '''Batch Update''' icon:[[Image:Batch_update_icon.png|link:]] :4. From the '''Update version to:''' drop down field, select the new version:5. Select the '''Batch Update''' button:[[Image:Batch_update_window.png|link:|600px]]

 {|class="wikitable"

||[[Image:Why.jpeg|50px|link=?|50px]]||Click [[Versioning - Why?|here]] to learn why this feature is a benefit to your organization.