Workflow conditions glitch

Hi Rachel,

I believe the issue you are referring to has been identified as Bug #77357 which we are looking to resolve in a future release of Sugar. Please take a look at the following Bug Report:

https://web.sugarcrm.com/support/issues/77357 

If you are experiencing something different, please let me know some specifics.

Hope this helps.

 -Chris

Chris, if we upgraded to version 7.7.2 would this issue be resolved? 

Rachel Keller in sugar 7.7.* process author is also available which is much more useful and advanced then workflows.

so you can replace workflow with process author in upgraded version.

Please find below link for more info on this. 

http://support.sugarcrm.com/Documentation/Sugar_Versions/7.6/Ult/Administration_Guide/Process_Author/

Thank you, Hemant Patil. Do you know if process author available in the professional edition? 

Hi Rachel,

From the Process Author Documentation:

Process Author, also known as Sugar's advanced workflow, is exclusive to Enterprise and Ultimate editions of Sugar 7.6.x and later.

I hope that helps!

-Alan

Thank you, Alan Beam!  Does that mean the professional edition still has workflows?  If so, do you know if there's a bug in the 7.7.2 version? 

Professional Edition does still have Workflows, but not for much longer. In a future version (possibly 7.8?) workflows will be completely removed. You can read this article for more information on your options at that point.

I know that this bug still exists in 7.6.2.2, but I don't know if it does in 7.7.x. Maybe Chris Weinlich knows?

Hi Rachel Keller,

This Bug is still being assessed by our internal team to work on a fix for this, therefore it has not been resolved in 7.7.2.x of Sugar. Given that we are phasing out the legacy workflows, there is more focus on enhancing other aspects of the application. You can use the link provided in my initial response to track the progress.

Hope this gives you some more information.

 -Chris

Hey Rachel,

We had this problem a while back and were told it was the bug mentioned above but that it didn't effect the Firefox browser. I made the switch and have not had the problem since. Supposedly it's an issue of display rather than functionality.

Cheers,
Dave

Good pick up David Fox! I have added this to our internal team so they are also aware. Many thanks!