Return to Jive Software

2,399 Views 4 Replies Last post: May 18, 2009 12:18 PM by Karl Cyr RSS
gayathri@lindenlab.com Beginner 353 posts since
Oct 14, 2008
Currently Being Moderated

Apr 22, 2009 9:17 PM

Collapsing threads in discussions

I'm curious if anyone else has either limited the number of posts that can respond on a discussion thread, split off various threads to other discussions, or how to at least set it up so that forum discussions are 'collapsed' with maybe a sentence or two of the response and a link to see 'more' if needed.

 

(In particular, our users who read discussions on their handhelds would like a feature they didnt have to scroll through EVERYTHING to see what was new, or could skim over long threads)

Tags: admin
Karl Cyr Jive Employee 6,819 posts since
Mar 12, 2008
Currently Being Moderated
Apr 23, 2009 3:34 PM in response to: gayathri@lindenlab.com
Re: Collapsing threads in discussions

I don't know of anybody who has performed this type of customization, but I can definitely see the value. It is possible to separate one thread into several using the "Branch Thread" feature.

Karl Cyr Jive Employee 6,819 posts since
Mar 12, 2008
Currently Being Moderated
May 18, 2009 12:18 PM in response to: gayathri@lindenlab.com
Re: Collapsing threads in discussions

Gayathri,

 

I found this link for a very similar type of discussion last year: Discussion or Document Thread Collapsed(?) View It has been spun into a Feature Request (CS-4597) and I have added your feedback to that ticket.

 

I think Aaron's suggestion to customize thread.ftl and use the isRead() method is probably the best start. The business objects aren't necessarily built to support this kind of functionality, but you certainly could play with things at the View layer (i.e. in the FTL) to make the discussion threads display as you desire.

 

Regards,

Karl

More Like This

  • Retrieving data ...

Bookmarked By (0)

Case Product Issues

Loading Jira issues

Loading related product issues for this case
To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.