Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Standard icons

Updated on April 5, 2022

Standard variations of pxIcon are provided. Each is preconfigured with an icon, tooltip, and action. As a best practice, use these standard rules to ensure correct appearance and behavior.

If the action is not included in the list, keep pxIcon and use the Parameters dialog to configure the control.

This table below provides the icon name, the description of action invoked when clicked, and the standard icon control, which contains its parameters.

Icon NameIcon and Action> Control Rule
Add ItemAdds (above or below) a row to a grid, tree, or tree grid layoutpxIconAddItem
Add New WorkAdds a new work item using the primary page data. Saves the new work item on the deferred list.pxIconAddNewWork
Attachments Presents a list of work item attachments, so users can view or add attachments. This icon appears only for users who hold the Work-.AccessAuditTrail privilege. pxIconAttachments
BlankNo action is associated with it.pxIcon
CancelCloses the current form without applying any changes.pxIconCancel
ContentsFor a cover work item, changes the form to allow users to view and navigate among the covered work items. You can override a standard list view rule to control details of this display.pxIconContents
Delete ItemRemoves a row in a grid, tree, or tree grid layout.pxIconDeleteItem
Enable Action SectionPresents the user form in review-only mode; inputs allowed in the action section only.pxEnableActionSection
Expand/CollapseRedraw the form with all areas fully expanded.pxIconExpandCollapse
ExploreFor a folder work item, changes the form to allow users to view and navigate among the associated work items.pxIconExplore
Finish AssignmentSubmits changes and marks this assignment as complete.pxIconFinishAssigment
Get Next WorkCancels any unsubmitted changes and finds the most important assignment to work on next.pxIconGetNextWork
History Displays the work item history, for users who hold the Work-.AccessAuditTrail privilege. pxIconHistory
PrintStarts browser-based printing, which prints the current user form as displayed. This printout may not include desired fields and may use colors, fonts, and labels that are not desired in hard copy prints.pxIconPrint
Reopen Work Item Reopens a resolved work item, for users who hold the Work-.Reopen privilege. Runs the standard activity Work-.Reopen or your application override. pxIconReopenWorkItem
ReviewPresents the user form in review-only mode, allowing no updates.pxIconReview
SaveSaves the work item with Submit.pxIconSave
Show Flow Location Known as the Where-am-I? icon marks the location of the current assignment with an arrow. This icon appears only to users who hold the Perform privilege.
Note: If the harness is a New harness — one supporting the entry of new work items — do not include the Show Flow Location icon in most cases. A flow execution doesn't start until users submit a user form. If you do include this icon in a New harness, use a when condition rule to disable the icon at runtime unless a non-blank work item ID exists.
pxIconShowFlowLocation
Show Reopen Screen Shows the form in review mode but allows users to reopen a resolved work item. Available to users who hold the Work-.Reopen privilege. Runs the standard activity Work-.Reopen or your application override. pxIconShowReopenScreen
Spell Checker Enables spell-checking. See Enabling spell checking in user forms. pxIconSpellChecker
Update Redraws the form in update mode. Appears only for users who hold the Work-.Update privilege. Update mode allows changes to values that appear in sections other than the TAKE ACTION section.

This capability is not desirable in all applications, as it allows users to overwrite values entered previously, perhaps by other users.

The Apply button sends changed user inputs to the server, but does not commit these changes. The user must select and complete a flow action to save the changes. See Understanding transactions in flow executions.

pxIconUpdate

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us