SugarCRM SupportProduct GuidesSugar Versions11.1 Sugar11.1 Sugar EnterpriseSugar Enterprise 11.1 Administration GuideDeveloper ToolsStudioAction Buttons
This release is only available for SugarCloud customers.

Action Buttons

Overview

Action Buttons are custom buttons that can be added to records to enable users to perform quick actions directly from records such as sending an email, creating or editing a related record, and opening an external web page. Action Buttons are implemented as a field type in Studio and are easily extended using Sugar Logic and SugarBPM.

Understanding Action Buttons

Action Buttons are powerful tools that provide your users with shortcuts to perform tasks within records that otherwise would require leaving the record. The benefit of using Action Buttons is that they support an efficient workflow, giving users the tools they need to perform their work directly where they need it. Action Buttons look like standard Sugar action buttons in record views and can be displayed in records, their headers, or both. Buttons are easily configurable by style (color, labels, icons) and function (direct action or calculated) and their availability in records can be made dependent on specific conditions as well as role or team-based permissions. 

For examples of how Action Buttons can be used in records, please refer to the Action Button Example Use Cases section. 

Compatibility

Action Buttons are Sugar fields and are subject to access control rules that may be set via team membership, user type, and role restrictions. For more information on teams and roles, please refer to the Team Management and Role Management documentation in the Administration Guide.

The following limitations apply to Action Buttons:

  • Action Buttons can only be used on Record View dashlets and a module's record view and preview layouts and will therefore not be available to select on other layouts in Studio.
  • Action Buttons cannot be accessed by users on the Sugar Mobile app.
  • Action Buttons cannot be accessed from within the SugarLive console.
  • Action Buttons are not available for Sugar Professional.

Note: If you previously installed the Custom Buttons package included in the wTools bundle, please refer to the Understanding Action Buttons vs wTools Custom Buttons article to help you determine if you should re-create your Action Buttons directly in Studio in your Sugar instance.

Configuring Action Buttons

Administrators can place an Action Button on a record by creating and configuring a new field in Studio with a Data Type of "ActionButton" for the record's module and then adding that field to the record view layout. The "ActionButton" type field requires additional configuration after the field is created. This section describes the configuration options available for Action Buttons. To see how Action Buttons are displayed in records, please refer to the User Interface documentation in the Application Guide.

A single ActionButton field may be configured to show one or more buttons. When one field contains more than one button, the buttons can be shown either side-by-side in the singular field's area or as an Actions-menu style button with a dropdown list using the display settings in the Design panel. If you would like to have more granular control over access and placement of multiple buttons within a module, consider creating them as separate fields so that they can be managed independently. For more information, refer to the Working With Multiple Buttons section.

Note: You can only configure custom Action Buttons as described in this section; you cannot configure the standard Sugar action buttons or module Actions menus.

To configure Action Buttons, click "Configure Buttons" at the bottom of the field definition when creating the field:
studio configure button

The button configuration drawer opens:

studio buttonconfigdrawer 

The configuration drawer includes the following sections:

  • Header: A tabbed view of all buttons included in the current field
  • Properties: Options like the button's label, icon, color, and dependencies
  • Design: Additional display options including how to display multiple buttons within a field
  • Action: The action that will occur when the button is clicked by a user

Refer to the following sections for information on configuring each of these areas.

The Header section across the top of the drawer contains tabs that represent each button for the current field. The Properties and Action display for the selected tab. When there are multiple buttons for the field, display settings in the Design panel apply to all buttons. 

Properties

Define basic visual options in the Properties section of the Action Button configuration drawer. When there are multiple buttons for the field, these settings only apply to the button defined on the active tab in the header.

  • Label: The text to be displayed on the button. You do not need to include a label; you may want to only include an icon (see "Show Icon" below).
  • Show Label: When enabled, the text identified in the Label field will be displayed on the button. When not selected, the button will be blank or display only the icon if the "Show Icon" option is selected.
  • Color Scheme: The button color. Select an option from the dropdown list and view the results in the Preview section of the Design panel.
  • Dependent: When enabled, the button will only display in records when the conditions defined in the Formula field are met.
    • Formula: Conditions that define the criteria for displaying the button on records. Please refer to the Sugar Logic documentation for more information.
  • Tooltip: Text to be displayed when a user hovers over the button.
  • Show Icon: When enabled, the icon identified in the Icon field below will display on the button. Refer to the Preview area of the Design panel to see how the icon will appear on the button.
  • Icon: Filename of the icon to be displayed on the button. The Show Icon field must be enabled for the icon to be displayed. Refer to the Preview area of the Design panel to see how the icon will appear on the button.

Design

Define additional display options for the Action Button and view the button display in the Design panel. When there are multiple buttons for the field, these settings apply to the entire group of buttons.

  • Preview: View-only section that shows you the button appearance based on the current settings.
  • Type: The Action Button style
    • Dropdown: When multiple buttons are configured for the same field, the first button displays with a dropdown list that contains the other button labels.
      dropdown
    • Button: A single button.
    • Button Group: When multiple buttons are configured for the same field, they are displayed in the record together with no space between them.
      buttongroup
  • Show Field Label in Record Layout: When enabled, displays the text identified in the Action Button Field Label above or next to the button on records (the location is determined by the user preference setting). This is not the label that is displayed on the button (see "Show Label" in the Properties section).
    button fieldlabel
  • Show in Record Header: When enabled, displays the button in the record header adjacent to the record name. If the field is also added to the record view layout, users will see the button in both places. If this option is not enabled, then the button must be added to the record view layout in Studio.
  • Hide on Edit: When enabled, the button will be hidden when the record is in Edit mode.
  • Size: Set the button's display size (Default, Small, Large). Refer to the Preview area after making a selection to compare sizes.

