==Overview==
'''Versioning '''(also referred to as '''SmartVersioning''') is a [[SmartSimple]] function that allows you to make concurrent versions of applications and forms while using a common set of underlying [[Custom Fields – General Information|fields]].
Without needing to change the content of previous versions or requiring a test-to-production environment, Versioning means you have the ability to store multiple versions of the same list of fields in a single location. You can test and use a new version prior to it going live.
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 '''copy. When you're ready to create a new version of an application or form, Versioning takes a '''snapshot '''of your core field-set - that is, a copy of all the custom fields and their respective settings. This is the '''baseline '''that will be used as the starting point of your new version.
'''<u>Benefits of Versioning</u>''':
* Greatly reduces the work required to manage the changes that occur in forms and applications
* Easy creation, modification, and testing of forms prior to going live
* Preservation of past forms' values and appearance, allowing [[Global User Administrator|System Administrators]] to view previous form versions in their original format
<pre> You must be a user with SysAdmin privileges to configure the Versioning setting in your system. </pre>
==Configuration - Essentials==
===How Versioning Works===
'''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 field-set, and taking a '''Snapshot '''of the field-set which creates the '''baseline. '''
Follow the steps below to create the baseline.
===Create a New Version===
1. Click on the 9-square menu icon on the top right of your page.
:: {{Icon-Menu}}
2. Under the heading '''Configuration, '''select '''Global Settings.'''
3. Under the heading '''System Configuration, '''click the hyperlink '''SmartVersioning.'''
:: [[File:Smartversioning.png|800px|border]]
Any existing versions that have already been created in your system may be listed here. If you want to edit these, simply click the '''pencil icon '''to the left of each version name.
4. To create a new version, click the '''+ icon '''on the top left.
:: [[File:New smartversion.png|800px|border]]
5. The New Version form will be displayed. Fill out the fields of this form.
:: [[File:New version form.png|600px|border]]
{| class="wikitable"
|-
|[[Image:How.png|50px'''Version ID'''|link=]]|This article number will explain be autopopulated.|-||'''howName''' you can implement this feature ||Provide an appropriate Name for use on your SmartSimple systemnew version.|-||'''Description'''||Provide a narrative description of your new version.|-||'''Condition'''||If applicable, insert in any conditions for the new version. See [[Versioning#Conditional Versioning]] for more information.
|}
* You must fill out at least the '''Name '''and '''Description '''fields to save a new version
* '''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 done inputting information into the fields, click the '''Save '''button.
===Create a Baseline===
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]]
1. Click into the '''Select Application '''field - a drop-down list of available {{UTA}}s within the system will appear.
==Overview==:: [[File:Smartversion select apps.png|250px|border]]'''Versioning''' greatly reduces the work required Pick which application for which you would like to manage the changes that occurs in forms and applications. Versioning accomplishes this by allowing the creation of concurrent versions of applications and forms all using save a common set version of underlying its fields. The result allows for the easy creation, modification, and testing of forms pre-launch. Other benefits include the preservation of past forms values and appearance, allowing admins to view previous form versions in their original format.
Before '''Versioning''' making and testing changes to applications and forms could be cumbersome, and to ensure a smooth transitions many organizations deployed whole testing environments to manage these events2. These environments allowed organizations the ability to build new applications and formsAfter selecting an application, and thoroughly test them before promoting the changes click into the live production environment. Although the '''VersioningEntity ''' does not eliminate field which will open a drop-down list of the need for testing environmentsassociated [[Entity|entities]] with that application. All {{L1}}, {{L2}}, organizations who regularly change or update requirements on applications can now manage this process within the '''Versioning''' feature setand {{L3}} entities will be available.
'''Note: Global Administrator''' privileges are required : [[File:Smartversion select entity.png|130px|border]]Select the specific entity level of your application to make up the field-set that you wish to configure this settingcapture.
'''Note: '''If no specific level is chosen, the system will default to the {{L1}} of that application. For example, it will default to '''Budget '''if the application in question is the '''Budget Manager. '''
==Getting 3. Once both the '''Application Name '''and '''Entity '''have been chosen, click the Most Out of Versioning Webinar==button on the right side: '''Take Snapshot. '''
{{#ev:youtube|DDCpYI_EcM0 }}4. A confirmation pop-up message will appear. Click '''Yes.'''
:: [[File:Smartversion are you sure.png|500px|border]]
5. After you confirm, the '''Version Objects '''section of the version form will reload and display the time and stamp date of the snapshot.
==Getting Started :: [[File:Smartversion created.png|800px|border]] The details outlined in red comprise the snapshot that you have taken - all the fields that were included with that application and Taking a Snapshot/Creating a Baseline==entity level at the time that the snapshot was taken is what makes up the '''baseline. '''
* '''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.
Versioning works by first capturing all of ===Finding the Current Version===Having followed the underlying fields that makes up an application or form. We call this total set of fields steps from the '''"baseline"'''. The baseline set of fields contains all fields in all application previous sections, you have just enabled Versioning onto your system and form versions. The created your first step in using Versioning is to create a new versionsnapshot. This process includes giving the version a name and descriptionBy default, selecting the your '''Application NameCurrent ''' and is your '''Entitybaseline ''' that contains version. You can verify the field-set, and taking a snapshot of the field-set which creates current version used in your system at any time by following the baseline. Follow the details steps below to create the baseline.:
===Create a new 1. Navigate to the desired {{UTA}} whose Version===you want to confirm.
'''Note: '''You can navigate to any UTA by clicking the 9-square menu icon on the top right and clicking on the UTA name under the heading '''Applications.'''
:12. Under Click on the Configuration menu click on UTA settings icon - the '''gear icon '''Global Settings- which will allow you to enter into '''::[[Image:configurationmenuarcadiaConfiguration Mode.png|link:|200px]] '''
:: [[File:Gear icon.png|200px|border]]
3. Scroll down until the subheading '''Features and Options. '''
:24. Under the System Configuration section, click on Locate the '''SmartVersioningCurrent Version '''::[[Image:versioning_system_configurationfield, which will display the current version of that UTA.png|link:|700px]]
:: [[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.
:3. Click on ===Custom Fields and Versioning===Once Versioning is enabled against a UTA object, then the list of [[Custom Fields]] related to that object will also indicate an '''"+"Active Version ''' icon to create a new version.::[[Image:new_version_buttonon the top right of the page.png|link:]]
1. After navigating to the desired UTA, click the '''gear icon '''above its name in order to enter '''Configuration Mode.'''
:4. The '''New Version''' window is displayed.::[[ImageFile:create_a_new_versionGear icon.png|link:|500pxborder]] 2. Click into the tab for the level of object that you have enabled Versioning for.
3. Click on the hyperlink labelled '''Custom Fields.'''
:5. Give At the top of the Version a Name and Description, when done click list of custom fields will be the '''SaveVersion '''combo box.
The '''Note:Version''' Naming versions with clear and appropriate titles and descriptions will great assistance when using Versioning. Clearly combo box contains the name of the baseline version so of the application or form that it you are currently editing. It is differentiated from this field that allows you to switch between the future different concurrent versions (exthat are available. Baseline General Application). It may be useful to name Here is where you will switch between the '''baseline '''application version, the current application version, and the new application you are building and form versions based on their period name (ex. 2016 Q1 General Application)testing.
[[Image:Select_custom_field_version2017.png|900px|border|link:]]
===Take a Snapshot/Create a baseline===
The individual Custom Field Setting page will also include be an indication of the '''Active Version''' at the top alongside a Version combo box.
Once you've created There will also be a new Version, the '''Version ObjectsSet''' section is displayed. This section allows you button to select the '''Application Name''' allow users to [[Versioning#Editing_Fields_in_Versions|edit fields]] in a specific version, and a '''EntityDiff''' and take a Snapshot. The snapshot captures all button to allow users to [[Versioning#Comparing_Fields_in_Versions|compare fields contained ]] in the selected form or application to the newly created one Version with another version. The baseline is also created by taking a snapshot.
:1. Select the '''Application Name''', the dropdown list will include all application forms within the system.:2. Select the '''Entity Level''', this dropdown list will allow the selection of the Level 1, 2, or 3 to make up the field-set that you wish to capture.::[[Image:Version_objects_entitySingle_custom_field_version2017.png|link:900px|500px]]:3. Click the ''''Take Snapshot''''.:4. Click '''Save'''.:5. After clicking the Save button, the window will capture the created on and modified by details as well as display the Version Objects fields.::[[Image:New_version_window_after_save.pngborder|link:|500px]]
'''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.
====Editing Fields in Versions====
1. Navigate to the desired UTA.
You can do so by clicking the 9-square menu icon on the top right of your page ({{Icon-Menu}}), and selecting the UTA under the heading '''Applications.'''
==Finding 2. Click on the '''gear icon '''above the Current Version==UTA name, which will bring you into the UTA settings in '''Configuration Mode.'''
:: [[File:Gear icon.png|border]]
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.
You have enabled Versioning and created your first snapshot4. By default your Current Version is the baseline versionClick on the '''Custom Fields '''hyperlink. You can verify the current version at any time by following the steps below:
:1. Navigate to the desired UTA:2. Click on the UTA Settings icon:3. Click on the Level 1 tab:45. In the From the '''UTA PropertiesVersion ''' section locate drop-down option on the top right, select the '''Current Version''' field.::[[Image:Current_version.png|link:]]:5. The current version is displayedwhose fields you want to edit.
'''Note:''' To change the current : [[File:Smartversion choose version, click .png|400px|border]]The list of Custom Fields displayed will differ depending on what has been saved as the dropdown menu and select field-set for the new version Version that you would like to activate, then click the "Activate" button, and finally click the '''Save''' button at the bottom of the windowchoose.
6. To edit a specific field, click the '''pencil icon '''to the left of the custom field name.
:: [[File:Edit fieldd.png|200px|border]]
You will be brought to the '''Custom Field '''edit page of that field. Make any required changes to the version you are working on.
==* Remember, these edits will only affect the current version you are editing - which can always be known with the text box at the top right - unless you are making changes to the '''baseline '''version. * To learn more about editing a Custom Field, see our [[Custom Fields – General Information#General Settings|Custom Fields and Versioning==- General Settings]] page.
Once Versioning ====Deleting Fields in Versions====It is enabledvery important 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 that are taken afterwards will not include the deleted fields. As well, there deleting fields from baseline will be a new field added remove your ability to reference those fields and their values, thus removing the ability to use the Level 1 and Level 2 Custom Fields pagepreviously stored values.
Deleting fields from versions that are '''not the baseline '''will only remove those fields from the specific version you are editing - they will not be removed from other versions.
[[Image:Select_custom_field_versionTo delete a field, check the box next to the desired field(s) to delete.png|link:|700px]]A '''trashcan icon '''will then appear in the top row of buttons. Clicking on this icon will delete the fields.
:: [[File:Smartversion deleting field.png|900px|border]]
:
:* Remember, you can always note which version you are in with the '''Active Version '''text box that appears on the top right of your page.
Notice the '''<pre> To delete an entire Version''' (not just an individual field added next to the '''Field Class''' field. The '''Version''' field contains the name of the version of the application or form that ), you can only do so when there are currently editing. It is this field that allows you no fields attached 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 testingit.</pre>
===Deleting fields =Comparing Fields in Versions====1. Navigate to the desired UTA.
It is very important that you always doubleYou can do so by clicking the 9-check square menu icon on the top right of your page ({{Icon-Menu}}), and selecting the UTA under the version that you are editing. heading '''Always be carefulApplications.''' 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 2. Click on the '''gear icon '''above the baselineUTA name, which will only remove those fields from bring you into the specific version you are editing and not other versionsUTA settings in '''Configuration Mode.'''
:: [[File:Gear icon.png|border]]
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.
===Editing fields in Versions===4. Click on the '''Custom Fields '''hyperlink.
:1. Navigate to the desired UTA:2. Click on the UTA Settings icon:3. Click on the appropriate Level 1, 2, or 3:45. Click on the the '''Custom Fields" link:5. From the pencil icon '''Versionto edit a specific ''' dropdown option, select the Version that you will be editing:6Custom Field. 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.
6. 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. '''
===Creating a new :: [[File:Smartversion diff.png|400px|border]]7. A modal window that allows '''Version Comparison '''will appear, showing the custom field===settings for two different versions side-by-side.
Best practice for creating new fields are To toggle between which versions you would like to add them to the baseline version first. This makes the new compare this custom field available to all against, simply select different versions once an update snapshot is takenby clicking into each '''Version '''field.
:1. Navigate to the desired UTA:2. Click on the UTA Settings icon[[File:3Smartversion comparison. Click on the appropriate Level 1, 2, or 3png|750px|border]]:4. Click on the '''Custom Fields" link====Creating a New Field====:5. Click on the '''+''' icon Best practice for creating new fields are to add a them to the'''New Fieldbaseline''':6version first. Add all fields required to create This makes the new field. For details on creating custom fields click '''[[Creating Custom Fields|here]]'''available to all versions once an update snapshot is taken.
1. Navigate to the desired UTA.
===Adding all new field to existing Version===You can do so by clicking the 9-square menu icon on the top right of your page ({{Icon-Menu}}), and selecting the UTA under the heading '''Applications.'''
Add all new field that has been added to 2. Click on the '''gear icon '''above the baseline to an existing version by updating UTA name, which will bring you into the Versions snapshotUTA settings in '''Configuration Mode. '''
This will update :: [[File:Gear icon.png|border]] 3. Click on the desired tab for {{L1}}, {{L2}}, or {{L3}} entity associated with the fieldUTA. The levels go in sequential order -sets that comprise the selected Version first tab after the '''General '''tab represents the Level 1 Entity and will include any newly added fields added to the baseline since the last snapshotso on.
See the section above titled: 4. Click on the '''Take a Snapshot/Create a baselineCustom Fields ''' for details on taking a snapshothyperlink.
5. Click on the '''+ ''''''icon '''on the left hand side to create a new field.
===Add / update individual :: [[File:Create new field.png|350px|border]] 6. Input all the fields required to Older Version===create your new field. For details on creating custom fields, see [[Custom Fields – General Information#General Settings|Custom Fields – General Settings]].
Sometimes a user may wish ====Adding All New Fields to apply a new custom field an Existing Version====If you want to mass update fields to an older existing version, or to apply changes made in single you can easily do by updating the '''Version Snapshot. '''This will update the field-sets that comprise the selected Version, without taking a snapshot that would apply unwanted updates in other and will include any newly added fields added to the '''baseline '''since the old versionlast snapshot.
The '''Copy See [[Versioning#Create a Baseline|Create a Baseline]] for details on how to Older Version''' option will allow users to do thistake a snapshot.
[[Image:CopyToOldVersion1====Add 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 might apply unwanted updates in other fields to the old version.png]]
In order to do so, follow these steps:
This is available against all 1. Navigate to the desired UTA custom field lists, but only appears once at least one field has been selected.
[[Image:CopyToOldVersion2You can do so by clicking the 9-square menu icon on the top right of your page ({{Icon-Menu}}), and selecting the UTA under the heading '''Applications.png|700px]]'''
2. Click on the '''gear icon '''above the UTA name, which will bring you into the UTA settings in '''Configuration Mode.'''
If you select some custom fields and click :: [[File:Gear icon.png|border]] 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 '''Copy to Older VersionGeneral ''' button then you are presented with tab represents the Copy to Older Versions screenLevel 1 Entity and so on.
[[Image:CopyToOldVersion34. Click on the '''Custom Fields '''hyperlink.png|700px]]
The list of Custom Fields will be displayed.
Users select the Version that the 5. Select ''at least one ''custom field, or edits, should be added for which you want to apply its updated modifications to from the Version drop-down listan older version.
<pre> If this is a brand new field is not selected, then it the Copy to Older Version function will automatically be added not show up. </pre>6. Click the '''Copy to Older Version '''option which looks like a '''two page icon '''on the selected Versiontop row of buttons.
If the :: [[File:Smartversion copy to older versions.png|350px|border]]7. A modal window that allows you to choose which version you want to apply this updated field already exists on the selected Version then updates will only occur if users select the '''Update''' option from the '''If field already exists''' setting. If users leave it as '''Ignore''' then the changes to will not be appliedappear.
Users must then click on :: [[File:Smartversion copy to other versions.png|650px|border]] {| class="wikitable"|-||'''Version'''||Check the Submit button, and should a confirmation message box next to indicate 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 updated field to all of the changes have been appliedolder versions.
[[Image:CopyToOldVersion4|-||'''If field already exists'''||If the field already exists on the selected versions, then updates will only occur if users specifically select the '''Update '''option.png|700px]]
If a user leaves this option as '''Ignore, '''then changes will not be applied to the field that already exists in older versions.
==Viewing changes to the Application/Form==|}8. Click the '''Submit '''button..
The changes that have been made to modal window will refresh and provide a version view can be viewed by opening confirmation message of '''Update Completed '''if the application or form and selecting field was successfully updated to the appropriate form documentolder version(s).
:1<pre> You cannot copy a Version ''into ''a core field-set; it is a unidirectional process. Navigate to the desired UTA:2. Open the desired application </ form :3. From the Version dropdown option, select the version you with to view.pre>
[[Image:Viewing_changes_to_version.png|link:|800px]]
===Viewing Changes to the Application/Form===
The changes that have been made to a version view can be viewed by opening the application or form and selecting the appropriate form document.
:41. Navigate to the desired UTA. Click '''Set'''
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.'''
:'''Note:''' Toggling between different versions from this page will allow you to easily flip between 2. Open the existing desired application or form and your modified version.
3. From the '''Version '''drop-down option on the top right, select the version that you would like to view.
:: [[File:Smartversion choose version.png|400px|border]]
Toggling between the different versions will allow you to easily flip between the existing form, and your modified version so that you can keep track of what the changes will employ from an applicant perspective.
===Activating a New Version===
1. Navigate to the desired UTA.
==Activating a new Version==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.'''
: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 the '''Current Versiongear icon ''' field.:5. From above the dropdown options select the version UTA name, which will bring you wish to make active.:6. Click on into the UTA settings in '''Activate''' buttonConfiguration Mode.:7. Click '''Save'''.
:: [[File:Gear icon.png|border]] 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 '''Note:General ''' Once an application or form is made active all new submissions will be completed tab represents the Level 1 Entity and associated with the current version. Past submissions will retain their original version informationso on, in chronological order.
4. Under the subheading '''Features and Options, '''locate the '''Current Version field.'''
5. Click into the drop-down list of available versions and select the version you wish to make active for your UTA.
==Batch updating records 6. Click on the '''Activate '''button to Versions==the right of this field.
To 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 desired7.A confirmation message will appear - click '''Yes. '''
: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:[[ImageFile:Batch_update_version_checkmarkSmartversion activate confirmation.png|link:300px|600pxborder]]8. Once the version has been activated, another confirmation message will appear to state that the activation 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.
:31. Click on Navigate to the '''Batch Update''' icon:[[Image:Batch_update_icondesired UTA.png|link:]]
:4. From You can do so by clicking the 9-square menu icon on the '''Update version to:''' drop down field, select top right of your page and selecting the new version:5. Select UTA under the heading '''Batch UpdateApplications.''' button:[[Image:Batch_update_window.png|link:|600px]]
2. Check the box on the right of each application you want to bulk update.
==Conditional :: [[File:Versioning==batch update selected 2019.png|700px|border]]3. Click on the '''Batch Update '''icon found on the top right of your page.
'''Conditional Versioning''' allows for a customized version of an application or form to be displayed to specific users based on conditions you set:: [[File:Batch update button 2019.png|border]]The Batch Update modal window will appear.
Conditions 4. 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 '''drop down '''or use the '''binocular icon '''to look up the options that you can include (but are not limited choose to batch update the records to):for each field.
* Geography:: [[File:Batch update process 2019.png|400px|border]]* Role* Organization type* Gender* Age* Past Activities* Many5. Once you are done selecting your batch update options, many moreclick the '''Update '''button at the bottom of the modal window.
Conditions can also be based on ====Custom Batch Update====Next to the individual fields Batch Update button is a '''down arrow '''button that make up an application or formallows you to '''Custom Batch Update. Any field can be '''Options available include making a '''Copy '''of the basis applications as well as changing the status of a conditionthe applications.
Each Version has a Condition field:: [[File:Custom batch update button 2019. In the example below the condition looks at Country field value entered against the current users profilepng|150px|border]]If you select '''Batch Update Copy, '''a confirmation message will appear to confirm that you want to ''copy ''and will only display trigger the current version if the Country is not set to Canada[[Workflows Overview|workflows]] associated with all selected records.
If you select the second option (Approved),''' '''you will run the '''Batch Update '''to change the status and trigger the [[Image: ConditionalVersion2.pngWorkflows Overview|500pxworkflows]]associated with all selected records.
==Also See==:: [[File:Custom batch update example 2019.png|700px|border]]: :* In this example, a UTA with grants as the Level 1 Entity can be selected and batch '''Approved '''so that each [[Versioning - Why?Status|status]] of the grants selected changes to approved at once.:* When you have successfully updated a record, the [[List View Overview|list]]will reload and there will be a pop-up notification at the top of your screen confirming the number of records that have been updated.:* Note the '''Approved '''status of the record that was successfully updated. This record will now also appear in the second tab, in the list of '''Approved '''grants.
==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.
Conditions can include (but are not limited to):
::* Geography
::* Role
::* Organization type
::* Record type
::* Age
::* 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.
{|class="wikitable"|-|[[Image:WhyEach Version has a Condition field.jpeg|50px|link=?]]|Click [[Versioning - Why?|here]] to learn why this feature 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 a benefit not set to your organizationCanada.|}
See [[System Variables]] and SmartSimple's [[Variable List]] for more information about which variables you might want to use when setting conditions.
<!-- [[CategoryImage:VersioningConditionalVersion2.png|700px]] -->
===Reporting with Versions===
After more than one Version is created, you can select which Version you would like to include in your [[Reports]] by searching through the versions.
<!-- [[Category:Pending Review|EricVersioning]] -->[[Category:Versioning]]
