Date: 18.01.2021

Platform: Web

Designer: Anton Fischer

Intro

The Mass Change pattern allows users to prepare, review and submit changes for multiple homogenous objects simultaneously.

The Fiori Design Guideline describes a Mass Editing pattern that is the basis for this pattern. However, it doesn’t account for the fact that some changes are more critical have far-reaching consequences (e.g. payroll impact).

Usage

• You need to modify two or more objects simultaneously.
• You want to change multiple properties for a number of objects, and not necessarily the same ones for all objects.
• Changes to the object are critical, and hence need to be reviewed and approved. Usually, a workflow approval is required.
• Business rules are triggered based on the user input, and the user needs to be aware of the outcome before submitting.
• You need to see the result of rule processing before submitting the change.
• You want to allow other people to review your work before it gets submitted.
• You need to change only one object. In that case, use the object page with edit functionality.
• Your changes are non-critical and can be performed without review. In that case, use the Fiori Mass Editing pattern to update objects directly.

Structure

The Mass Change Pattern is implemented using multiple components:

• Multi-select enabled to select any number of items
• Item states: to highlight changed items in the table
• Updated Value (SFSF custom pattern; WIP) to allow review of values per item
• Popover to show all changes in one place
• Button to trigger the edit dialog ("Edit")
• Content switch: to allow users to filter the full table down to only the changed items
• to make changes to multiple items simultaneously (following Fiori's Mass Editing pattern)
• for finalizing actions (submit, cancel)

Behavior

• User selects from items displayed in table.
• Presses edit to bring up the mass editing dialog.
• Upon pressing apply, user is taken back to table and the changes are reflected in table (or, processing happens asynchronously).
• User reviews changes. If errors exist, they need to be resolved before submit.
• repeat step 1–4 as often as necessary until all changes are added.
• User submits changes.

All items start in default state (no highlight). After applying a change to an object (and processing underlying rules), it can be in either one state:

• Modified
• Modified with errors

If one or more items of the mass change are in state “Modified with errors”, this will prevent you from submitting the mass change.

As soon as one item is in one of the modified states, a content switch (see Structure) is shown in the Table Toolbar. This allows users to switch between all items in the table and only the modified (and modified with errors) ones.

Responsiveness and Adaptiveness

The text “Modified” and “Modified with Errors” is clickable and shows all changes for an item in one place. This works as a ‘catch all’ which is particularly helpful when not all table columns can be displayed.

Application-specific example

InVision: https://sapsf.invisionapp.com/share/GMXW4V27QZ8#/423482767\_01\_Landing\_Initial (PW: masschange2020)