Re: SugarCRM?
Adam Tauno Williams <[email protected]>
| Newsgroups | gmane.comp.cms.opengroupware.discuss.general |
|---|---|
| Organization | Morrison Industries |
| Message-ID | <[email protected]> |
> > Then we also need a workflow engine. This is necessary if your sales > > cycle or project management has a team of people with roles to play. > > (Roles and function are different entities). > All this is true but not relevant in the discussion unless you can > point to SugarCRM pages which show that the mentioned features are > indeed implemented by that tool. By 'workflow' I think he means the ability of tasks to progress through various statuses beyond, or more specific than, created, processing, done, and archived. SugarCRM uses: pending input, deferred, completed, deferred, and in progress. And the status can be moved back and forth - this seems to me like it could be done with an extended attribute. The ability to move a task from Done back to Processing would be a useful feature in OGo by itself. You can also [in SugarCRM] associate a task with a contact. OGo currently has the Accounting Information, Associated Companies, and Associated Contact fields but these are just free form text fields and not really useful associations (they are used by Zidelook?). -- OpenGroupware.org Discussion [email protected] http://mail.opengroupware.org/mailman/listinfo/discuss