3. Select RIQ Field Visits as the module, enter a rule name and click "Next".

4. Set the workflow to be triggered whenever a record is updated via a specific field. The workflow needs to be triggered every time the field "Check-out Time" is modified to not-empty. Set the workflow rule to be applied for "All RIQ Field Visits" that matches the said condition.

5. Choose "Function" in the 'Insert Action' field and click "Configure Function".

6. In the following page, a custom function is displayed. Edit it and add the below arguments and map it accordingly.

1. Int recordID = #RIQ Field Visits - RIQ Field Visit Id

2. Int plannedVisitOrder = #RIQ Field Visits - Planned Visit Order
   

3. Int routeID = #Lookup:RIQ Route Name - RIQ Route Id
   

7. Within the function, copy and paste the below snippet of code. This code checks and finds the email field of the record which triggered the workflow.

1. //Arguments:
2. // Int recordID = #RIQ Field Visits - RIQ Field Visit Id
3. // Int plannedVisitOrder = #RIQ Field Visits - Planned Visit Order
4. // Int routeID = #Lookup:RIQ Route Name - RIQ Route Id
5. 
   
6. // Constants
7. riqFVModApiName = "zrouteiqzcrm__RIQ_Field_Visits";
8. riqPlanVisitOrder = "zrouteiqzcrm__Planned_Visit_Order";
9. riqRouteName = "zrouteiqzcrm__RIQ_Route_Name";
10. riqAssociatedModApiName = "zrouteiqzcrm__Associated_Record_Module_API_Name";
11. riqAssociatedRecID = "zrouteiqzcrm__Associated_Record_ID";
12. // Add all RouteIQ integrated module's API name as keys, and respective field API names as values
13. crmModVsField = Collection("Leads":"Email","Events":"Email","Contacts":"Email","Accounts":"Email","Auto_Route_Creation":"Email");
14. //Global Variable with the next stop's visit order as plus one
15. plannedVisitOrderPlusOne = plannedVisitOrder + 1;
16. plannedVisitOrderPlusOneAsString = plannedVisitOrderPlusOne.toString();
17. // Getting all Stop Details with the same Route ID and the planned order as plus one
18. recordSearchCrt = "(" + riqRouteName + ":equals:" + routeID + ") and (" + riqPlanVisitOrder + ":equals:" + plannedVisitOrderPlusOne + ")";
19. nextStopDetails = zoho.crm.searchRecords(riqFVModApiName,recordSearchCrt);
20. nextStopDetails = nextStopDetails.get(0);
21. //Checking if there's a next stop or not
22. if(nextStopDetails.size() == 0)
23. {
24. info "No Next Stop";
25. }
26. else
27. {
28. //Getting next stop's associated record details
29. nextStopModuleAPIName = nextStopDetails.get(riqAssociatedModApiName);
30. nextStopAssociatedRecordID = nextStopDetails.getJSON(riqAssociatedRecID);
31. //Getting next stop's record details
32. if(!nextStopAssociatedRecordID.isNull())
33. {
34. nextStopRecordDetails = zoho.crm.getRecordById(nextStopModuleAPIName,nextStopAssociatedRecordID);
35. if(!nextStopRecordDetails.isNull())
36. {
37. info nextStopRecordDetails;
38. nextStopEmail = crmModVsField.get(nextStopModuleAPIName);
39. //Checking the module, and getting the email value from email field
40. if(!nextStopEmail.isNull())
41. {
42. //Type your mail logic here
43. info nextStopRecordDetails.get(nextStopEmail);
44. }
45. }
46. }
47. else
48. {
49. info "This is not a CRM Record. It might be a RIQ address record";
50. }
51. }

Note: Line 13 needs to have a list of all RIQ integrated modules - api names and their respective email / phone fields - field api names. We recommend adding/removing the values within this collection based on the CRM modules integrated with RouteIQ. Write your own email/SMS triggering logic with content from line no 42.

Example in action

You check out from Warehouse A refilling your bag with all the supplies you're going to be dropping off today. Automatically, Doctor Johnson (your next stop) receives an email/SMS based on your setup like:
"Sonia from Rung Pharmaceuticals is on the way.”

Key Notes  

• If a stop was added manually using @places or @favorite places (i.e., no CRM record is linked), RouteIQ cannot fetch mobile/email automatically. This is because there is no CRM record for that stop. Hence the workflow will be ignored for that particular case.
  
  

• 
  Notifications can be customized. You can choose the exact SMS/email text when setting up the workflow.
  

Note: RouteIQ does not have any SMS / Email vendors in place. To be able to use this function, you have to have an integration setup either through Zoho Marketplace or other vendors of your choice. For further help in this area, please contact support@zohocrm.com and our team will guide you with the process.

• This helpdoc is an example of how data can be taken advantage of to automate your business processes. Learn more on where and what details does RouteIQ send to Zoho CRM to get an idea on writing your own automations.

What you can achieve  

• Saves you time.

• Reduces scope for human error. Bots never forget, people do. This automation rule helps you overcome the shortcoming with manual notifications.

• Saves you work. No one wants to do boring tasks that can be done by a bot