Changes

Jump to: navigation, search

List View Overview

420 bytes added, 14:13, 10 June 2019
no edit summary
|-
||'''Option'''
||Select from a number of types of what you want your button to perform. A common use case is for the '''Option '''function to depend on '''Status - '''for example, on a List View of grant applications, this Batch Update button will change the status of all selected records at once. * Other options: Archiving, updating [[Custom Fields]] to predefined or custom values on either common or Type-specific fields, etc 
|-
||'''Value'''
:: [[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.
 
'''Notes''':
If using '''Status''' for your * Batch Update buttonupdate functionality can also be used to run template formulae, once you save the button an option for writing a confirmation message but will appear. This is not mandatory, but often helpful for users as they can see the batch override all logic restrictions and trigger workflows*  Batch update progress and confirmation at the top of the screen, but may not be aware of the ramifications: leaving a note buttons are available on the function [[Universal Tracking Application|UTAs]] of the button will help them decide whether they want to use the Batch Update button or not. all levels
'''Notes''': * 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. * If ever in doubt, run the Batch Update Button on your [[Backup Server and Testing Instance]]. It is best practice, although not mandatory, for Batch Update buttons to provide one valid progression - e.g. a list view with a predefined filter of all applications in pending approval status, where the last step is to approve them simultaneously and for all notifications to go out at the same time.
==Contact and Company List Views==
==See Also==
* [[Portals]]
* [[Dashboards:Category:Reports]] * [[Portals#List View and Mixed Record Type]] 
2,299
edits

Navigation menu