Changes

Versioning

1,228 bytes added, 23:17, 29 June 2019

no edit summary

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

1. Navigate to the desired UTA.

* 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.

:* 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. 

====Comparing Fields in Versions====

1. Navigate to the desired UTA.

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. 

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

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

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

:: [[File:Smartversion diff.png|400px|border]]

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

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.

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. 

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

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

:: [[File:Create new field.png|350px|border]] 

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

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

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. 

See [[Versioning#Create a Baseline|Create a Baseline]] for details on how to take a snapshot. 

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

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

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.''' 2. Click on the '''gear icon '''above the UTA name, which will bring you into the UTA settings in '''Configuration Mode.''' :: [[ImageFile:CopyToOldVersion1Gear 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. The list of Custom Fields will be displayed.

5. Select ''at least one ''custom field for which you want to apply its updated modifications to an older version. 

This <pre> If a field is available against all UTA custom field listsnot selected, but only appears once at least one field has been selectedthen the Copy to Older Version function will not show up.</pre> 

[[Image:CopyToOldVersion26. Click the '''Copy to Older Version '''option which looks like a '''two page icon '''on the top row of buttons.png|700px]]

:: [[File:Smartversion copy to older versions.png|350px|border]]

If 7. A modal window that allows you select some custom fields and click on the '''Copy to Older Version''' button then choose which version you are presented with the Copy want to Older Versions screenapply this updated field to will appear.

:: [[ImageFile:CopyToOldVersion_3Smartversion copy to other versions.png|700px650px|border]] 

{| class="wikitable"

|-

||'''Version'''

||

Check the box next to the name of the version that you want to update this field to. You can also choose '''Select All '''if you want to apply this updated field to all of the older versions.

Users select |-||'''If field already exists'''||If the field already exists on the version (or selected versions) that the field, or edits, should be added to from the Version drop-down listthen updates will only occur if users specifically select the '''Update '''option. 

If a user leaves this is a brand new field option as '''Ignore, '''then it changes will automatically not be added applied to the selected Versionsfield that already exists in older versions. 

|}<br />If the field already exists on the selected versions 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 will not be applied.

Users must then click on the Submit button, and should a confirmation message to indicate that the changes have been applied.

• ← Older edit
• Newer edit →

Emmy Fu

2,299

edits