<?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: Workflows and Deployment in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/workflows-and-deployment/m-p/93893#M64283</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Dean:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have just posted our RQA build of our 2.0.1 enterprise maintenance release to the Alfresco Content Community (&lt;/SPAN&gt;&lt;A href="http://community.alfresco.com" rel="nofollow noopener noreferrer"&gt;http://community.alfresco.com&lt;/A&gt;&lt;SPAN&gt;).&amp;nbsp; This is a pre-release version of our upcoming 2.0.1 release, intended to give early access to people to preview and assist in testing our new deployment capabilities.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Our new deployment service is integrated into our UI to enable users to deploy any staging snapshot to one or multiple servers.&amp;nbsp;&amp;nbsp; Using this new&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;deployment service, you can configure staging to deploy to a test or QA&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;box and a live box.&amp;nbsp; Your publishers can submit to staging, deploy staging&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to QA, and review can happen offline via the remote server.&amp;nbsp; Once approved,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;that snapshot can be deployed via the GUI to the live server.&amp;nbsp; Alternatively,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;since deployment is now a service hooked into the Alfresco server, you&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;can call deployment via a workflow and automate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Apr 2007 17:08:54 GMT</pubDate>
    <dc:creator>kvc</dc:creator>
    <dc:date>2007-04-02T17:08:54Z</dc:date>
    <item>
      <title>Workflows and Deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/workflows-and-deployment/m-p/93892#M64282</link>
      <description>I have a bit of a different sitaution and I am wonder what the right approach would be..Our sitation…we have a databse driven application that makes virtualization difficult.&amp;nbsp; So we are planning to push the content out to a staging server as part of the approval workflow.&amp;nbsp; \I am struggline with how</description>
      <pubDate>Fri, 30 Mar 2007 19:30:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/workflows-and-deployment/m-p/93892#M64282</guid>
      <dc:creator>dnewport</dc:creator>
      <dc:date>2007-03-30T19:30:12Z</dc:date>
    </item>
    <item>
      <title>Re: Workflows and Deployment</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/workflows-and-deployment/m-p/93893#M64283</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Dean:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We have just posted our RQA build of our 2.0.1 enterprise maintenance release to the Alfresco Content Community (&lt;/SPAN&gt;&lt;A href="http://community.alfresco.com" rel="nofollow noopener noreferrer"&gt;http://community.alfresco.com&lt;/A&gt;&lt;SPAN&gt;).&amp;nbsp; This is a pre-release version of our upcoming 2.0.1 release, intended to give early access to people to preview and assist in testing our new deployment capabilities.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Our new deployment service is integrated into our UI to enable users to deploy any staging snapshot to one or multiple servers.&amp;nbsp;&amp;nbsp; Using this new&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;deployment service, you can configure staging to deploy to a test or QA&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;box and a live box.&amp;nbsp; Your publishers can submit to staging, deploy staging&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;to QA, and review can happen offline via the remote server.&amp;nbsp; Once approved,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;that snapshot can be deployed via the GUI to the live server.&amp;nbsp; Alternatively,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;since deployment is now a service hooked into the Alfresco server, you&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;can call deployment via a workflow and automate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 17:08:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/workflows-and-deployment/m-p/93893#M64283</guid>
      <dc:creator>kvc</dc:creator>
      <dc:date>2007-04-02T17:08:54Z</dc:date>
    </item>
  </channel>
</rss>

