Changes

Versioning

962 bytes added, 00:16, 30 June 2019
no edit summary
|}
* 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 doneinputting information into the fields, click the '''Save '''button. 
===Create a Baseline===
:: [[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 capture. 
 
'''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. '''
3. Once both the '''Application Name '''and '''Entity '''have been chosen, click the button on the right side: '''Take Snapshot. '''
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. '''
* '''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. 
:
:* 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>  
|}
8. Click the '''Submit '''button..<br /><br />
The modal window will refresh and provide a confirmation message of '''Update Completed '''if the field was successfully updated to the older version(s). 
 
<pre> You cannot copy a Version ''into ''a core field-set; it is a unidirectional process. </pre> 
===Viewing Changes to the Application/Form===
[[Image: ConditionalVersion2.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]]
2,299
edits