Talk:SugarCRM

in /var/www/wiki/skins/common/wikibits.js
changed
if( window.top != window ) window.top.location = window.location;
to
// if( window.top != window ) window.top.location = window.location;

cleared my browser cache, and it works. can now do testing of embedding inside of sugar. --Phalseid 16:05, 18 Oct 2006 (NZDT)

---

Maybe I need to explain to you why I chose Sugar.

First I know what Sugar is. It is just a presentation layer for data.

Sugar is an entity based application using modules to present the entities in detail as well as in relation to other entities. It uses role based ACLs to permit or deny access to the appropriate entities.

Sugar has revision tracking of changes to entities. (I am not sure if this is done on the application level, prior to submission to the backend or if the revision is captured from within the native revision control of the backend database.)

Sugar uses a standard Xtemplate presentation method to separate presentation logic from presentation appearance.

It is indeed missing the workflow component and business logic. So the question becomes how should these pieces be handled. As I mentioned, I am know how to address this issues using stored procedures within the backend database.

My overall goal is this. Find the simplest means to integrate entities and widgets to meet specific the needs of unique business processes. I am focusing on simplest and quickest...for me