Changes

==<br />Overview==Versioning works by starting with a core field-set that contains all fields from all applications, then allows you to choose which fields you want for any new version you're creating. You can add as many fields as you wish for your master '''baseline 'Versioning ''copy. When you'(also referred re ready to as create a new version of an application or form, Versioning takes a '''SmartVersioningsnapshot ''') of your core field-set - that is , a [[SmartSimple]] function that allows you to make concurrent versions copy of applications all the custom fields and forms while using a common set their respective settings. This is the '''baseline '''that will be used as the starting point of underlying [[Custom Fields – General Information|fields]]your new version. 

||If applicable, write insert in any conditions for the new version. See [[SSLogicVersioning#Conditional Versioning]] conditions for this new versionmore information.

* '''Tip: '''Naming versions with clear and appropriate titles/descriptions will be of great assistance. For example, clearly name the '''baseline '''version so that it is differentiated from any future versions (i.e. '''Baseline General Application'''). It may also be useful to follow a standard naming convention, such as naming the application and form versions based on their period name (ex: '''2016 Q1 General Application''')so that you know when the versions existed. * '''Tip: '''Period-based dates such as '''Up to 2020 Budget Manager '''are particularly useful for future-facing Versioning; label the Version so that you know you will not make it active until the time has come. 

6. When you are doneinputting information into the fields, click the '''Save '''button. 

* '''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 '''lines to capture any additional objects, activities, or transactions. * '''Tip: '''It is useful to repeat the process and capture field-sets from all levels of a {{UTA}}, particularly if they are pulling fields from each other. * '''Note: '''A snapshot does not mean that the version is active; the version will not be activated (that is, in use to the extent that all applications in this version will pertain with the field-set of that version) until you [[Versioning#Activating a New Version|activate the version]] in your system. 

====Editing Fields in Versions====

====Deleting Fields in Versions====

<pre> To delete an entire Version (not just an individual field), you can only do so when there are no fields attached to it. </pre>  ====Comparing Fields in Versions====

34. Click on the '''Custom Fields '''hyperlink.

45. Click the '''pencil icon '''to edit a specific '''Custom Field.'''

56. The details of the Custom Field will be displayed. At the top right, the '''Active Version '''is displayed. On the right of the '''Version '''field box, select the button '''Diff. '''

67. A modal window that allows '''Version Comparison '''will appear, showing the custom field settings for two different versions side-by-side.

====Creating a New Field====

34. Click on the '''Custom Fields '''hyperlink.

45. Click on the '''+ ''''''icon '''on the left hand side to create a new field.

56. Input all the fields required to create your new field. For details on creating custom fields, see [[Custom Fields – General Information#General Settings|Custom Fields – General Settings]]. 

====Adding All New Fields to an Existing Version====

====Add / update individual fields or Update Individual Fields to an Older Version====Sometimes a user may wish to apply a new custom field to an older version, or they might want to apply changes made in a single field, without taking a snapshot that would might apply unwanted updates in other fields to the old version.

The '''Copy to Older Version''' option will allow users In order to do this.so, follow these steps: 

[[Image:CopyToOldVersion11. Navigate to the desired UTA.png]]

This is available against all 2. Click on the '''gear icon '''above the UTA custom field listsname, but only appears once at least one field has been selectedwhich will bring you into the UTA settings in '''Configuration Mode.'''

:: [[ImageFile:CopyToOldVersion2Gear icon.png|700pxborder]] 3. Click on the desired tab for {{L1}}, {{L2}}, or {{L3}} entity associated with the UTA. The levels go in sequential order - the first tab after the '''General '''tab represents the Level 1 Entity and so on. 

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 screenThe list of Custom Fields will be displayed.

[[Image:CopyToOldVersion_35.png|700px|border]]Select ''at least one ''custom field for which you want to apply its updated modifications to an older version. 

Users select the version (or :: [[File:Smartversion copy to older versions) .png|350px|border]]7. A modal window that the allows you to choose which version you want to apply this updated field, or edits, should be added to from the Version drop-down listwill appear.

If :: [[File:Smartversion copy to other versions.png|650px|border]] {| class="wikitable"|-||'''Version'''||Check the box next to the name of the version that you want to update this field to. You can also choose '''Select All '''if you want to apply this is a brand new updated field then it will automatically be added to all of the selected Versionsolder versions.

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

Users must If a user leaves this option as '''Ignore, '''then click on changes will not be applied to the Submit button, and should a confirmation message to indicate field that the changes have been appliedalready exists in older versions. 

[[Image:CopyToOldVersion4|}8. Click the '''Submit '''button..png|700px]]

The modal window will refresh and provide a confirmation message of '''Update Completed '''if the field was successfully updated to the older version(s).  <pre> You cannot copy a Version ''into ''a core field-set; it is a unidirectional process. </pre>  ===Viewing changes Changes to the Application/Form===

:: 1. Navigate to the desired UTA. You can do so by clicking the 9-square menu icon on the top right of your page and selecting the UTA under the heading '''Applications.''' :: 2. Open the desired application / or form. :: 3. From the '''Version '''drop-down option on the Version dropdown optiontop right, select the version that you with would like to view.  :: [[ImageFile:Viewing_changes_to_versionSmartversion choose version.png|800px400px|link:border]]:: 4. Click '''Set''':: '''Note:''' Toggling between the different versions from this page will allow you to easily flip between the existing form , and your modified versionso that you can keep track of what the changes will employ from an applicant perspective. ===Activating a new New Version===:: 1. Navigate to the desired UTA. You can do so by clicking the 9-square menu icon on the top right of your page and selecting the UTA under the heading '''Applications.''' :: 2. Click on the '''gear icon '''above the UTA name, which will bring you into the UTA Settings iconsettings in '''Configuration Mode.''' :: [[File:Gear icon.png|border]] 3. Click on the appropriate desired tab for {{L1}}, {{L2}}, or {{L3}} entity associated with the UTA. The levels go in sequential order - the first tab after the '''General '''tab represents the Level 1Entity and so on, 2, or 3in chronological order. :: 4. Under the UTA Properties sectionsubheading '''Features and Options,  '''locate the the '''Current Versionfield.''' field.:: 5. From Click into the dropdown options drop-down list of available versions and select the version you wish to make activefor your UTA.:: 6. Click on the the '''ActivateActivate ''' buttonto the right of this field.:: 7. Click A confirmation message will appear - click '''SaveYes. '''. :: '''Note[[File:''' Smartversion activate confirmation.png|300px|border]]8. Once an application or form is made active all new submissions will be completed and associated with the current version. Past submissions has been activated, another confirmation message will retain their original version information.==Batch updating records to Versions==To update many different applications and forms appear to a new version, first start by creating state that the new version, then use the batch update feature to update as many applications and forms as desiredactivation has been successful. Click '''OK.'''

:: [[File:Smartversion successful activation.png|200px|border]]'''Note: '''Once an application or form is made active, all new submissions that are completed will be associated with the current version - however, past submissions retain their original version information.  ===Batch Updating Records to Versions===To update many different applications and forms in 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 UTA. You can do so by clicking the 9-square menu icon on the top right of your page and selecting the UTA under the heading '''Applications.''' :: 2. Add a check mark to Check the check box for on the right of each application and form you want to bulk update. :: [[ImageFile:Batch_update_version_checkmarkVersioning batch update selected 2019.png|600px700px|link:border]]:: 3. Click on the the '''Batch UpdateUpdate ''' iconfound on the top right of your page. :: [[ImageFile:Batch_update_iconBatch update button 2019.png|link:border]]:: The Batch Update modal window will appear. 4. From On the left side, you are able to select which fields you want to update. As soon as you select a field, its options will appear on the right side. Either select from the '''Update version to:drop down ''' drop down field, select the new version:: 5. Select or use the '''Batch Updatebinocular icon ''' buttonto look up the options that you can choose to batch update the records to for each field.  :: [[ImageFile:Batch_update_windowBatch update process 2019.png|600px400px|link:border]]5. Once you are done selecting your batch update options, click the '''Update '''button at the bottom of the modal window.  ====Custom Batch Update==Conditional Versioning==Next to the Batch Update button is a '''Conditional Versioningdown arrow ''' button that allows for a customized version you to '''Custom Batch Update. '''Options available include making a '''Copy '''of the applications as well as changing the status of an application or form to be displayed to specific users based on conditions you setthe applications.

Conditions can include (but are not limited :: [[File:Custom batch update button 2019.png|150px|border]]If you select '''Batch Update Copy, '''a confirmation message will appear to):confirm that you want to ''copy ''and trigger the [[Workflows Overview|workflows]] associated with all selected records.

:* Geography:* Role:* Organization type:* Gender:* Age:* Past Activities:* ManyIf you select the second option (Approved), many moreConditions can also be based on ''' '''you will run the '''Batch Update '''to change the individual fields that make up an application or form. Any field can be status and trigger the basis of a condition[[Workflows Overview|workflows]] associated with all selected records.

Each Version has a Condition field:: [[File:Custom batch update example 2019. png|700px|border]]: :* In this example, a UTA with grants as the example below Level 1 Entity can be selected and batch '''Approved '''so that each [[Status|status]] of the condition looks grants selected changes to approved at Country field value entered against once.:* When you have successfully updated a record, the current users profile, [[List View Overview|list]] will reload and there will only display be a pop-up notification at the top of your screen confirming the current version if number of records that have been updated.:* Note the '''Approved '''status of the Country is not set to Canadarecord that was successfully updated. This record will now also appear in the second tab, in the list of '''Approved '''grants.

[[Image: ConditionalVersion2==Configuration - Advanced=====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.png|700px]]

{| class="wikitable"|-||[[Image:Why.jpeg|link=?|50px]]=Reporting with Versions===||Click After more than one Version is created, you can select which Version you would like to include in your [[Versioning - Why?|hereReports]] to learn why this feature is a benefit to your organizationby searching through the versions.|}