Communication Events, Content, and Forums

[Adrian Crum <ad...@yahoo.com>]

I need some guidance on how to accomplish a task in
OFBiz.

I have our OFBiz instance routing incoming emails
(communication events) to our OFBiz users. They can
view their messages and the attachments. I recently
updated the trunk to enable setting the attachment's
data resource to isPublic = "Y".

What I need is a way to allow the user to attach the
bits of content marked isPublic = "Y" to forum
messages. I pictured a drop-down list in the Add Forum
Message screen which would allow the user to select
the content that is flagged as public.

Is that a good way to go? Has anyone else tried this?

Any suggestions?

-Adrian



      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

Re: Communication Events, Content, and Forums

[David E Jones <jo...@hotwaxmedia.com>]

On Jan 25, 2008, at 12:37 PM, Adrian Crum wrote:

> I need some guidance on how to accomplish a task in
> OFBiz.
>
> I have our OFBiz instance routing incoming emails
> (communication events) to our OFBiz users. They can
> view their messages and the attachments. I recently
> updated the trunk to enable setting the attachment's
> data resource to isPublic = "Y".
>
> What I need is a way to allow the user to attach the
> bits of content marked isPublic = "Y" to forum
> messages. I pictured a drop-down list in the Add Forum
> Message screen which would allow the user to select
> the content that is flagged as public.

A drop-down seems like a limiting way to go about it. Even in a small  
user group (like a few people) there can be tens of thousands of  
messages per year. I guess this would certainly depend on how the  
system was used and the expected message volume, and then how many of  
those have attachments.

But anyway, the idea in general seems fine, and a pop-up with certain  
query parameters like to/from emails or users or whatever might be  
better.

BTW one other thing, the isPublic is a very coarse-grained permission  
pattern and is really meant for totally public things like in and  
outside an organization. If that's what you need, then great, but I  
know that's not often the case. Of course, if you only want internal  
access and there is only internal access to the system that's fine,  
though it may limit future flexibility.

-David