<?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: Share script requires a manual re-run to affect all nodes in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/share-script-requires-a-manual-re-run-to-affect-all-nodes/m-p/298560#M251690</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have gotten around this problem, but it's kind of a silly fix.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Right now the way this works is an external application is causing files to get imported into Alfresco.&amp;nbsp; This application performs a number of checks once this is done, and then executes a web script which kicks off some workflows.&amp;nbsp; In the process of running these checks I now have it calling another web script which will add a character to the description of any files still in the watched folder, causing the script (which is not being executed the first time around) to run again, and so the "stranded" node will get treated after all.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is, as I said, a very silly solution, and I'd still be glad for some insight into what (if anything) I could do to not have to do this in the first place.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Feb 2014 18:46:26 GMT</pubDate>
    <dc:creator>srowsell</dc:creator>
    <dc:date>2014-02-10T18:46:26Z</dc:date>
    <item>
      <title>Share script requires a manual re-run to affect all nodes</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/share-script-requires-a-manual-re-run-to-affect-all-nodes/m-p/298559#M251689</link>
      <description>I have a share script which is run as a rule on a folder within a site's document library, and I will paste the relevant parts below.&amp;nbsp; It is meant to operate in the following manner:1.&amp;nbsp; An external operation causes up to a few hundred documents at a time to be imported into a watched folder.2.&amp;nbsp; Upon</description>
      <pubDate>Wed, 05 Feb 2014 19:41:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/share-script-requires-a-manual-re-run-to-affect-all-nodes/m-p/298559#M251689</guid>
      <dc:creator>srowsell</dc:creator>
      <dc:date>2014-02-05T19:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: Share script requires a manual re-run to affect all nodes</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/share-script-requires-a-manual-re-run-to-affect-all-nodes/m-p/298560#M251690</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have gotten around this problem, but it's kind of a silly fix.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Right now the way this works is an external application is causing files to get imported into Alfresco.&amp;nbsp; This application performs a number of checks once this is done, and then executes a web script which kicks off some workflows.&amp;nbsp; In the process of running these checks I now have it calling another web script which will add a character to the description of any files still in the watched folder, causing the script (which is not being executed the first time around) to run again, and so the "stranded" node will get treated after all.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is, as I said, a very silly solution, and I'd still be glad for some insight into what (if anything) I could do to not have to do this in the first place.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Feb 2014 18:46:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/share-script-requires-a-manual-re-run-to-affect-all-nodes/m-p/298560#M251690</guid>
      <dc:creator>srowsell</dc:creator>
      <dc:date>2014-02-10T18:46:26Z</dc:date>
    </item>
  </channel>
</rss>

