<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: auto deploy option in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/auto-deploy-option/m-p/132675#M93186</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Stephen:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I do know of one partner that is implementing a solution exactly like this for a customer in the Media and Entertainment space.&amp;nbsp; I also know that that partner is hoping to contribute that back as a Community contribution, which we in turn hope to include in an updated distribution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To enable auto-deploy, this should involve adding an additional action in the end task for your workflow that executes the deployment.&amp;nbsp; If you look at how deployment is called and executed from the web client, this should give you what you need to enable in workflow.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you do do this work, please do contribute back via a Forge project.&amp;nbsp; We would very much like to include this into the product (but unfortunately, we can't do everything ourselves).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Sep 2007 13:31:46 GMT</pubDate>
    <dc:creator>kvc</dc:creator>
    <dc:date>2007-09-18T13:31:46Z</dc:date>
    <item>
      <title>auto deploy option</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/auto-deploy-option/m-p/132674#M93185</link>
      <description>We have a lot of cases in which the author of the content is also the approver of the content.&amp;nbsp; When they are adding things like news stories, etc. the desire is to be able to submit the new content from the user's sandbox and have the content be published out to the live servers.&amp;nbsp; That means no wor</description>
      <pubDate>Mon, 17 Sep 2007 19:02:14 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/auto-deploy-option/m-p/132674#M93185</guid>
      <dc:creator>slynn</dc:creator>
      <dc:date>2007-09-17T19:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: auto deploy option</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/auto-deploy-option/m-p/132675#M93186</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Stephen:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I do know of one partner that is implementing a solution exactly like this for a customer in the Media and Entertainment space.&amp;nbsp; I also know that that partner is hoping to contribute that back as a Community contribution, which we in turn hope to include in an updated distribution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;To enable auto-deploy, this should involve adding an additional action in the end task for your workflow that executes the deployment.&amp;nbsp; If you look at how deployment is called and executed from the web client, this should give you what you need to enable in workflow.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you do do this work, please do contribute back via a Forge project.&amp;nbsp; We would very much like to include this into the product (but unfortunately, we can't do everything ourselves).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2007 13:31:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/auto-deploy-option/m-p/132675#M93186</guid>
      <dc:creator>kvc</dc:creator>
      <dc:date>2007-09-18T13:31:46Z</dc:date>
    </item>
  </channel>
</rss>

