<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Clearspace Server Syndication Feed</title>
    <link>http://www.jivesoftware.com/jivespace/blogs</link>
    <description>A syndication feed of all the blogs on this system</description>
    <pubDate>Mon, 28 Jul 2008 17:00:47 GMT</pubDate>
    <generator>Clearspace 2.5.5 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-07-28T17:00:47Z</dc:date>
    <item>
      <title>Web Service operation UserService deleteUser going away.</title>
      <link>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/07/28/web-service-operation-userservice-deleteuser-going-away</link>
      <description>&lt;!-- [DocumentBodyStart:5827c2d6-8b2f-4f89-8ea9-4253c0a5b0ce] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;In 2.0.6 and 2.5.0 the UserService deleteUser method is going away. This is due to a transaction issue in the core UserManager#deleteUser method. The UserManager#deleteUser method is also disabled in these versions because of this.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;In the web service we opted to remove the method, rather than have the WSDL reflect a method that would only throw an Exception. &lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The method will once again return in a future version. In the meantime we recommend using the UserService disableUser operation instead as this will prevent the user from contributing any new content.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:5827c2d6-8b2f-4f89-8ea9-4253c0a5b0ce] --&gt;</description>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/tags">clearspace</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/tags">web-services</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/tags">clearspacex</category>
      <pubDate>Mon, 28 Jul 2008 17:00:47 GMT</pubDate>
      <author>andrew</author>
      <guid>http://www.jivesoftware.com/jivespace/blogs/jivespace/2008/07/28/web-service-operation-userservice-deleteuser-going-away</guid>
      <dc:date>2008-07-28T17:00:47Z</dc:date>
      <wfw:comment>http://www.jivesoftware.com/jivespace/blogs/jivespace/comment/web-service-operation-userservice-deleteuser-going-away</wfw:comment>
      <wfw:commentRss>http://www.jivesoftware.com/jivespace/blogs/jivespace/feeds/comments?blogPost=1563</wfw:commentRss>
    </item>
    <item>
      <title>Extending Clearspace's Document Approval</title>
      <link>http://www.jivesoftware.com/jivespace/blogs/jivespace/2007/07/27/extending-clearspaces-document-approval</link>
      <description>&lt;!-- [DocumentBodyStart:104a3f96-af4f-478f-b09f-2a1bf5167eff] --&gt;&lt;div class='jive-rendered-content'&gt;&lt;p&gt;Clearspace ships with a simple approval workflow system. You are allowed to select people that should approve a document. The approvers can be forced on all documents at the space level that are created, or can be added by authors at the invidual document level. Though this system is quite powerful and sufficient for many circumstances it may not fit everyone's needs. This is why we built workflow on Open Symphony's&amp;nbsp; &lt;a class="jive-link-external-small" href="http://www.opensymphony.com/osworkflow"&gt;OSWorkflow&lt;/a&gt; architecture.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;OSWorkflow allows entire new workflow processes to be added to Clearspace. Clients can define and customize the workflow system by changing an xml configuration rather than rewriting parts of the core document api.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Customized workflows can be written via a Clearspace plugin. The plugin will contain custom workflow classes, the workflow configuration, and any additional workflow related webwork actions and pages. Your workflow can then be deployed at runtime without having to redeploy the core Clearspace application.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:104a3f96-af4f-478f-b09f-2a1bf5167eff] --&gt;</description>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/tags">workflow</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/tags">opensymphony</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/tags">clearspace</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/tags">osworkflow</category>
      <category domain="http://www.jivesoftware.com/jivespace/blogs/tags">approval</category>
      <pubDate>Fri, 27 Jul 2007 19:09:31 GMT</pubDate>
      <author>andrew</author>
      <guid>http://www.jivesoftware.com/jivespace/blogs/jivespace/2007/07/27/extending-clearspaces-document-approval</guid>
      <dc:date>2007-07-27T19:09:31Z</dc:date>
      <wfw:comment>http://www.jivesoftware.com/jivespace/blogs/jivespace/comment/extending-clearspaces-document-approval</wfw:comment>
      <wfw:commentRss>http://www.jivesoftware.com/jivespace/blogs/jivespace/feeds/comments?blogPost=1019</wfw:commentRss>
    </item>
  </channel>
</rss>

