Customizing the Email Action

The Email action in Case Feed lets support agents connect with customers via email. With the apex:emailPublisher component, you can:

  • Customize the dimensions of the Email action.
  • Define defaults and visibility for fields.
  • Define the visibility and label of the send button.
  • Define onSubmit functionality.
  • Support email templates and attachments in the action.

The apex:emailPublisher component closes a task in Open Activities created by Email-to-Case inbound email.

Attribute NameAttribute TypeDescriptionRequired?API VersionAccess
autoCollapseBodyBooleanA Boolean value that specifies whether the email body collapses to a small height when it is empty. 25.0
bccVisibilityStringThe visibility of the BCC field can be ‘editable’, ‘editableWithLookup’, ‘readOnly’, or ‘hidden’. 25.0
ccVisibilityStringThe visibility of the CC field can be ‘editable’, ‘editableWithLookup’, ‘readOnly’, or ‘hidden’. 25.0
emailBodyStringThe default text value of the email body. 25.0
emailBodyFormatStringThe format of the email body can be ‘text’, ‘HTML’, or ‘textAndHTML’. 25.0
emailBodyHeightStringThe height of the email body in em. 25.0
enableQuickTextBooleanA Boolean value that specifies whether the Quick Text autocomplete functionality is available in the action. 25.0
entityIdidEntity ID of the record for which to display the Email action. In the current version, only Case record ids are supported.Yes25.0
expandableHeaderBooleanA Boolean value that specifies whether the header is expandable or fixed. 25.0
fromAddressesStringA restricted set of from addresses. 25.0
fromVisibilityStringThe visibility of the From field can be ‘selectable’ or ‘hidden’. 25.0
idStringAn identifier that allows the component to be referenced by other components on the page. 25.0Global
onSubmitFailureStringThe JavaScript invoked if the email is not successfully sent. 25.0
onSubmitSuccessStringThe JavaScript invoked if the email is successfully sent. 25.0
renderedBooleanA Boolean value that specifies whether the component is rendered on the page. If not specified, this value defaults to true. 25.0Global
reRenderObjectThe ID of one or more components that are redrawn when the email is successfully sent. This value can be a single ID, a comma-separated list of IDs, or a merge field expression for a list or collection of IDs. 25.0
sendButtonNameStringThe name of the send button in the Email action. 25.0
showAdditionalFieldsBooleanA Boolean value that specifies whether the additional fields defined in the action layout are displayed. 25.0
showAttachmentsBooleanA Boolean value that specifies whether the attachment selector is displayed. 25.0
showSendButtonBooleanA Boolean value that specifies whether the send button is displayed. 25.0
showTemplatesBooleanA Boolean value that specifies whether the template selector is displayed. 25.0
subjectStringThe default value of the Subject. 25.0
subjectVisibilityStringThe visibility of the Subject field can be ‘editable’, ‘readOnly’, or ‘hidden’. 25.0
submitFunctionNameStringThe name of a function that can be called from JavaScript to send the email. 25.0
titleStringThe title displayed in the Email action header. 25.0
toAddressesStringThe default value of the To field. 25.0
toVisibilityStringThe visibility of the To field can be ‘editable’, ‘editableWithLookup’, ‘readOnly’, or ‘hidden’. 25.0
widthStringThe width of the action in pixels (px) or percentage (%). 25.0

Cirrus Computers, a multinational hardware company with technical support agents in 10 support centers throughout the world, wanted to customize the Email action to increase standardization in outgoing messages and to limit the fields agents could edit.

Cirrus used the apex:emailPublisher component to create an Email action that:

  • Has read-only To and Subject fields.
  • Pre-populates those fields, ensuring consistency and increasing agents’ efficiency when writing email messages.

Case Feed Email publisher example