{"id":168,"date":"2009-11-30T06:09:00","date_gmt":"2009-11-30T00:39:00","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=168"},"modified":"2009-11-30T06:09:00","modified_gmt":"2009-11-30T00:39:00","slug":"how-to-track-the-next-action-and-last-touch-dates-on-account","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2009\/11\/how-to-track-the-next-action-and-last-touch-dates-on-account\/","title":{"rendered":"How to Track the Next Action and Last Touch dates on Account"},"content":{"rendered":"

Quite often you need to monitor and have workflows designed based on the “Last Touch Date” or the “Next Action” date. While the former should reflect the last interaction made with the customer, the later is to keep track of the next upcoming interaction with the customer.
\nEnd users often believe the Modified date reflected on the Account form, is the “Last Touch Date”. Well, that is not true. The Modified date on the Account Form is only updated when any changes are made directly to any of the attributes on the account form. Even adding of a note to the account does not update the “Modified Date”. To track the true “Last Touch date”, you would require to write a custom plugin or perhaps a Workflow could do the job as well.
\nHow to track “Last Touch Date” using Workflow.<\/span><\/strong>
\nYou need to trap the create\/update\/status change events of all the activities that you need to track for an account. Assuming that we would set the regarding to Account for each activity that we create.
\n1. New Worklow – Set the entity as Appointment – Event Create, Update and Status change
\n\"\"<\/a> 2. Add step to Update entity as shown as below screenshot.<\/p>\n

\"\"<\/a> 3. Choose Regarding(Account) as shown as below screenshot. <\/p>\n
\"\"<\/a>
\n4. Select custom date attribute for tracking “Last touch” set date = Workflow execution as shown in the below screenshot. <\/p>\n
\"\"<\/a><\/p>\n
How to track “Last Touch Date”\/Next Action Date using Plugins.<\/span><\/strong>You need to write Plugin to trap the create\/update\/chnage status events of the activities. In the Post event, read the account associated with the activity and update the “Last Touch Date” with today’s date.
\nFor the next action date, in each of these events, you need to read the account associated with the activity. Using the RollupActivitiesforAccount \u201cTargetRollupActivityPointerByAccount\u201d you can get the next due activity and update the “Next Action Date” to this date.\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Quite often you need to monitor and have workflows designed based on the “Last Touch Date” or the “Next Action” date. While the former should reflect the last interaction made with the customer, the later is to keep track of the next upcoming interaction with the customer. End users often believe the Modified date reflected\u2026 Read More: How to Track the Next Action and Last Touch dates\u2026 »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,67],"tags":[82,982,1723],"class_list":["post-168","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm","category-workflows","tag-accounts","tag-last-action","tag-track-next-action"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t