==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.
==Overview=Create a Baseline===Once you have created and '''VersioningSaved ''' greatly reduces a new version, the work required page will reload to manage display the changes that occurs in forms date and applications. Versioning accomplishes this by allowing time stamp of the creation /modification, the name of concurrent versions 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 applications and forms all using available {{UTA}}s within the system will appear. :: [[File:Smartversion select apps.png|250px|border]]Pick which application for which you would like to 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 {{L3}} entities will be available. :: [[File:Smartversion select entity.png|130px|border]]Select the specific entity level of forms preyour application to make up the field-launchset that you wish to capture. Other benefits include '''Note: '''If no specific level is chosen, the system will default to the preservation {{L1}} of past forms values and appearancethat 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. ''' 4. A confirmation pop-up message will appear. Click '''Yes.''' :: [[File:Smartversion are you sure.png|500px|border]] 5. After you confirm, allowing admins to view previous the '''Version Objects '''section of the version form versions will reload and display the time and stamp date of the snapshot. :: [[File:Smartversion created.png|800px|border]] The details outlined in their original formatred 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. '''
Before * '''VersioningNote:''' making and testing changes You may want to applications and forms could be cumbersomecapture fields-sets from the Level 1, Level 2, and to ensure a smooth transitions many organizations deployed whole testing environments to manage these eventsLevel 3. These environments allowed organizations In this case you will repeat the ability steps above and create additional '''Version Objects '''lines to capture any additional objects, activities, or transactions. * '''Tip: '''It is useful to build new applications repeat the process and formscapture field-sets from all levels of a {{UTA}}, and thoroughly test them before promoting the changes into the live production environmentparticularly if they are pulling fields from each other. Although * '''VersioningNote: ''' A snapshot does not eliminate mean that the version is active; the need for testing environmentsversion will not be activated (that is, organizations who regularly change or update requirements on in use to the extent that all applications can now manage in this process within version will pertain with the '''field-set of that version) until you [[Versioning''' feature set#Activating a 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 '''Note: Global AdministratorCurrent '''is your '''baseline ''' privileges are required to configure this settingversion.You can verify the current version used in your system at any time by following the steps below:
1. Navigate to the desired {{UTA}} whose Version you want to confirm.
==Getting '''Note: '''You can navigate to any UTA by clicking the Most Out of Versioning Webinar==9-square menu icon on the top right and clicking on the UTA name under the heading '''Applications.'''
{{#ev:youtube|DDCpYI_EcM0 }}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]]
3. Scroll down until the subheading '''Features and Options. '''
==Getting Started and Taking a Snapshot/Creating a Baseline==4. Locate the '''Current Version '''field, which will display the current version of that UTA.
:: [[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.
===Custom Fields and 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 ===Once Versioning is to create enabled against a new version. This process includes giving the version a name and descriptionUTA object, selecting then the list of [[Custom Fields]] related to that object will also indicate an '''Application Name''' and '''EntityActive Version ''' that contains on the field-set, and taking a snapshot top right of the field-set which creates the baseline. Follow the details steps below to create the baselinepage.
===Create a new Version===1. After navigating to the desired UTA, click the '''gear icon '''above its name in order to enter '''Configuration Mode.'''
:: [[File:Gear icon.png|border]]
2. Click into the tab for the level of object that you have enabled Versioning for.
:13. Under Click on the Configuration menu click on hyperlink labelled '''Global SettingsCustom Fields.'''::[[Image:configurationmenuarcadia.png|link:|200px]]
At the top of the list of custom fields will be the '''Version '''combo box.
:2The '''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. Under Here is where you will switch between the System Configuration section, click on '''SmartVersioningbaseline '''::[[Image:versioning_system_configurationapplication version, the current application version, and the new application you are building and testing.png|link:|700px]]
:3. Click on the '''"+"''' icon to create a new version.::[[Image:new_version_buttonSelect_custom_field_version2017.png|900px|border|link:]]
:4. The individual Custom Field Setting page will also include be an indication of the '''New Active Version''' window is displayed.::[[Image:create_a_new_version at the top alongside a Version combo box.png|link:|500px]]
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.
:5. Give the Version a Name and Description, when done click '''Save'''.
'''Note[[Image:''' 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)Single_custom_field_version2017.png|900px|border|link:]]
===Take a Snapshot/Create a baseline=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.'''
Once you2. Click on the 've created a new Version, the ''gear icon 'Version Objects''' section is displayed. This section allows above the UTA name, which will bring you to select into the UTA settings in '''Application Name''' and '''EntityConfiguration Mode.''' 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.
:: [[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.
: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 on the '''SaveCustom Fields '''hyperlink.: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]]
5. From the '''Version '''drop-down option on the top right, select the Version whose fields you want to edit.
'''Note:''' You may want to capture fields-sets from the Level 1, Level 2, and Level 3: [[File:Smartversion choose version. In this case you png|400px|border]]The list of Custom Fields displayed will repeat differ depending on what has been saved as the field-set for the steps above and create additional "Version Objects" line to capture any additional objects, activities, or transactionsthat you choose.
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.
==Finding * Remember, these edits will only affect the Current Version==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.
====Deleting Fields in 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.
You have enabled Versioning and created your first snapshot. By default your Current Version is Deleting fields from versions that are '''not the baseline '''will only remove those fields from the baseline specific versionyou are editing - they will not be removed from other versions. You can verify the current version at any time by following the steps below:
:1. Navigate To delete a field, check the box next to the desired UTA:2field(s) to delete. Click on the UTA Settings icon:3. Click on the Level 1 tab:4. In the A '''UTA Propertiestrashcan icon ''' section locate will then appear in the '''Current Version''' fieldtop row of buttons.::[[Image:Current_version.png|link:]]:5. The current version is displayedClicking on this icon will delete the fields.
'''Note:''' To change the current version: [[File:Smartversion deleting field.png|900px|border]] : :* Remember, click on the dropdown menu and select the new you can always note which version you would like to activate, then click the "Activate" button, and finally click the are in with the '''SaveActive Version ''' button at text box that appears on the bottom top right of the windowyour 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>
==Custom ==Comparing Fields and Versioningin Versions====1. Navigate to the desired UTA.
Once Versioning is enabledYou can do so by clicking the 9-square menu icon on the top right of your page ({{Icon-Menu}}), there will be a new field added to and selecting the Level 1 and Level 2 Custom Fields pageUTA 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.'''
:: [[ImageFile:Select_custom_field_versionGear icon.png|link:|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.
4. Click on the '''Custom Fields '''hyperlink.
Notice the 5. Click the '''Versionpencil icon ''' field added next to the edit a specific '''Custom 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.
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. '''
:: [[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.
===Deleting fields in Versions===To toggle between which versions you would like to compare this custom field against, simply select different versions by clicking into each '''Version '''field.
It is very important that you always double-check :: [[File:Smartversion comparison.png|750px|border]]====Creating a New Field====Best practice for creating new fields are to add them to the version that you are editing. '''Always be carefulbaseline''' when deleting fields from the baseline versionfirst. Deleting fields from This makes the baseline will delete those fields from new field available to all associated applications and forms. Any new snapshots that are versions once an update snapshot is 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 1. Navigate to the baseline, will only remove those fields from the specific version you are editing and not other versionsdesired 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.'''
===Editing fields :: [[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 Versions===sequential order - the first tab after the '''General '''tab represents the Level 1 Entity and so on.
: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 the '''Custom Fields" link:5. From the Fields '''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 versionhyperlink.
5. Click on the '''+ ''''''icon '''on the left hand side to create a new field.
==Viewing changes :: [[File:Create new field.png|350px|border]] 6. Input all the fields required to the Application/Form==create your new field. For details on creating custom fields, see [[Custom Fields – General Information#General Settings|Custom Fields – General Settings]].
The changes that have been made ====Adding All New Fields to an Existing Version====If you want to mass update fields to a an existing version view , you can be viewed easily do by opening updating the '''Version Snapshot. '''This will update the application or form field-sets that comprise the selected Version, and selecting will include any newly added fields added to the '''baseline '''since the appropriate form documentlast snapshot.
:1. Navigate to the desired UTA:2. Open the desired application / form :3. From the Version dropdown option, select the version you with See [[Versioning#Create a Baseline|Create a Baseline]] for details on how to viewtake a snapshot.
[[Image:Viewing_changes_to_version====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|link:|800px]]
In order to do so, follow these steps:
: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 ({{Icon-Menu}}), and selecting the UTA under the heading '''Applications.'''
:2. Click on the '''Note:gear icon ''' Toggling between different versions from this page above the UTA name, which will allow bring you to easily flip between into the existing form and your modified versionUTA 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.
4. Click on the '''Custom Fields '''hyperlink.
==Creating a new field==The list of Custom Fields will be displayed.
Best practice 5. Select ''at least one ''custom field for creating new fields are which you want to add them apply its updated modifications to the baseline an older version first. This makes the new field available to all versions once an update snapshot is taken.
:1. Navigate <pre> If a field is not selected, then the Copy to the desired UTA:2Older Version function will not show up. Click on the UTA Settings icon</pre>:36. Click on the appropriate Level 1, 2, or 3:4. Click on the the '''Custom Fields" link:5. Click on the Copy to Older Version '''+option which looks like a ''' icon to add a two page icon '''New Field''':6. Add all fields required to create on the new field. For details on creating custom fields click '''[[Creating Custom Fields|here]]'''top row of buttons.
:: [[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 to will appear.
:: [[File:Smartversion copy to other versions.png|650px|border]] {| class===Adding new "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 updated field to existing Version===all of the older versions.
Add all new |-||'''If field that has been added to already exists'''||If the baseline to an existing version by updating field already exists on the Versions snapshotselected versions, then updates will only occur if users specifically select the '''Update '''option.
This If a user leaves this option as '''Ignore, '''then changes will update not be applied to the field-sets that comprise the selected Version and will include any newly added fields added to the baseline since the last snapshotalready exists in older versions.
See the section above titled: |}8. Click the '''Take a Snapshot/Create a baselineSubmit ''' for details on taking a snapshotbutton..
The modal window will refresh and provide a confirmation message of '''Update Completed '''if the field was successfully updated to the older version(s).
==Activating <pre> You cannot copy a new Version==Version ''into ''a core field-set; it is a unidirectional process. </pre>
: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 ===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 is made active all new submissions will be completed and associated with selecting the current version. Past submissions will retain their original version informationappropriate form document.
1. Navigate to the desired UTA.
==Copy to Older 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.'''
Sometimes a user may wish to apply a new custom field to an older version, 2. Open the desired application or to apply changes made in single field, without taking a snapshot that would apply unwanted updated in other fields to the old versionform.
The 3. From the '''Copy to Older VersionVersion ''' drop-down option will allow user on the top right, select the version that you would like to do thisview.
:: [[ImageFile:CopyToOldVersion1Smartversion 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.
This is available against all You can do so by clicking the 9-square menu icon on the top right of your page 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, in chronological order.
If you select some custom fields 4. Under the subheading '''Features and click on the Options, '''locate the '''Copy to Older Current Versionfield.''' button then you are presented with the Copy to Older Versions screen.
[[Image:CopyToOldVersion35. Click into the drop-down list of available versions and select the version you wish to make active for your UTA.png|700px]]
6. Click on the '''Activate '''button to the right of this field.
Users select the Version that the field, or edits, should be added to from the Version drop7. A confirmation message will appear -down listclick '''Yes. '''
If this is a brand new field then it :: [[File:Smartversion activate confirmation.png|300px|border]]8. Once the version has been activated, another confirmation message will automatically be added appear to state that the selected Versionactivation has been successful. Click '''OK.'''
If the 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:: [[File:Smartversion successful activation. If users leave it as png|200px|border]]'''IgnoreNote: ''' then the changes Once an application or form is made active, all new submissions that are completed will not be appliedassociated with the current version - however, past submissions retain their original version information.
Users must ===Batch Updating Records to Versions===To update many different applications and forms in a new version, first start by creating the new version, then click on use the Submit button, batch update feature to update as many applications and should a confirmation message to indicate that the changes have been appliedforms as desired.
[[Image:CopyToOldVersion41. Navigate to the desired UTA.png|700px]]
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.'''
==Batch updating 2. Check the box on the right of each application you want to Versions==bulk update.
To :: [[File:Versioning batch update many different applications and forms to a new version, first start by creating selected 2019.png|700px|border]]3. Click on the '''Batch Update '''icon found on the new version, then use the batch update feature to update as many applications and forms as desiredtop right of your page.
: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_checkmarkBatch update button 2019.png|link:|600pxborder]]The Batch Update modal window will appear.
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 choose to batch update the records to for each field.
:: [[File:Batch update process 2019.png|400px|border]]
5. Once you are done selecting your batch update options, click the '''Update '''button at the bottom of the modal window.
:3. Click on ====Custom Batch Update====Next to the Batch Update button is a '''down arrow '''button that allows you to '''Custom Batch Update. '''Options available include making a ''' icon:[[Image:Batch_update_iconCopy '''of the applications as well as changing the status of the applications.png|link:]]
:4: [[File:Custom batch update button 2019. From the png|150px|border]]If you select '''Batch Update version to:Copy, ''' drop down field, select the new version:5. Select the a confirmation message will appear to confirm that you want to ''copy 'Batch Update''' button:and trigger the [[Image:Batch_update_window.png|link:Workflows Overview|600pxworkflows]]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 [[Workflows Overview|workflows]] 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]]
