<?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: Can you do time-based pulishing with Alfresco? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/can-you-do-time-based-pulishing-with-alfresco/m-p/167524#M121045</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;For WCM content, you can define an effectivity period (start date / end date) that controls when the content gets promoted to the staging sandbox (and hence becomes eligible for deployment).&amp;nbsp; This isn't &lt;/SPAN&gt;&lt;EM&gt;quite&lt;/EM&gt;&lt;SPAN&gt; the same thing is scheduled deployment, but if you've configured auto deploy (available from v2.2 onward) then in practical terms it ends up being the same thing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Note that with this model, undeployment is still manual - the end date is a reminder rather than an automatic action; it serves to "poke" the author and remind them that something (eg. deletion) needs to be done with the content.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you require true scheduled deployment, you might find the "wcm-deployment" project on the forge relevant (&lt;/SPAN&gt;&lt;A href="http://forge.alfresco.com/projects/wcm-deployment/" rel="nofollow noopener noreferrer"&gt;http://forge.alfresco.com/projects/wcm-deployment/&lt;/A&gt;&lt;SPAN&gt;).&amp;nbsp; It includes a Web Script that can be invoked via wget from cron, and the intention is to implement the same functionality as a Quartz bean as well (so that it can be scheduled from within Alfresco via the Quartz timed job execution engine).&amp;nbsp; I just haven't had time to do that yet.&amp;nbsp; :wink:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Peter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Aug 2008 05:16:42 GMT</pubDate>
    <dc:creator>pmonks</dc:creator>
    <dc:date>2008-08-13T05:16:42Z</dc:date>
    <item>
      <title>Can you do time-based pulishing with Alfresco?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/can-you-do-time-based-pulishing-with-alfresco/m-p/167523#M121044</link>
      <description>Hi. Does Alfresco support time-based publishing? In other words, you can tell it when to start showing a certain content and when to end.</description>
      <pubDate>Tue, 12 Aug 2008 19:42:14 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/can-you-do-time-based-pulishing-with-alfresco/m-p/167523#M121044</guid>
      <dc:creator>oneworld95</dc:creator>
      <dc:date>2008-08-12T19:42:14Z</dc:date>
    </item>
    <item>
      <title>Re: Can you do time-based pulishing with Alfresco?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/can-you-do-time-based-pulishing-with-alfresco/m-p/167524#M121045</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;For WCM content, you can define an effectivity period (start date / end date) that controls when the content gets promoted to the staging sandbox (and hence becomes eligible for deployment).&amp;nbsp; This isn't &lt;/SPAN&gt;&lt;EM&gt;quite&lt;/EM&gt;&lt;SPAN&gt; the same thing is scheduled deployment, but if you've configured auto deploy (available from v2.2 onward) then in practical terms it ends up being the same thing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Note that with this model, undeployment is still manual - the end date is a reminder rather than an automatic action; it serves to "poke" the author and remind them that something (eg. deletion) needs to be done with the content.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you require true scheduled deployment, you might find the "wcm-deployment" project on the forge relevant (&lt;/SPAN&gt;&lt;A href="http://forge.alfresco.com/projects/wcm-deployment/" rel="nofollow noopener noreferrer"&gt;http://forge.alfresco.com/projects/wcm-deployment/&lt;/A&gt;&lt;SPAN&gt;).&amp;nbsp; It includes a Web Script that can be invoked via wget from cron, and the intention is to implement the same functionality as a Quartz bean as well (so that it can be scheduled from within Alfresco via the Quartz timed job execution engine).&amp;nbsp; I just haven't had time to do that yet.&amp;nbsp; :wink:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Peter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Aug 2008 05:16:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/can-you-do-time-based-pulishing-with-alfresco/m-p/167524#M121045</guid>
      <dc:creator>pmonks</dc:creator>
      <dc:date>2008-08-13T05:16:42Z</dc:date>
    </item>
  </channel>
</rss>

