Action Plans are made of a series of steps (activities) and each step can provide a particular type of action that a user can perform while working on that particular step. Action Steps can be further configured to enforce certain behaviour when the user is working on it. Action Plans can be a useful tool in preparing a business plan and tie it with existing objects in ConcourseSuite CRM. Today Action Plans can be tied with 'Accounts' or 'Tickets', but can easily be extended to associate with other objects. For more technical information on Action Plans, see Action Plan Development.

Here we describe how one can add Action Plan support for Leads module. A developer needs to perform the following changes to support Action Plans.

• Admin support for Leads Action Plans
• Action Plan support in the Leads module

Admin Module: Leads Action Plans

When the Admin navigates to ‘Configure Modules > Leads’ a new configuration item ‘Action Plan Editor’ should be displayed.
When the admin clicks on ‘Action Plan Editor’ the ‘Leads > Action Plan Editors’ page needs to be displayed. The admin can edit the action plans that are associated with Leads. Then the admin can proceed to add and configure new Action Plans and review existing ones similar to ‘Admin > Configure Modules > Accounts > Action Plan Editors > Action Plans’

• Add a new permission sales-leads-action-plans for Lead Action Plans with VAED attributes. Add the permission under “Leads” in permissions_en_US.xml. Provide a BSH upgrade script that will insert this permission into the database.

• Set the ‘Leads’ module to have action plans by providing ‘actionPlans="true"’ attribute for category ‘Leads’ in permissions_en_US.xml. Provide a BSH script which will enable existing systems to have Lead Action Plans.

• Specify a new Constant in ActionPlan.java for LEADS = 711071244 as ‘leads’. Add a <record> element for ‘action_plan_constants’ in lookuplists_en_US.xml with ‘leads’ data. Provide a BSH script similar to 2005-09-12-script01-partha.bsh to add this record to an existing system based on the dictionary available.

• When the user is working through an action plan, each step in the plan can have a particular type of user action tied to it. There is a predefined pool of available user actions that can be used while configuring an action step. The developer needs to determine the subset of these actions that are visible to the admin while configuring Lead Action Plans & Steps. Provide a BSH script which defines the various actions available while configuring Action Steps for Lead Action Plans. Refer to 2005-09-16-script01-partha.bsh. The Lead step actions will be the subset that is available for Account Action Plans. So the section under Accounts Mappings in the bsh should be provided.

• The LEADS constant must be used for action_plan.link_object_id when adding action plan templates for Leads in the Admin section. When adding action plans for a particular Lead, the action_plan_work.link_module_id and action_item_work.link_module_id should be set using the LEADS constant.

Leads Module: Action Plan Support

When the user navigates to the Leads module and selects a particular Lead object to review its details, based on the user's role there are several side-tabs that are visible. If 'Action Plans' are visible to the user he can add any number of action plans based on the action plan templates that have been configured by the admin.

• Include the ‘sales-leads-action-plans’ permission for ‘actionPlans’ submenu under ‘leads’ container in cfs-container_menus.xml.

• Provide the action commands ‘View’, ‘Add’, ‘Insert’ and ‘Details’ in SalesActionPlans.java. Please refer to AccountActionPlans.java to provide similar action commands. Use action command chaining to use common functionality in ActionPlans.java.

• The Leads Action Plan list page should display a drop-down menu for each record with the following actions:
• View Action Plan
• Reassign
• Review Notes
• Archive
• Delete