Action

In the Action section, define the action that will occur when a user engages the Action Button. 

Action Description Fields
Assign Record Assigns the record to the designated user. Assign To: Select the user to whom the record should be assigned.
Compose Email Enables users to quickly compose an email using an email template. When the button is engaged, the configured email client is opened with the selected email template and designated recipients. 
  • Use PMSE: When enabled, the available SugarBPM Process Email Templates will be displayed in the Template list below. The templates available are those that were created with the target module where you are creating the field (e.g. when creating an Action Button field in the Contacts module, only the Process Email Template records with a "Target Module" set to Contacts will be displayed.)
  • Template: Name of the standard email template or SugarBPM Process Email Template to be used to compose the email.
  • Email To: Conditions that define the email recipients. Please refer to the Sugar Logic documentation for more information.
Create Record Enables users to quickly create records in other modules from the current record.
  • Module: Name of the Sugar module in which the record will be created.
  • Auto Create: When enabled, Sugar will create and save a new record in the module identified above. If this option is not enabled, then the user must manually save the newly created record after engaging the button.
  • Preset: The field for which you want to set a value in the newly created record. After selecting the field from the dropdown list, a text box displays where you can identify the value or set a calculated value using Sugar Logic.
  • Link: When enabled, the newly created record will be related to the record from which the Action Button was pressed (i.e. the parent record). 
  • Copy Parent Values: This option populates fields in the newly created record with the values from matching fields in the parent record.
  • Preset From Parent: The field in the newly created record to be populated with the value from the parent record. After selecting the field from the dropdown list, a text box displays where you can select the field name from the parent record from which the value will be copied.
Open URL Opens a URL in a new browser window. 
  • Calculated: When enabled, the URL to be opened will be constructed based on the conditions identified. Please refer to the Sugar Logic documentation for more information.
  • URL: Direct URL to be opened in a new browser window.
Run Report Provides a shortcut to run reports from a record. Run Report: Name of the Sugar report to be run when the button is engaged.
Update Record Provides a shortcut to update specific fields in the current record. 
  • Fields: Name of the field in the current record to be updated. After selecting the field from the dropdown list, a text box displays where you can identify the value or set a calculated value using Sugar Logic.
  • Auto Save: When selected, the updated record is automatically saved after the user engages the button. If this option is not enabled, then the user must manually save the updated record after engaging the button.

Working with Multiple Buttons

Several buttons can be shown within the same field. This is useful for grouping multiple shortcuts that are related to the same workflow within a module.

Note: Plan the order in which you want multiple buttons to appear in records before configuring. The order of the buttons in the record matches the order in which the buttons are designed and cannot be changed. 

To create additional buttons for the current field, click the plus icon in the header:
actionbutton1

A new tab opens to define the new button and the button is added to the Preview display on the right.
newbutton props

Note: If buttons exceed the horizontal space in a record header, then the button type is automatically converted to a dropdown button.

Displaying Action Buttons in Records

As with all field types, you need to add the Action Button to the record view layout before it will display in records, unless you only want the buttons to display in the record header, which can be configured using the display settings in the Design panel. Please refer to the Studio documentation for more information on adding fields to record views.

Action Button Example Use Cases

There are many use cases for Action Buttons depending on the module and your own workflows. The following are just a few examples of how Action Buttons can be utilized. For details on how to implement these examples, please refer to the Creating an Action Button article.

Escalate a Case

Provide your Support team with a one-step method of case escalation with an Action Button that updates the Priority field to "High" and the Assigned To field to the manager. While you can also define a Sugar BPM process for case escalation, utilizing an Action Button in this way does not require BPM knowledge and allows your Support reps to instantly escalate a case while engaged with a customer on the phone.
caseescalate example

Reject a Lead

Enable your Sales team to quickly update a lead record to reject the lead, assigning the record to the regional sales manager, setting the status to "Dead", and adding "no purchase potential" to the Description field. 

killlead1 killlead2

Add a Call Note to an Opportunity

Using an Action Button in an opportunity record can provide quick creation of calls associated with the opportunity. For example, automatically create a call record with the Status field set to "Held", Direction set to "Outbound", and Description populated with the name of the opportunity.
callnote buttonexample

Access Supporting Documents from a Quote

Use an Action Button to provide a link to external systems that contain supporting documentation. For example, link to design documents located in a corporate intranet from a quote record to provide user access to all information directly where it is needed.
sharepoint link buttonexample

Email a Team

Including an email Action Button can be a time saver in any module. This type of Action Button enables users to quickly send email to a predetermined recipient list using an email template or process email template.
email buttonexample

Including an Action Button that links to a specific map location (e.g. https://google.com/maps?q={primary account address}) can provide your Sales team with directions to the account's location in one click.
map button example

Last modified: 2021-08-18 21:11:46