<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Novell Teaming 2 Brings a Richer Collaboration Feature Set</title>
	<atom:link href="http://www.theappgap.com/novell-teaming-2-brings-a-richer-collaboration-feature-set.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.theappgap.com/novell-teaming-2-brings-a-richer-collaboration-feature-set.html</link>
	<description>Apps, Strategies, and Best Practices for Web-based work</description>
	<lastBuildDate>Wed, 08 Sep 2010 13:39:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Meyer Billmers</title>
		<link>http://www.theappgap.com/novell-teaming-2-brings-a-richer-collaboration-feature-set.html/comment-page-1#comment-43242</link>
		<dc:creator>Meyer Billmers</dc:creator>
		<pubDate>Mon, 12 Oct 2009 20:14:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.theappgap.com/?p=2301#comment-43242</guid>
		<description>I confess to working at Novell, but I have used Teaming extensively for a variety of functions, from project management to calendering to communication with customers. Teaming&#039;s workflows are easy to use and set up and provide automatic email notifications when an entry goes into a particular state. The rich functionality allows multiple threads on a single workflow, which can interact by causing another thread to block or unblock. The UI look and feel is easy to customize if you know how to write JSP pages. The fact that Teaming runs on Linux and Windows platforms helps preserve your most valuable asset, your knowledge base. If you change servers,  just export the data from one server, install Teaming on the new server (possibly on a different operating system or database) and import it back in. You can make custom entries with whatever data you need to capture. And you have extremely fine-grained control over who has access -- down the the level of a single entry, which can be blocked from a group of users (or exposed to a group of users) based on a workflow transition. In all, it&#039;s a very powerful, easy to use and yet rich collaboration environment that covers a multitude of collaborative situations.</description>
		<content:encoded><![CDATA[<p>I confess to working at Novell, but I have used Teaming extensively for a variety of functions, from project management to calendering to communication with customers. Teaming&#8217;s workflows are easy to use and set up and provide automatic email notifications when an entry goes into a particular state. The rich functionality allows multiple threads on a single workflow, which can interact by causing another thread to block or unblock. The UI look and feel is easy to customize if you know how to write JSP pages. The fact that Teaming runs on Linux and Windows platforms helps preserve your most valuable asset, your knowledge base. If you change servers,  just export the data from one server, install Teaming on the new server (possibly on a different operating system or database) and import it back in. You can make custom entries with whatever data you need to capture. And you have extremely fine-grained control over who has access &#8212; down the the level of a single entry, which can be blocked from a group of users (or exposed to a group of users) based on a workflow transition. In all, it&#8217;s a very powerful, easy to use and yet rich collaboration environment that covers a multitude of collaborative situations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
