SugarBPM: trigger event when a field change to any value

Set a parallel gateway that includes receive message (change in field) and the timer.  Then your exclusive gateway that sends the message and end or just ends.  I would have attached a screenshot with the diagram but didn't see how to do that.

If the field changes before the timer, the process will end before the seven days expires.

Bud Hartley's answer is good. I had something similar in mind but I think an Event-based gateway might be a slightly better choice because only one of the two paths can be taken. With a Parallel gateway, both paths could theoretically be taken, which is highly unlikely in this case but you never know!

Here is what I had in mind:

Check out the Parallel Gateways and Event-Based Gateways documentation for more information on the two options.

Bud, you can add an image via Insert > Image/video/file. To choose a file on your computer, click "Upload" below the URL field. It doesn't look like it is clickable but I discovered that it is.

Thanks Brenda - I guess I didn't look for the Upload option :-)

Thanks to both of you for the tip.

I only have one question, does the flow as set by Brenda stay open in loop?

Let me explain:

1. the flow starts
2. waits 7 days to verify the modification of the description field
3. the description is modified 2 days after saving

At this point the flow starts again, right? So it is basically always open until you change one of the starting parameters (phase, amount or type). Is it correct?

Hi Mirco, SugarBPM prevents infinite loops because it doesn't allow multiple processes targeting the same record. So updating the description would not trigger a new process until the current one has ended.

Hope that helps.