Hi! First off, thanks much to the many posters here, searching the forums has been helpful over the past months as we ramp up our use of sugar. We are currently running 5.2.e professional edition.
Now for my question --
Workflows for 'on update' and 'on save' are all working great. But the "After time elapses" workflows seem to be very problematic as noted on many forum topics in the last couple years.
I'm trying to write a workflow that notifies us of 'stale' opportunities, basically opportunities that haven't been updated for 60+ days.
In testing, I've run into three problems:
1. A new "after time elapses" workflow only seems to apply to data entered AFTER the workflow is created. For example, if I have 150 existing opportunities, then create a workflow to alert of stale opportunities, it only will alert of stale Opportunities we create AFTER making the workflow. How do I make a "after time elapses" workflow retroactively work for previously existing data?
2. I can get the "after time elapses" rule to work (on new data) only if I have a single condition. It doesn't matter what field, i.e., 'Sales Stage: does not change for 60 days' works fine. But I want to check for multiple conditions by also checking that 'Expected Close Date: does not change for 60 days'. My assumption is that when you have multiple conditions it ANDs them, but in testing it seems to just completely break. I.e., 1 condition and things work fine, but 2 conditions and I never get anything. It is testable and repeatable.
3. I only ever get 1 alert generated from a workflow. I would like the alert to be sent every time the scheduler triggers processWorkflow. I.e., I want it to nag us. But it seems like the workflow remembers when it sends an alert, and only ever does it once.
Any advice on these topics would be appreciated.


LinkBack URL
About LinkBacks



Reply With Quote

Bookmarks