vchmakov [https://community.jboss.org/people/vchmakov] created the discussion "Re: Design advice: multi-day scenario" To view the discussion, visit: https://community.jboss.org/message/795276#795276 -------------------------------------------------------------- Hi, This process is executed by scheduler periodically, e.g. daily: Select Customer.ID Customer where Today-Customer.ActivationDay = 10 and Customer.Status <> “No Mail” -> send email A Select Customer.ID Customer where Today-Customer.ActivationDay = 20 and Customer.Status <> “No Mail” -> send email B Select Customer.ID Customer where Today-Customer.ActivationDay = 30 and Customer.Status <> “No Mail” -> send email C Select Customer.ID Customer where Today-Customer.ActivationDay = 45 and Customer.Status <> “No Mail” -> send email D Select Customer.ID Customer where Today-Customer.ActivationDay = 60 and Customer.Status <> “No Mail” -> update Customer set Customer .status=“No Mail” where Customer.ID=? This process is triggered by “Unsubscribe” event: Select * from Customer where Customer.ID = ? -> update customer set status=“No Mail” where Customer.ID=? In my opinion this use case fits perfectly for the Drools implementation (event/rule driven), but has nothing to do with jBPM. Maybe there is something not mentioned above that can be implemented in jBPM, but it is always easy to do implementing a rule in certain way. Thanks, Vladimir -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/795276#795276] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]

vchmakov [https://community.jboss.org/people/vchmakov] created the discussion "Re: Design advice: multi-day scenario" To view the discussion, visit: https://community.jboss.org/message/795290#795290 -------------------------------------------------------------- Hi, That’s the point - you do not need to store the number of days since creation, you calculate it: Today-Customer.ActivationDay. Other parameters are also persisted in your data model, e.g. update Customer set Customer .status=“No Mail” where Customer.ID=? etc. Why would you use jBPM persistence to store the values which belong to YOUR business logic? jBPM is about to help you solving other problems. I’m not saying that there is no use of it in your project, but what you have described above in not for jBPM implementation in my opinion. That’s all I’m trying to say. Thanks, Vladimir -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/795290#795290] Start a new discussion in jBPM at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]