Consistency in actions and action location across an application help create an identifiable and easy to learn pattern for users. Resolving, closing, and canceling are all common actions found throughout traditional Pega UI and collaboration.

Canceling

Users should always be able to cancel or undo their actions. Action areas and forms should have a "Cancel" button in the bottom left corner.

Modal dialogs have an “x” in the upper right corner for desktop and on the left in mobile applications. If the modal dialog has actions, it should also have a "Cancel" button on desktop.

Resolving and closing

Cases can be deleted or resolved (closed). Avoid using “Close” as the name of the action because it can be confused with an action to close the tab or window.

This action should be named appropriately based on the use case. Cases that have recently been created can be deleted; but when the history and audit trail of a case needs to be preserved, “resolve” should be the preferred term.

Delete or resolve a case by using the Actions menu on the top right. There should be an additional confirmation message before completing the action.

Collaboration

The Pega Pulse widget allows people to collaborate on cases by commenting and attaching documents. Pulse is shown when the user clicks the Pulse icon in the upper right hand corner of a screen. Pulse opens a slide-out panel. If Pulse needs to be more prominent for a particular application, it is shown directly under the action area.

Bulk actions

Use bulk actions when applying the same action to many items in a list.

When a user selects one or more items in a list, actions that can be done to every selected item are shown in the top actions area. Actions that apply to only one item remain inline with that item.

If pagination is being used, a “Select all” button and selection across all pages should be available. If you have more than three bulk actions, consider putting the bulk actions into an actions menu.

If bulk actions cannot be undone, provide a dialog confirming user’s action. Other types of lists follow the same interaction patterns as grids.