2,299
edits
Changes
no edit summary
|-
||'''View Name'''
||The name of the list view is editable. Give your list view a distinct name that you will be able to remember and associate with that list view. * '''Note:''' Best practices for naming convention is to make it consistent across the system. Example: '''Rolename - Criteria Summary '''can be applied to all View Names, creating names such as '''Staff - This Year Approved Applications '''
|-
||'''Display Order'''
'''Ex: '''If you want your '''Default List View '''to show up first on the list of list view options, you could set its display order to 1 (or any other amount that is lower than all other list view display orders).
* '''Note: '''Display order can be internally reordered by clicking on the cog icon when accessing a record in list view.
|-
:: [[File:Batch update button.png|border]]
If using '''Status''' for your Batch Update button, once you save the button an option for writing a confirmation message will appear. This is not mandatory, but often helpful for users as they can see the batch update progress and confirmation at the top of the screen, but may not be aware of the ramifications: leaving a note on the function of the button will help them decide whether they want to use the Batch Update button or not.Batch Update buttons work based on [[Role Based Security]].
'''Notes''':
* Batch update functionality can also be used to run template formulae, but will override all logic restrictions and trigger workflows
* Batch Batch update buttons are available on [[Universal Tracking Application|UTAs]] of all levels
* If there are automated processes that may be triggered by a batch update, best option is to open any affected record when in the [[Global User Administrator|System Administrator]] role and select '''Options''' >> '''Workflow History''' to view the process of triggers.
* [[Portals]]
* [[:Category:Reports]]
* [[Portals#List View and Mixed Record Type]]
