Force.com Platform Fundamentals

Preface
Introducing the Force.com Platform
About the Sample Recruiting App
Reviewing Database Concepts
Building a Simple App
Enhancing the Simple App with Advanced Fields, Data Validation, and Page Layouts
Expanding the Simple App Using Relationships
Securing and Sharing Data
Collaborating with Chatter
Using Custom Workflow and Approval Processes
Introducing Workflow
Workflow in Our Recruiting App
Creating Workflow Rules That Assign Tasks
Try It Out: Create the “Send Rejection Letter” Workflow Rule
Try It Out: Create the “Send Rejection Letter” Workflow Task
Try It Out: Create the “Extend an Offer” Workflow Rule and Task
Look at What We've Done
Creating a Workflow Rule That Updates Fields
Creating a Workflow Rule That Sends Email Alerts
Introducing Approvals
Summing Up
Analyzing Data with Reports and Dashboards
Moving Beyond Point-and-Click App Development
Learning More
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Try It Out: Create the “Send Rejection Letter” Workflow Task

The Specify Workflow Actions step of the workflow wizard allows you to specify which actions, such as tasks, field updates, and email alerts, should occur when the condition of our workflow rule is met.

Specifying Workflow Actions Step 3 of the Edit Workflow Rule - Send Rejection Letter wizard with the Immediate and Time-Dependent Workflow Actions sections highlighted

You can either define actions that occur immediately after the condition is met, or you can define actions that occur before or after a certain amount of time has elapsed (for example, seven days before the value of the Hire By field, or three days after the workflow rule is triggered). We'll talk more about these time-dependent workflow actions a little later. For now, we just need to define a single workflow task that executes as soon as our rule criteria is met.

  1. In the Immediate Workflow Actions area, click Add Workflow Action and select New Task.

Did you notice that the Object field is already filled in with Job Application? Here's where we saved ourselves a couple of clicks—if we'd started building our workflow task before our workflow rule, we would have needed to specify the object with which the task would be associated. That's because, like workflow rules, workflow actions need to be associated with a single object.

In this case, we got to skip a page because the object with which a workflow action is associated must match the object of a workflow rule that uses it. For example, if we had a workflow rule associated with the Candidate object, any action that's triggered by our candidate workflow rule must also be associated with the Candidate object. Because we started building our “Send Rejection Letter” workflow task in the wizard right after defining our “Send Rejection Letter” workflow rule, the platform knew that the object associated with our task had to match the rule that we'd already built. That's why our new workflow task is already associated with the Job Application object.

The rest of the fields on this edit page make up the template for any “Send Rejection Letter” tasks that our workflow rule will generate.
  1. Next to the Assigned To field, click the lookup icon (Lookup icon).
Here we can choose the assignee of the task either by specifying a particular user, role, or the owner of the job application record that triggered the workflow rule in the first place. Since recruiters always own the job application records of the positions that they're responsible for, and recruiters are responsible for sending rejection letters at Universal Containers, let's select the record owner.
  1. In the Type drop-down list, choose Owner.
  2. Click Job Application Owner.

If you thought that choosing the Recruiter role for the Assigned To field might have been another valid option, be careful. If the assignee of a workflow task is a role that contains more than one assigned user, the person who triggered the rule will become the task assignee instead. For this reason, you never want to assign workflow tasks to roles unless you're sure that only one user will ever be assigned to them at a time.

Warning

The rest of the workflow task fields are easy.
  1. In the Subject text box, enter Send Rejection Letter.
  2. In the Due Date drop-down lists, choose Rule Trigger Date plus 2 days.

This Due Date setting will give our recruiters two days to notify the candidate after they're first assigned the task.

  1. In the Status drop-down list, choose Not Started.
  2. In the Priority drop-down list, choose High.

The Notify Assignee checkbox allows us to send an email to the assignee as soon as the task is created by the workflow rule. This ensures that the assignee knows about the task without having to log in to the application on a regular basis, so let's select it. (This option is unavailable when user control over task assignment notifications is enabled.)

  1. Click Save.
  2. Click Done.
Creating the “Send Rejection Letter” Workflow Task The Workflow Task - New page with the Configure Task section displayed and the Edit Workflow Task > Due Date field set to the Rule Trigger Date plus 2 days

At this point, we finally get to see the detail page for the workflow rule that we just created. It includes the workflow rule criteria and a list of the associated actions. The only thing that remains to be done is to activate the rule.

  1. Click Activate.

All done! We've just created our first workflow rule and task. You'll find that the remaining workflow actions all operate in a very similar way, so we'll speed through the rest of them, focusing just on the fields and options that are unique to each.