==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.
==Overview==:: [[File:New forms for smartversioning.png|800px|border]]1. Click into the '''VersioningSelect Application ''' greatly reduces field - a drop-down list of available {{UTA}}s within the work required system will appear. :: [[File:Smartversion select apps.png|250px|border]]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 2. After selecting an application, click into the '''Entity '''field which will open a drop-down list of the easy creationassociated [[Entity|entities]] with that application. All {{L1}}, modification{{L2}}, 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{{L3}} entities will be available.
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 events:: [[File:Smartversion select entity. These environments allowed organizations png|130px|border]]Select the ability specific entity level of your application 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 make up the '''Versioning''' feature field-setthat you wish to capture.
'''Note: Global Administrator ''' privileges are required If no specific level is chosen, the system will default to configure this settingthe {{L1}} of that application.For example, it will default to '''Budget '''if the application in question is the '''Budget Manager. '''
3. Once both the '''Application Name '''and '''Entity '''have been chosen, click the button on the right side: '''Take Snapshot. '''
==Getting the Most Out of Versioning Webinar==4. A confirmation pop-up message will appear. Click '''Yes.'''
{{#ev:youtube: [[File:Smartversion are you sure.png|500px|DDCpYI_EcM0 }}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.
:: [[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 entity level at the time that the snapshot was taken is what makes up the '''baseline. '''
==Getting Started * '''Note:''' You may want to capture fields-sets from the Level 1, Level 2, and Taking 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 Snapshot/Creating {{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 Baseline==New Version|activate the version]] in your system.
===Finding the Current Version===
Having followed the steps from the previous sections, you have just enabled Versioning onto your system and created your first snapshot. By default, your '''Current '''is your '''baseline '''version. You can verify the current version used in your system at any time by following the steps below:
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 versions1. The first step in using Versioning is Navigate to create a new version. This process includes giving the version a name and 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 details steps below desired {{UTA}} whose Version you want to create the baselineconfirm.
===Create a new Version==='''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.'''
2. Click on the UTA settings icon - the '''gear icon '''- which will allow you to enter into '''Configuration Mode. '''
:1. Under the Configuration menu click on '''Global Settings'''::[[ImageFile:configurationmenuarcadiaGear icon.png|link:200px|200pxborder]]3. Scroll down until the subheading '''Features and Options. '''
4. Locate the '''Current Version '''field, which will display the current version of that UTA.
:2: [[File:Smartversion current version. Under png|500px|border]]'''Note:''' To change the System Configuration sectioncurrent 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 '''SmartVersioningSave'''::[[Image:versioning_system_configurationbutton at the bottom of the window.png|link:|700px]]
===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 '''on the top right of the page.
:31. Click on After navigating to the desired UTA, click the '''"+"gear icon ''' icon above its name in order to create a new versionenter '''Configuration Mode.::[[Image:new_version_button.png|link:]]'''
:: [[File:Gear icon.png|border]]
2. Click into the tab for the level of object that you have enabled Versioning for.
:43. The Click on the hyperlink labelled '''New VersionCustom Fields.''' window is displayed.::[[Image:create_a_new_version.png|link:|500px]]
At the top of the list of custom fields will be the '''Version '''combo box.
:5The '''Version''' combo box contains the name of the version of the application or form that you are currently editing. Give 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 Version a Name and Description, when done click '''Savebaseline '''application version, the current application version, and the new application you are building and testing.
'''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).
[[Image:Select_custom_field_version2017.png|900px|border|link:]]
===Take The individual Custom Field Setting page will also include be an indication of the '''Active Version''' at the top alongside a Snapshot/Create a baseline===Version combo box.
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#Comparing_Fields_in_Versions|compare fields]] in one Version with another version.
Once you've created a new Version, the '''Version Objects''' section is displayed. This section allows you to select the '''Application Name''' and '''Entity''' and take a Snapshot. The snapshot captures all fields contained in the selected form or application to the newly created version. The baseline is also created by taking a snapshot.
[[Image:Single_custom_field_version2017.png|900px|border|link:]]
: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_entity.png|link:|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.png|link:|500px]]
'''Note:''' You may want to capture fields-sets from the Level ====Editing Fields in Versions====1, Level 2, and Level 3. In this case you will repeat Navigate to the steps above and create additional "Version Objects" line to capture any additional objects, activities, or transactionsdesired 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.'''
2. Click on the '''gear icon '''above the UTA name, which will bring you into the UTA settings in '''Configuration Mode.'''
==Finding :: [[File:Gear icon.png|border]] 3. Click on the Current Version==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.
4. Click on the '''Custom Fields '''hyperlink.
You have enabled Versioning and created your first snapshot5. By default your Current From the '''Version '''drop-down option on the top right, select the Version is the baseline versionwhose fields you want to edit. 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:4. In the '''UTA Properties''' section locate the '''Current Version''' field.::[[ImageFile:Current_versionSmartversion choose version.png|link:400px|border]]:5. The current version is list of Custom Fields displayedwill differ depending on what has been saved as the field-set for the Version that you choose.
'''Note:''' 6. To change the current versionedit a specific field, click on the dropdown menu and select the new version you would like to activate, then click the "Activate" button, and finally click the the '''Savepencil icon ''' button at to the bottom left of the windowcustom 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 - General Settings]] page.
==Custom ==Deleting Fields and Versioningin Versions====It is very 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, deleting fields from baseline will remove your ability to reference those fields and their values, thus removing the ability to use the previously stored values.
Once Versioning is enabled, there 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 a new field added to the Level 1 and Level 2 Custom Fields pageremoved from other versions.
To delete a field, check the box next to the desired field(s) to delete. A '''trashcan icon '''will then appear in the top row of buttons. Clicking on this icon will delete the fields.
:: [[ImageFile:Select_custom_field_versionSmartversion deleting field.png|link:900px|700pxborder]] : :* 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.
<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>
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.
====Comparing Fields in Versions====
1. Navigate to the desired UTA.
===Deleting fields in Versions===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.'''
It is very important that you always double-check the version that you are editing2. Click on the '''Always be carefulgear icon ''' when deleting fields from above the baseline version. Deleting fields from the baseline UTA name, which will delete those fields from all associated applications and forms. Any new snapshots that are taken afterwards will not include bring you into 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 valuesUTA settings in '''Configuration Mode.'''
Deleting fields from versions that are not :: [[File:Gear icon.png|border]] 3. Click on the baselinedesired tab for {{L1}}, {{L2}}, will only remove those fields from or {{L3}} entity associated with the UTA. The levels go in sequential order - the first tab after the '''General '''tab represents the specific version you are editing Level 1 Entity and not other versionsso on.
4. Click on the '''Custom Fields '''hyperlink.
===Editing fields in Versions===5. Click the '''pencil icon '''to edit a specific '''Custom Field.'''
:16. Navigate to The details of the desired UTA:2Custom Field will be displayed. Click on At the UTA Settings icon:3. Click on the appropriate Level 1top right, 2, or 3:4. Click on the the '''Active Version '''Custom Fields" link:5is displayed. From On the right of the '''VersionVersion ''' dropdown optionfield box, select the Version that you will be editing:6. Click button '''SetDiff. ''':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.
:: [[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.
===Creating a new To toggle between which versions you would like to compare this custom field===against, simply select different versions by clicking into each '''Version '''field.
:: [[File:Smartversion comparison.png|750px|border]]====Creating a New Field====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]]'''.
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.'''
===Adding all new field to existing Version===2. Click on the '''gear icon '''above the UTA name, which will bring you into the UTA settings in '''Configuration Mode.'''
Add all new field that has been added to :: [[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 baseline to an existing version by updating first tab after the '''General '''tab represents the Versions snapshotLevel 1 Entity and so on.
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 snapshot4. Click on the '''Custom Fields '''hyperlink.
See the section above titled: 5. Click on the '''+ ''''''Take a Snapshot/Create a baselineicon ''' for details on taking the left hand side to create a snapshotnew field.
:: [[File:Create new field.png|350px|border]]
6. 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]].
===Add / update individual fields =Adding All New Fields to Older an Existing Version====If you want to mass update fields to an existing version, you can easily do by updating the '''Version 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.
Sometimes See [[Versioning#Create a user may wish to apply Baseline|Create a new custom field Baseline]] for details on how to an older version, or to apply changes made in single field, without taking take a snapshot that would apply unwanted updates in other fields to the old version.
The '''Copy ====Add or Update Individual Fields to an Older Version''' option will allow users ====Sometimes a user may wish to do thisapply 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.
[[ImageIn order to do so, follow these steps:CopyToOldVersion1.png]]
1. Navigate to the desired UTA.
This is available against all You can do so by clicking the 9-square menu icon on the top right of your page ({{Icon-Menu}}), and selecting the UTA custom field lists, but only appears once at least one field has been selectedunder the heading '''Applications. '''
[[Image:CopyToOldVersion22.png|700px]]Click on the '''gear icon '''above the 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.
If you select some custom fields and click 4. Click on the the '''Copy to Older VersionCustom Fields ''' button then you are presented with the Copy to Older Versions screenhyperlink.
[[Image:CopyToOldVersion_3The list of Custom Fields will be displayed.png|700px]]
5. Select ''at least one ''custom field for which you want to apply its updated modifications to an older version.
Users select the version (or versions) that the <pre> If a fieldis not selected, or edits, should be added then the Copy to Older Version function will not show up. </pre>6. Click the '''Copy to from Older Version '''option which looks like a '''two page icon '''on the Version drop-down listtop row of buttons.
If :: [[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 is a brand new updated field then it to will automatically be added to the selected Versionsappear.
If the field already exists on the selected :: [[File:Smartversion copy to other versions then updates will only occur if users select the .png|650px|border]] {| class="wikitable"|-||'''UpdateVersion''' option from ||Check the box next to the name of the '''If version that you want to update this field already exists''' settingto. If users leave it as You can also choose '''IgnoreSelect All ''' then if you want to apply this updated field to all of the changes will not be appliedolder versions.
Users must then click |-||'''If field already exists'''||If the field already exists on the Submit buttonselected versions, and should a confirmation message to indicate that the changes have been appliedthen updates will only occur if users specifically select the '''Update '''option.
[[Image:CopyToOldVersion4If a user leaves this option as '''Ignore, '''then changes will not be applied to the field that already exists in older versions.png|700px]]
==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|700pxworkflows]]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:Versioning]] -->
[[Category:Versioning]]
