In Summer ’19, Action Plans expanded object support to more standard and custom objects.
If your API implementation of Action Plans references TargetId and assumes it’s an account record, you must update your code.
Required Editions
Available in: Lightning Experience
Available in: Automotive Cloud, Consumer Goods Cloud, Education Cloud, Financial
Services Cloud, Government Cloud with Lightning Scheduler, Health Cloud, Manufacturing Cloud,
Nonprofit Cloud, and Public Sector Solutions. View edition
availability.
Before API version 46, Action Plans only supported the Account object. If you
implemented Action Plans using automation, TargetId was the
ID of the Account record that relates to an action plan.
Starting in API version 46, Action Plans supports multiple target objects,
including Account, Campaign, Case, Contact, Contract, Lead, Opportunity, and more. You can also
use Action Plans with custom objects that have activities enabled. This enhancement means that
TargetId is now a polymorphic field key. Use TargetEntityType to determine the type of object the action plan
template is based on. Then use TargetId to look up the
record in the appropriate object’s table.
Before version 47, Action Plan Templates could only contain task items. Starting in
API version 47, Action Plan Templates can contain a mix of task, document checklist, and
assessment task items. Task triggers that use API version 46 or less can fail if triggered by an
Action Plan Template that contains different types of items. Solve this by upgrading task
triggers to API version 47 or greater, or making sure that Action Plan Templates only contain one
type of item.
You can’t customize the ActionPlanTemplate object. Any updates to the object
fields via the UI are applicable only to the local org and can’t be retrieved by using Metadata
APIs.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.