<?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: Simple Workflow - Overwrite Content Problem in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/simple-workflow-overwrite-content-problem/m-p/243788#M196918</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;There's a couple of ways you can approach this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) Rethink your rules - Ultimately, if something is deemed published/public/approved/etc, one would essentially want to work off that document so, from a end user training perspective, they should perform a 'Check Out' of the document and perform the checkout to the draft folder.&amp;nbsp; The draft folder would still have a rule to then move to Review.&amp;nbsp; The difference is the rule in 'PROD' would need to check-in the doc (which is an available action).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Leaving things the way they are, you can apply a rule to 'Execute a Script' in the 'PROD' space.&amp;nbsp; The script should essentially check to see if a doc with that name exists - if it does, update the content, if it doesn't create net new.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Oct 2009 19:10:28 GMT</pubDate>
    <dc:creator>richard_im</dc:creator>
    <dc:date>2009-10-21T19:10:28Z</dc:date>
    <item>
      <title>Simple Workflow - Overwrite Content Problem</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/simple-workflow-overwrite-content-problem/m-p/243787#M196917</link>
      <description>Hi All,I've recently been playing around with the simple workflow rules, in the Alfresco Explorer.I'm trying to simulate an experience where a user will open a piece of content, in a "DRAFT" space, using the "edit online" feature.&amp;nbsp; Once they are satisfied with their changes, they will click on the i</description>
      <pubDate>Tue, 06 Oct 2009 17:56:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/simple-workflow-overwrite-content-problem/m-p/243787#M196917</guid>
      <dc:creator>peterstb</dc:creator>
      <dc:date>2009-10-06T17:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: Simple Workflow - Overwrite Content Problem</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/simple-workflow-overwrite-content-problem/m-p/243788#M196918</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;There's a couple of ways you can approach this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) Rethink your rules - Ultimately, if something is deemed published/public/approved/etc, one would essentially want to work off that document so, from a end user training perspective, they should perform a 'Check Out' of the document and perform the checkout to the draft folder.&amp;nbsp; The draft folder would still have a rule to then move to Review.&amp;nbsp; The difference is the rule in 'PROD' would need to check-in the doc (which is an available action).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Leaving things the way they are, you can apply a rule to 'Execute a Script' in the 'PROD' space.&amp;nbsp; The script should essentially check to see if a doc with that name exists - if it does, update the content, if it doesn't create net new.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Oct 2009 19:10:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/simple-workflow-overwrite-content-problem/m-p/243788#M196918</guid>
      <dc:creator>richard_im</dc:creator>
      <dc:date>2009-10-21T19:10:28Z</dc:date>
    </item>
  </channel>
</rss>

