Changes

Batch Update

356 bytes added, 19:40, 1 June 2016
no edit summary
:::Level 1 records can be [[Archiving Records|archived]]
::: Level 1 [[Versioning|version]] can be updated
::: Level 1 [[UTA Provider/Consumer Relationships]] can be updated
:* '''Level 2''': [[Status]] and Owner
:::UTA [[Configuring UTA Provider/Receiver (Consumer) Relationships|Consumer/Provider]] <!--per 18763 - Consumer/Provider Batch Update for L2s--> - ability to assign providers to consumer Level 2s
::: Level 2 [[Versioning|version]] can be updated
::: Level 2 [[UTA Provider/Consumer Relationships]] can be updated
:* '''Level 3''': [[Status]] and Owner
:::Level 3 [[Versioning|version]] can be updated
:* '''User''': [[Status]]
There is a default Batch Update option, which provides the ability to update a preset number of options, as well as a customisable Batch Update option, where individual update options can be made available based on role.  Disambiguation: There is also a '''Batch Update''' the for the ''settings'' section of Custom Fields,
found on the '''Field List''' page when editing [[Custom Fields]].
[[Batch Update Custom Field Settings|Click here]] to go to the associated Wiki article.
* '''Important''': [[#Important: Security Information|See below]] for the security implications of allowing Batch Update to be used.
==Customizable batch update options==
 
The Batch update features specific to UTA records can now be configured so that, instead of opening the entire batch update page with all its options, certain batch update options can be made available for specific roles.
 
The customized batch update buttons are built upon listviews. Each Leve1, 2 and 3 listview builder has a tab called "Batch Update Buttons".
 
:[[Image:CustomBatchUpdate.png|700px]]
 
If you click on the New Batch Update Button then you will be presented with the following fields, for use in creating a list of customized batch update buttons for that specific listview. . .
 
* ''Button ID'': will be initially blank, and system generated ID on Save
* ''Display Order'': the order of how buttons are displayed among the action buttons
* ''Button Name'': name given to the button. Will not be exposed to end-users of the system when accessing the button.
* ''Button Label'': accepts both text and icon. Text is required as in classic mode the button label must be text for consistency purpose. In Arcadia it will display the icon, and render the text as caption. If icon not defined for Arcadia then the button will show text.
* ''Description'': optional field to enter general description of the button. Will not be exposed to end-users of the system when accessing the button.
* ''View Roles'': Use Lookup button to defines the user roles to view this button
* ''Option'': drop-down listing all existing fields / attributes of the entity that can be updated using the general batch update page (e.g. Status, Owner, Version, Consumer/Provider)
* ''Value'': field to allow you to select the value that field will be updated to. Can be left blank
 
:[[Image:CustomBatchUpdate2.png|800px]]
 
 
Once the buttons are created, they will show next to the general Batch Update button alongside the other action buttons. Clicking on these button will perform similar actions as the general batch update button, except that the action is pre-configured.
* Any [[Visibility Condition]]s or [[Custom Field Type: Special – Browser Script|Browser Scripts]] that control the Owner or Status fields will be ignored.
 
 
==Customizable batch update options==
 
The Batch update features specific to UTA records can now be configured so that, instead of opening the entire batch update page with all its options, certain batch update options can be made available for specific roles.
 
The customized batch update buttons are built upon listviews. Each Leve1, 2 and 3 listview builder has a tab called "Batch Update Buttons".
 
:[[Image:CustomBatchUpdate.png|700px]]
 
If you click on the New Batch Update Button then you will be presented with the following fields, for use in creating a list of customized batch update buttons for that specific listview. . .
 
* ''Button ID'': will be initially blank, and system generated ID on Save
* ''Display Order'': the order of how buttons are displayed among the action buttons
* ''Button Name'': name given to the button. Will not be exposed to end-users of the system when accessing the button.
* ''Button Label'': accepts both text and icon. Text is required as in classic mode the button label must be text for consistency purpose. In Arcadia it will display the icon, and render the text as caption. If icon not defined for Arcadia then the button will show text.
* ''Description'': optional field to enter general description of the button. Will not be exposed to end-users of the system when accessing the button.
* ''View Roles'': Use Lookup button to defines the user roles to view this button
* ''Option'': drop-down listing all existing fields / attributes of the entity that can be updated using the general batch update page (e.g. Status, Owner, Version, Consumer/Provider)
* ''Value'': field to allow you to select the value that field will be updated to. Can be left blank
 
:[[Image:CustomBatchUpdate2.png|800px]]
 
 
Once the buttons are created, they will show next to the general Batch Update button alongside the other action buttons. Clicking on these button will perform similar actions as the general batch update button, except that the action is pre-configured.
==See Also==
Smartstaff, administrator
4,478
edits