<?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 SQL to filter by allowable actions in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/sql-to-filter-by-allowable-actions/m-p/278215#M231345</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am helping build Alfresco client support (via CMIS) into an existing Java application. In our Alfresco implementation we have a number of different sites - currently almost 100. At full implementation we may have considerably more. Our targeted user community will be segregated by project and a typical user will only have write access to a limited number of sites.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I want to retrieve a sorted list of sites that includes only the sites to which a user has write access (allowable actions CAN_CREATE_DOCUMENT,CAN_UPDATE_PROPERTIES, etc.). I have this currently working very nicely with the API via getDescendents on the Sites folder and related method calls.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem: performance sucks (is terrible, for those not familiar with English slang). It can take up to 30 seconds to return the filtered, sorted list of sites to the user. This will only get worse as we add more sites.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have coded an alternate implementation that fetches only the relevant properties for the user UI using an SQL query. It returns a sorted list in 2 seconds. The only problem is that this list is not filtered by allowable actions.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is there a way to query allowable actions using SQL?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am happy to post code fragments on request, but this seems like a generic type of question so I won't for now.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Jun 2014 21:02:05 GMT</pubDate>
    <dc:creator>mikerawlins</dc:creator>
    <dc:date>2014-06-18T21:02:05Z</dc:date>
    <item>
      <title>SQL to filter by allowable actions</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/sql-to-filter-by-allowable-actions/m-p/278215#M231345</link>
      <description>I am helping build Alfresco client support (via CMIS) into an existing Java application. In our Alfresco implementation we have a number of different sites - currently almost 100. At full implementation we may have considerably more. Our targeted user community will be segregated by project and a ty</description>
      <pubDate>Wed, 18 Jun 2014 21:02:05 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/sql-to-filter-by-allowable-actions/m-p/278215#M231345</guid>
      <dc:creator>mikerawlins</dc:creator>
      <dc:date>2014-06-18T21:02:05Z</dc:date>
    </item>
    <item>
      <title>Re: SQL to filter by allowable actions</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/sql-to-filter-by-allowable-actions/m-p/278216#M231346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I assume that you know you can retrieve the allowable actions with the objects by passing includeAllowableActions=true as part of the request. You'll still have to filter the result set based on those values, though, because the spec doesn't provide for a query filter based on that.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jeff&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Jul 2014 19:49:19 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/sql-to-filter-by-allowable-actions/m-p/278216#M231346</guid>
      <dc:creator>jpotts</dc:creator>
      <dc:date>2014-07-07T19:49:19Z</dc:date>
    </item>
  </channel>
</rss>

