Buttons

Administrators can create buttons to add functionality and navigation in Community Hub. Administrators can position buttons to suit their needs, and can designate whether the button represents a primary or secondary user action. The behavior of a button can be customized with development effort by associating it with an Apex class. The Apex class can control all button attributes as well as when a button is displayed and whether it is enabled.

Simple Buttons

Buttons in their simplest form are used to provide constituents the ability to navigate within Community Hub with ease. Buttons display text provided by a custom label, and will navigate the constituents to a designated URL when clicked.

Advanced Buttons

Building on the simple functionality of a button, more advanced buttons are associated with an Apex class which can control any button attribute.

For example, Administrators can make a button:

• Enabled or disabled so constituents can only take appropriate actions
• Display only when certain conditions are met so constituents only see the button when appropriate
• Reveal a menu of options so constituents can choose from multiple actions
• Run an autolaunched flow so constituents can initiate an automated process

Advanced buttons are used in Community Hub to perform various tasks throughout a constituent's experience.

Button Messages

Working in tandem with the Cookie Message Card Type, you can specify a label to display once a page is successfully submitted after a button is clicked. The success message can display on the same page, or another page depending on the behavior of the button.

To give your constituents context sensitive details in a message, you can use the same expression language as formulas to designate which field value(s) should display, and where in the custom label Value.

When specifying fields to include in the message, remember you can only use those fields that are returned by the data source used on your button and that you need to call out the object on which the field is located.

Here is an example of a message displayed after a constituent removes an affiliation. It displays the name of the individual or company for which they removed the affiliation and the name of their company.

The custom label Value of:

Got it, thanks. You removed {!nu__Affiliation__c.nu__Account__r.Name} from the roster for: {!nu__Affiliation__c.nu__ParentAccount__r.Name}.

Displays like this:

Got it, thanks. You removed Joshua Barker from the roster for: NimbleUser.

Button User Actions

Buttons can be positioned in the containing card in different ways to provide ideal placement. This also allows multiple buttons to be placed on a card using complimentary positions. Finally, buttons can be configured to act as a primary or secondary action to the user. Primary and secondary actions have no effect on how the button behaves, but are used to help constituents distinguish how to progress through a process or interaction or to exit out of it.

A primary action is one that allows constituents to move forward past a given page or complete a process. The Submit and Next buttons are good examples of primary actions.

A secondary action is one that allows constituents to move backward in a process or retract information they may have entered or options they've selected. The Cancel button is a good example of a secondary action.

Customize Buttons

Administrators use Button Configuration to configure Community Hub buttons. Administrators can:

• View a button
• Create a button
• Edit a button
• Clone a button
• Add a button to a card
• Change the location of a button
• Change the user action of a button
• Set whether a button opens a page in the same browser tab or in a new one
• Change the Apex class that controls the behavior of a button
• Change the label displayed upon successful submission of a button