Re: OGo/Plone integration

Hi Helge et all!

> Support requests should be handled by a good
> ticketing application, 
> like RT or Bugzilla. This is not really a groupware
> nor a CMS topic, 
> though obviously there are integration points ;-)

No arguments there, but integration is good from a CRM
point of view.  I agree with Kelly's comments about
RT; Jesse did a fine job with it, and it's a great
application.  Integration is the only issue.  I worked
for a big hi tech company, and almost all the
applications were "islands in the stream".  There was
way too much duplicate, or conflicting information, or
none at all, and chasing it down was always difficult.
 Bringing everything together (somehow?) into
something like OGo would really benefit a lot of
companies by providing an accurate overview of their
customer relations - be it internal or external
customers.
 
> If you have low requirements: tasks + projects. If
> you have higher 
> requirements, see above.

Tasks and projects are good.  Tasks should support
dependencies at some point for real project management
applications.  Maybe something like RT's "depended on"
or "depends on" features.

> > Also, Plone has a workflow system.  How would OGo
> handle that?
> 
> A somewhat too generic statement? Do you have an
> application in mind or 
> just try to be buzzword compliant? ;-)

< ;-P >Helge, I'm shocked!  Are you suggesting I use
buzzwords for the sake of using them? </ ;-P >  :-)

Seriously though, workflow (business process, document
flow, whatever) is common everywhere in business, and
it would be good if OGo had some sort of more advanced
version of business logic available.  In documents, at
the least there is Create -> Submit ->
Review{Approve/Reject} -> Publish (like the OGo
plone).  In the company I used to work for (5k people
on campus) there were hundreds of documents being
used/worked on at any one time.  There was an
electronic document review process (workflow) that
notified the signoff "committee" as to the state of
documents (pending review, pending acceptance, etc)
and the signoff status of each member, working towards
final approval by the lead.  That kind of thing... 

> OGo _has_ group permissions for almost all objects
> in OGo. We miss 
> roles, especially for administration.

Roles would be handy.  That way you could have stuff
like "signoff_required", "Manager", "Owner", etc.  and
have that part of the workflow system as well as
overall OGo system administration & permission
structure.

> > BTW... why are OGo forms not recommended?
> 
> The ObjC/JavaScript bridge broke in subtle ways when
> going from SKYRiX 
> 4.1=>4.2 (which is the OGo basis) and no one had the
> time/interest to 
> fix that.
> It wasn't used a lot anyway, most extensions for
> customers being 
> written as WO extension plugins.

OK... then maybe could there be a stripped down
version of a WO extension plugin that people could use
as a template to create new modules?  If we had a well
documented "Module starter Kit", that could encourage
more developer involvement.

Gotta run and feed my baby.... then back to work when
she naps.  The joys of starting a business at home! 
(Actually, it is nice... challenging, but nice.)

/Mike

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca
-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss