https://connect.hyland.com/t5/alfresco-archive/expiration-date/m-p/164232#M117983 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><SPAN>I want to test publish a content with a launch date and an expiration date. Must be Alfresco installed on publication server? (now I have Alfresco only on editorial server form which I deploy content).</SPAN><BR /><BR /><SPAN>Thanks Daniel.</SPAN></BODY></HTML> Mon, 25 Feb 2008 17:24:49 GMT danielhrotek1 2008-02-25T17:24:49Z https://connect.hyland.com/t5/alfresco-archive/expiration-date/m-p/164232#M117983 Hi,I want to test publish a content with a launch date and an expiration date. Must be Alfresco installed on publication server? (now I have Alfresco only on editorial server form which I deploy content).Thanks Daniel. Mon, 25 Feb 2008 17:24:49 GMT https://connect.hyland.com/t5/alfresco-archive/expiration-date/m-p/164232#M117983 danielhrotek1 2008-02-25T17:24:49Z https://connect.hyland.com/t5/alfresco-archive/expiration-date/m-p/164233#M117984 <HTML><HEAD></HEAD><BODY><SPAN>The short answer is no, you don't need Alfresco in your delivery environment in order for launch and expiration dates to function.</SPAN><BR /><BR /><SPAN>The long answer is that effectivity periods and deployment in Alfresco are handled at different stages in the content lifecycle, so don't directly interact.&nbsp; In particular timed launch controls when content is </SPAN><STRONG>promoted to the staging sandbox</STRONG><SPAN>, and does not (as is often assumed) control when the content is deployed.</SPAN><BR /><BR /><SPAN>The expiration date is even more misleading, in that it's simply an advisory date - the Alfresco system actually doesn't do anything beyond creating a task for the author when the expiry date is reached.&nbsp; The user then has to choose what they wish to do with that content (eg. delete it and submit the deletion to workflow).</SPAN></BODY></HTML> Mon, 25 Feb 2008 18:52:22 GMT https://connect.hyland.com/t5/alfresco-archive/expiration-date/m-p/164233#M117984 pmonks 2008-02-25T18:52:22Z