Action Plans is open source software. We welcome your issue reports, ideas, documentation, code tweaks and all other participation.
Learn more.
Features:
Export and share your Action Plan Templates with other orgs.
Import Action Plan Templates.
Supports Task reminder times.
Action Plans Settings controls behavior around Chatter Notifications, actions when a Lead is converted, and default Task assignment behavior
Invocable Apex allows automatic Action Plan creation from a Template in Process Builder and Flow
Post Install Configuration
Getting started is easy. For each object, you need to add a button to the list view, add a button to the detail page. For Accounts, follow these steps:"
Update Action Plans Custom Settings
Change these setting by editing Action Plan Settings, and updating values at either the organization level, profile levels, or user levels.
Navigate to Setup > Develop > Custom Settings. Click on 'Manage' next to Action Plans Settings. Click the 'New' button near
'Default Organizational Level Value'. Check the values that you want to enable.
Enable Chatter Post places a post in the related record's Chatter Feed (if Chatter is enabled for that object). If unchecked, Action Plans does not
create a Feed Post.
Unassigned Task Defaults to Record Owner ensures that Action Plan Template tasks with a blank 'Assigned To' field go to the related record's
owner. If unchecked, tasks with a blank 'Assigned To' field are assigned to the running user. Tasks can be assigned to specific people on Action Plan
Templates, which overrides this setting.
Default Object on Lead Conversion specifies that if an Action Plan is related to a Lead, whether the Action Plan should be moved to the converted
Account, Contact, or Opportunity when the Lead is converted. The default is Contact.
Action Plans Business Hours ID and Use Business Hours are reserved for future functionality.
Weekends: Custom Metadata
Modify Custom Metadata Weekend Day to indicate which days of the week are the weekend and how many days to move a task forward or backwards to move it to
the end of the previous week or the start of the next week. This allows you to work with a different weekend, or to avoid assigning any task to be due on any specific
day of the week. All weekdays should have 0 in both numeric fields.
Update Your Page & Search Layout Configurations
Create Action Plans Buttons
For each object, you need to add a button to the list view, For Accounts, follow these steps:
Navigate to Setup > Object Manager > Account > Search Layouts for Salesforce Classic
Click on "Edit" from the menu near "List View."
Move the "Create Account Action Plans" button from "Available Buttons" to "Selected Buttons."
Note: the package includes a default "Action Plan Layout" for your reference. You do not need to use it.
Click on "Edit" near one of your standard Account Page Layouts.
Add "Action Plans" related list to the page.
Edit the properties of the related list by clicking the configuration button above it.
Expand "Buttons" section, clear the "New" checkbox and move "Create Account Action Plan" to the Selected buttons.
Update the fields in the related list to meet your needs. Recommended fields include Start Date, Action Plan Status, Action Plan Template, Plan Start Date.
Click "Save."
Repeat these steps for the other standard objects Action Plans supports: Contacts, Leads, Opportunities, etc.
Delete Action Plans Buttons
Follow this steps for Action Plan Object:
Navigate to Setup > Object Manager > Action Plan > Search Layouts.
Click on "Edit" near "List View."
Move the "Delete Action Plans" button from "Available Buttons" to "Selected Buttons."
Click "Save."
Task Layout
Optionally, add the "Action Plan Task" field to your Task page layout, but it should be Read-Only, as clearing this field will break the
ability to track Action Plan progress.
Security
Update Your Org-Wide Default Sharing Settings
Action Plans includes two shareable objects: Action Plan and Action Plan Template. You may configure your sharing settings in whatever way
works for your organization.
If you want anyone to be able to create and see plans and their templates, use Public Read/Write for Action Plan and Action Plan Template.
If you want anyone to be able to see Action Plans and Templates without being able to change them, select "Public Read Only."
If your Org-Wide Default sharing settings are set to Private for Action Plan or Action Plan Template, you may need to implement custom automation to share Action Plan
records with the appropriate people. You may do this via Apex sharing, or you may use other automation, to assign ownership of the Action Plan itself to the related
record owner or any desired user.
To use Action Plans, most users require access only to Tasks. They can be assigned Tasks without knowing that these Tasks are part of an Action Plan. Any
changes they make to a Task's Status will be reflected in the related Action Plan Task Template record automatically. No Permission Set is required.
Use Permission Sets For Security
Assign the appropriate Permission Set(s) to each user who will need to use Action Plans:
Action Plans Admin: Full permissions for Action Plans, Action Plan Templates, AP Tasks and APT Task Templates.
Action Plans Template Creator: Full permissions for Action Plan Templates and AP Template Tasks. No Action Plan access.
Action Plans Creator: Read, Create, Edit, Delete for Action Plans and AP Tasks. Read-only for Action Plan Templates and APT Task Templates.
Action Plans Import/Export: Access to export and import Action Plan Template records. View the appropriate button for export and tab for import.
Action Plans User: Read-only for Action Plans and AP Tasks. Edit permission for Tasks should be provided via the user's profile or other permission
sets.
Uses for each Permission Set:
Some users may require visibility into the Action Plans related to those Tasks. These users need the Action Plans User Permission Set. It gives Read-only
access to Action Plan.
Some users may need to create Action Plans from Templates but not edit the templates themselves. The Action Plans Creator Permission Set gives read-only
access to Action Plan Templates, and Read, Create, Edit, and Delete access to Action Plans.
Users who can create and edit Action Plan Templates require the Action Plans Template Creator Permission Set. This includes permission to Read, Create,
Edit, and Delete all Action Plan Templates only. It does not include any Action Plan or Task permissions. If these users require Action Plan access, other Permission
Sets should be used as well. A custom permission allows exporting of Action Plan Templates.
Intended as an add-on for Action Plans Template Creator, the Action Plans Import/Export permission set allows the viewing of the Export
button on Template detail pages and to the Import tab. The custom permission Action Plan Template Export allows exporting of Action Plan Templates and
associated tasks. Use this permission with care, as it is a potential security hole for your org's proprietary templates. This is a great way to move templates
from a Sandbox to Production org.
Action Plans Admin includes Modify All permissions for all four Action Plan objects (Action Plan, Action Plan Task Template, Action Plan Template, and
Action Plan Template Task Template). The custom permission allows exporting Action Plan Templates.
Note: The Apex used in Flows or via triggers does not require special permissions to run.
Using Action Plans with Custom Objects
Start Using an Object with Action Plans
Create the object and be sure to check "Track Activities" for the object attrributes
Create a lookup field from Action Plan to the object. Name the field the same as the object name. The field label can be anything.
As an example, if you have a custom object named MyObject__c, you must name the field on Action Plan MyObject__c
Add the field to the Related Objects fieldset on Action Plan.
The related object will now be available for selection when creating a new Action Plan and relating it to an object.
Add the following code to the object trigger in before delete and after undelete contexts (removing the
LabsActionPlans namespace if you're not using the managed package):
Don't forget to write a test class to cover the custom object trigger. If you're just going for coverage (not a best-practice!) just make a test method
inserting and then deleting a record. Unfortunately, the code in this package does not lend itself to easy creation of an Action Plan for a custom object... yet.
Adding a Create Custom Object Action Plan button to the Action Plan object
While Action Plans already overrides the New Action Plan action, the New button will show a new Action Plan screen, but will not allow adding an existing template.
(Perhaps this will be in a future release... safe harbor.) Create a custom button with the following format on the Action Plan object and add it to the related list on
the custom object page layout:
Navigate to Setup > Object Manager > Action Plan > Buttons, Links, and Actions > New Button or Link
Give it a label and name, such as "New MyObject Action Plan"
Display Type is List Button. Uncheck the list checkbox.
Use the following format for the button (removing the LabsActionPlans__ namespace if you're not using the managed package):
Be sure to remove the standard New button on the Action Plans related list and use this button instead.
Create Action Plans for multiple Custom Object records
Just as there is a button for Account list views to create multiple Action Plans, you can do the same for your custom object. Create a Visualforce page with the
following code:
Then create a list view button for that object and add it to your list views.
To Stop Using an Object with Action Plans
If you want, for example, not to allow relating Action Plans to Contracts, remove the Contract field from the Action Plan Related Objects fieldset. There is no
need to delete the field from the Action Plan object.
Create a Template
Now you're ready to create your first template. Navigate to the Action Plans Templates tab. Click on the "New Action Plan Template" button.
The template screen looks like this:
Name - Template Name.
Description - An explanation of how the template should be used.
Skip Weekends - Allows you to automatically reschedule a task that would fall on a weekend to either the day before or day after the weekend. When checked, a
picklist appears, allowing you to select before or after the weekend.
Action - Click "X" to eliminate a step in a template.
Subject - What the task is to do.
Task Dependency - The dependent task will only be created once the controlling task is completed.
Days After- This value determines the due date of the task.
For tasks with no dependency, the task's due date will be offset from the plan start date.
For tasks with a dependency, the due date will be offset from the expected due date of the task on which it depends.
Assigned To - Looks up to user. Leave blank if you want to assign the task dynamically. When assigning dynamically, the default behavior will be to assign the
task to the running user. You can also have the system assign it to the record owner by changing your Action Plan Settings. See "Post Install
Configuration" guide above.
Category - What type of activity.
Priority - Taken from Task priorities and Record Type (if applicable).
Email - Send a standard New Task email when checked. For Tasks depending on others, the email will be sent when the task is created.
Reminder - This check box will define the default behaviour for reminders when applying the template to create an Action plan .
If it's left unchecked, in the Action Plan Creation page the reminders will be initially disabled
If it's checked the reminders will be available.
User Reminder settings: Go Personal Setup > My Personal Information > Reminders, if the option "By default, set reminder on Tasks to:" is checked
then the selected time will be the default option for task template reminders.
User setting for Activity Object : Go App Setup> Feature Settings > Sales > Activity Settings, If "Enable Activity Reminders" is not checked,
then reminders column will not be displayed in the Action Plan creation page.
Comments - Comments supporting a task.
Add New Task - Adds an additional row to the tasks grid.
Save - Saves the template.
Task Record Types
If your org uses Task Record Types, you must specify which Record Type to use for all Tasks from each Action Plan and Template record. This will affect the Status
values available for each related Action Plan Task. This cannot be changed once an Action Plan or Template is created. Only one record type may be specified for all the
Tasks on that Action Plan or Template.
Create Action Plans for Several Accounts
Navigate to an Accounts list view. Select the Accounts for which you want to create Action Plans. Click on the "Create Account Action Plans" button.
Select the template you want to use by typing the name on the lookup and clicking on it.
Enter the information specific to this plan. Note that the Accounts you selected earlier are visible.
Save the Action Plan.
Note: Action Plan creation is handled by a queueable (asynchronous) process. It can take a couple of minutes to be able to view all created records.
Verify the Action Plan and the tasks.
Complete the first task on the Action Plan.
Note that the Action Plan is now in the correct related list and that this Account has one open activity and one closed activity. The third activity in the template
is dependent and will be created only when its controlling task is complete. (A Contact related list is shown here, but this applies equally to Accounts.)
Task notifications for Flow-created Action Plans
User Settings
To receive Task notifications if Send Email is selected on an Action Plan Task, ensure that users have been allowed to control receipt of Task notification
emails (this is active by default), and that they have allowed email notifications to be sent (this is also enabled by default). See
Salesforce H&T for more information.
Org Setting
The Send Email field on Action Plan Task must be checked to send a email notifications, and the setting
Allow Flow to send delegated task notifications on records created through Apex must also be enabled. Go to Settings > Feature Settings
> Sales > Activity Settings to check that box and allow email notifications to be sent via Flow-created Action Plans.
Action Plan Tasks
If the user has enabled task notification, then those will be sent when an Action Plan Task is created.
If the Action Plan Task is updated to a new owner, and if the Send Email box is NOT checked, the user may still receive a task notification if that is in
their personal settings.
If the box is checked, assuming that notifications are enabled for that user, the email will be sent.
Queues
Action Plan Tasks cannot be assigned to queues, so if the parent record is owned by a queue, each AP Task will be assigned to the running user. Tasks generated from
that Action Plan can be assigned to the queue by using a Flow to reassign the Tasks. Because the Invocable Apex returns a list of Action Plan Task IDs, the created
Tasks (which have a relationship to the Action Plan tasks) can be updated in that same flow, as they are created synchronously and can be queried immediately.
Alternatively, reassign Tasks to Queues any other way you'd like; it will not break Action Plans, and the Queue name will show on the Action Plan detail page.
Automate Action Plan Creation
Flow
Action Plans includes an Invocable Apex class that can be included in a Flow. The Record ID of the triggering record is required, as is the Id OR the Name of the
desired template. Days from trigger to start Action Plan is optional (and defaults to 0). The first task will be due the number of days (specified on the template)
from the start date. This date may fall on a weekend, though task due dates can be moved to avoid weekends if set on the template.
The Invocable Apex class returns the Salesforce IDs of all the created Action Plan Tasks, which can be used in the next Flow steps.
(Optional) Sample Action Plan Template for Account onboarding
Run the following:
sf apex run --file ./data/sample-data.apex
To use this Template with the included Flow, see the Create Action Plan From Template Apex Action in the
New Customer Onboarding Activities Flow
Create an Account and set Type to any value that starts with 'Customer'
Process Builder
It is recommended NOT to check the Recursion box when creating a Process Builder to work with Action Plans.
It is also recommended NOT to use Process Builder at all!
Apex
To call the invocable Apex from a Trigger or Apex class, adapt the following sample code:
UNMANAGED CODE
String apTemplateName;
ActionPlanTemplate__c apTemplate;
List<SObject> toInsert... // can use any object, such as Account, or the generic SObject class
List<ActionPlanCreateInvocable.CreateActionPlanRequest> requests = new List<ActionPlanCreateInvocable.CreateActionPlanRequest>();
for(SObject a : toInsert){
ActionPlanCreateInvocable.CreateActionPlanRequest req = new ActionPlanCreateInvocable.CreateActionPlanRequest();
req.templateNameOrID = apTemplate.Id;
req.relatedRecordID = a.Id;
req.daysToActionPlanStart = 0;
req.actionPlanName = a.Name + ' - Onboarding';
requests.add(req);
}
List<Id> resultIDs = ActionPlanCreateInvocable.makeActionPlanFromTemplate(requests);
MANAGED PACKAGE
String apTemplateName;
LabsActionPlans__ActionPlanTemplate__c apTemplate;
List<SObject> toInsert... // can use any object, such as Account, or the generic SObject class
List<LabsActionPlans.ActionPlanCreateInvocable.CreateActionPlanRequest> requests = new List<LabsActionPlans.ActionPlanCreateInvocable.CreateActionPlanRequest>();
for(SObject a : toInsert){
LabsActionPlans.ActionPlanCreateInvocable.CreateActionPlanRequest req = new LabsActionPlans.ActionPlanCreateInvocable.CreateActionPlanRequest();
req.templateNameOrID = apTemplateName;
req.relatedRecordID = a.Id;
req.daysToActionPlanStart = 1;
req.actionPlanName = a.Name + ' - Onboarding';
requests.add(req);
}
List<Id> resultIDs = LabsActionPlans.ActionPlanCreateInvocable.makeActionPlanFromTemplate(requests);
ActionPlanCreateInvocable.CreateActionPlanRequest class
Variables:
String templateNameOrID (required) Name is not unique, so ID is preferred
Id relatedRecordID (required) Must have a relationship field named the related record object name from Action Plan object
Integer daysToActionPlanStart (not required) Defaults to 0, the day the plan is created
String actionPlanName (not required) Give the Action Plan a custom name. If not specified, defaults to {Template Name} - {Parent Record Name}.
Share Your Templates and Discover Best Practices using Template Export and Template Import
Action Plans supports the sharing and discovery of best practices using Template Export and Template Import.
How to Share Your Template
Export is simple. Navigate to the Template you wish to export. Click on the "Export" button.
Export creates a simple XML file containing template header and task information. It also includes information about who created the template. Note: It does not
include user information or sensitive data about what objects you might use this template with.
If you are using Lightning Experience, the exported file is in your Files tab, in your private files library. If you are still using Salesforce Classic, it is in your
Documents tab, in your private documents folder.
Sharing the file is easy. Email the file to whomever you want to share it with. Do you want to share it with a broader audience? Email the file to Salesforce Labs at
labs@salesforce.com.
Best Practices: How to Import
Import is also simple. Navigate to the "Import Template" tab. Select the file you want to import using "Browse" and once you've found it click
on "Import Template."
(Optional) Sample Action Plan Template Import
This repository also includes sample Action Plan Template files, which you can import on the appropriate tab. You may download
New Customer Onboarding or
Trade Show Follow Up from GitHub, or you can find it in this
SFDX project in the data folder.
