Dynamically Creating Customer Journey Tasks with SugarBPM?

Question

Hi Everyone! 
 I'm seeking to find out what is best practice when it comes to dynamically creating customer journey tasks for an active customer journey, using SugarBPM workflows? 
 For example, if an agent completes a particular stage/task of the customer journey, and certain conditions are satisfied, then a SugarBPM triggers and creates a set of customer journey tasks appearing after the completed task. 
 I'm curious to find the ways in which people are achieving this? 
 Thanks

Joy Lamparas · Accepted Answer

Hi Ryan, 
 The easiest way to manipulate CJ tasks dynamically is to configure manipulation logic with Logic Builder configuring tool ( http://logicbuilder.integroscrm.com ) - e.g. to check criteria and contextually update Tasks created from CJ, relate them to the records the Tasks should belong to, fill out Tasks with Sugar data, ect That approach works for both - Sugar Cloud and On-premise , any Sugar version from 7.2 and up to the current and very useful if you prefer configuring instead of writing code to enhance Sugar I've made some screenshots to show the example - its easy to read if to enlarge the picture, then follow the while line . This might give you an idea, however, if you signed up to Logic Builder already then drop me the login with a private message and I will share the flowchart to you

Joy Lamparas · Answer

Hi Ryan 
 If you are on-premise, another option is to extend SugarBPM to create a new custom Action that could be leveraged in your process definition to add tasks to the Customer Journey record. 
 Please look at this GitHub repo, which gives you a solid starting point if you decide to go this route. 
 https://github.com/esimonetti/SugarAdvancedWorkflowCustomPHPMethods 
 I've actually done something similar to what you are looking for using the repo above for a POC we did last year for a Sugar customer. 
 The repo is a bit older as it was tested against 7.8, but I can confirm that it still works in 10.0.0. As I mentioned, in its current state, it will not work in SugarCloud as it leverages some functions that would not pass the package scanner. 
 I hope it helps.