Configuring Mass Updates

Mass update enables users to make the same change to multiple items at the same time. For example, users can reopen multiple closed items at the same time.

Depending on their privileges, users can use mass update to simultaneously:

Transition, update, or delete multiple primary items.
Update or delete multiple auxiliary items.
Modify values for specific fields.

In SBM Work Center, users can perform mass updates from Listing reports, activity views, and backlog views.

Note: The Editable Grid also allows users to update multiple items at the same time but if differs from mass update because users can make a variety of changes to information in multiple items at the same time. The Editable Grid is available for Listing reports. Users who have privileges to update items in reports can switch to edit mode and modify items in the list.

Considerations for Using Mass Update

Consider this information as you enable Mass Update:

Post Item or Create Subtask transitions are not available for mass updates.
Transitions that are set to require attachments are not available for mass updates.
When you select the Allow mass updates check box for dependent fields, be sure to do the same for all independent fields that drive the dependent field's values. If you fail to do this, users will not have any options to select when mass updating items.
Custom forms and any features they include are not available for mass updates. For example, AE Plug-In JavaScript API functions on a custom form cannot be used for mass updates. This includes field validation; auto-filled fields; information messages; and filters on Multi-Relational, Single Relational, Sub-Relational, Multi-Selection, and Single Selection fields.
If your mass transition executes a script or Web transition in the pre-transition context, the script and Web service appears to execute twice against each item in the list; however, the first execution is performed against a temporary record and the actual database record for each item is only affected once. This behavior is by design to prevent a potential over-consumption of memory.
Note that if the script or Web service affects other items that are not in the mass transition list (or if they affect external systems or objects that are not in the SBM database), the script or Web service could affect those objects twice. Therefore, it is best to avoid calling pre-transition scripts or Web services in a mass transition, unless you use the MassTransPreForm Shell property to prevent this from happening.

Enabling Mass Updates

To enable mass updates for fields:

Select the Data Design filter, and then select the table that contains the fields that you want users to change during a mass update.
Select the Attributes tab.
Select the Allow mass update check box.
Note: You can override this setting in SBM Application Administrator for default fields in projects and for transition fields.
Grant the Mass Update Items privilege through roles in SBM Composer or to users and groups in SBM Application Administrator.