PatronManager Help

Understanding Workflow Part 4: Actions

Updated on

Use this link to share with your colleagues:

Understanding Workflow Part 4: Actions: https://help.pm.leapevent.tech/a/829739

Workflow is an older version of automation that Salesforce is phasing out. These instructions are still available to you for updating existing Workflows, but new automation should be built with Process Builder or Flow.

Workflow rules are used in PatronManager to automate updates or notifications and optimize efficiency! There are four main parts of a workflow rule:

  1. Object ("what")
  2. Evaluation Criteria ("when")
  3. Rule Criteria ("why")
  4. Actions ("what now?")

This article will look at the fourth and final part of a workflow rule: actions. This is the "what now?" of the workflow.

Workflow falls under Salesforce Administration and is therefore outside the scope of PatronManager support services.

Let's revisit our workflow rule core questions from Part 1:

  1. What action am I trying to trigger?
  2. What record does the qualifying criteria for this action live on?

When establishing workflow actions, we're interested in the answer to question #1

You'll mostly work with these 3 action types:

You'll mostly be working with these 3 action types:

Click below for details on how to use each of these commonly-used workflow actions:

1. New Task
1. New Task
  1. Assigned To: Assign the task to a single user (make another task action if it needs to be assigned to more than one user in your organization)
  2. Subject: Give the task a subject line
  3. Unique Name: this will auto-fill based on subject
  4. Due Date: Add a due date for the task based on date fields on the primary object, or on the date the rule was triggered (most common)
  5. Status: Set the initial status for the task
  6. Priority: Establish the initial priority for the task
  7. Comments: Add any description or comments you find necessary - the task will be generated on the record to which it pertains
2. New Email Alert
2. New Email Alert
  1. Description: Describe the email alert
  2. Unique Name: This auto-fills from the description
  3. Object: This was selected in Part 1 of the workflow rule
  4. Email Template: this must be written before the Email Alert is created. See following step!
  5. Recipient Type: You can send the email alert to users in your database, or to any email field on the record from which the workflow is triggered. You can also enter up to 5 additional email addresses to be notified below
  6. From Email Address: Send the email alert from your email address or from alternate email addresses that you have configured in My Settings or in Organization-Wide Email Addresses

Email Template used for an Email Alert

Email Template used for an Email Alert

Go to Setup> Administer> Communication Templates> Email Templates to make a new email template.

  1. Folder: Choose the folder your template is filed under
  2. Email Template Name: Name the template
  3. Available for Use: Mark it as Available for Use (not checked by default)
  4. Plain Text Preview: Preview types (Plain text, HTML) depend on the template type selected during template creation process
  5. Body of email: This can include merge fields from the record the workflow is triggered from. If you include the Detail Link field on the object selected on Part 1 of the workflow, the email template will include a link to the record in question (recommended)
3. New Field Update

Example 1: Update a text field with a formula value

Example 1: Update a text field with a formula value
  1. Name: Name the field update
  2. Unique Name: This auto fills based on Name
  3. Description: Add an optional description of the field update
  4. Object: this was selected in Part 1 of the workflow rule setup
  5. Field to Update: Choose which field is updating on the record that has triggered the workflow rule
  6. Text Options: Specify the value with a formula using the Formula Editor

In this example, we'll update the Donation Name field based on the record type of the donation (this criteria would have been defined in Part 3).

Example 2: Update a picklist field

Example 2: Update a picklist field
  1. Field to Update: Choose the field you want to update
  2. Picklist Options: Specify which picklist value should result from the field update

In this example, we'll build a workflow rule that looks at donations from a current Board member and update the Type field on the Donation to "Board".

Time-Dependent Workflow Actions

Time-dependent actions are executed at a specific time (units in days and/or hours), such as ten days before a donation record’s close date. When that specific time passes, the workflow rule re-evaluates the record to make sure that it still meets the rule criteria. If the record does, the workflow rule executes those actions.

Click Add Time Trigger to define when the action should be executed.

Click Add Time Trigger to define when the action should be executed.

In this example, the Development Director wants a task 7 days before a Board Member's pledge is due.

In this example, the Development Director wants a task 7 days before a Board Member's pledge is due.

Define the action

Define the action

Configure your task, then save.

Configure your task, then save.

Want to learn more about Time-Dependent Workflow Actions?

Previous Article Understanding Workflow Part 3: Rule Criteria
Next Article Relative Date Values
Still Need Help? Continue to the Client Community