Bug Found in Cancel Process Event
Process Manager Customers,
One of our customers has discovered a bug in Process Manager that has been fixed as of 5/19/2010. This customer had three processes on Lead Modify. Each of the processes was triggered on status = 'a specific value' and a cancel event where status != 'the same value'. The processes had an immediate stage and delayed stages. As soon as the lead was modified to match the status - the first stage was triggered and was completed - then the delayed stages were queued up to run. However, because Process Manager had two other processes setup with cancel events on different values against the same field - the delayed stages were being removed from the queue.
A fix for this bug will be sent out to all registered owners of Process Manager.
Thanks
Bill
Customer Support
SierraCRM
One of our customers has discovered a bug in Process Manager that has been fixed as of 5/19/2010. This customer had three processes on Lead Modify. Each of the processes was triggered on status = 'a specific value' and a cancel event where status != 'the same value'. The processes had an immediate stage and delayed stages. As soon as the lead was modified to match the status - the first stage was triggered and was completed - then the delayed stages were queued up to run. However, because Process Manager had two other processes setup with cancel events on different values against the same field - the delayed stages were being removed from the queue.
A fix for this bug will be sent out to all registered owners of Process Manager.
Thanks
Bill
Customer Support
SierraCRM

Comments