The latest release of SierraCRM's Powerful Workflow module for SugarCRM includes major improvements in usability, core functionality and administrative capabilities.
This new release of SierraCRM’s Business Process Management product for SugarCRM includes a number of innovative new features designed to improve functionality and enhance the creation of workflow in SugarCRM.
New Features Include:
- Drag and Drop wizard like builder for process creation
- Administrative Console
- Enhanced Email capabilities.
- Update any one record or all related records
- Contract Approval Processes
- Lead Management Processes
Located in the Sierra foothills of Northern California, SierraCRM began as a consulting company in 1997
for then CRM Vendor Clarify. Clarify was soon acquired by Amdocs and SierraCRM continued to be a consulting partner
for Amdocs, deployed on projects worldwide. In 2005, when SugarCRM was a young company releasing the first truely open systems
CRM solution, SierraCRM embraced this product and signed on as a developer partner. SierraCRM's first vertical market
solution for SugarCRM was LenderCRM, a vertical solution for the Mortgage Banking Market. SierraCRM delivered the first release
of Process Manager as an open source project on SugarForge in 2007 and was awarded Project of the Month that year.
With over 30 years of combined CRM expertise, the team at SierrCRM delivers innovative products and solutions for SugarCRM, including
the all new Process Manager Enterprise 2.0
" SierraCRM’s Process Manager Enterprise 2.0 enables us to do what we do best, service and support our Life Insurance Brokers and not running the day to day operation of the... "Reid Tattersall - Back 9 Insurance
" SierraCRM’s Process Manager Pro has helped decrease work load while increasing productivity. Since implementation we have been able to automate many manual processes that it took a team, several hours... "Craig Broton, CEO – Sunflower Business Solutions
" I wanted to automate the creation of a series of tasks which needed to be done in a specific sequence every time a new instance of a custom module was... "Richard Cantin, Wilfrid Laurier University, 2012