<?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 Should content be searchable when still not approved in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224350#M177480</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am a newbie on Alfresco. Trying the buit in "review &amp;amp; approve" advanced workflow. Suppose User A creates a content and initiates the advanced workflow and sends the content to user B for approval. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Now till the user B approves the content, should any other user C be able to search and locate the content ? &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I tried this scenario and found that user C is very much able to search and even check out the content. Is this behaviour correct ? What should be done if we want to prevent the content from being searched till it is approved ?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Mar 2010 13:37:21 GMT</pubDate>
    <dc:creator>viralshah</dc:creator>
    <dc:date>2010-03-10T13:37:21Z</dc:date>
    <item>
      <title>Should content be searchable when still not approved</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224350#M177480</link>
      <description>Hi,I am a newbie on Alfresco. Trying the buit in "review &amp;amp; approve" advanced workflow. Suppose User A creates a content and initiates the advanced workflow and sends the content to user B for approval. Now till the user B approves the content, should any other user C be able to search and locate</description>
      <pubDate>Wed, 10 Mar 2010 13:37:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224350#M177480</guid>
      <dc:creator>viralshah</dc:creator>
      <dc:date>2010-03-10T13:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: Should content be searchable when still not approved</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224351#M177481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The simple answer is that the search results depend on the search query.&amp;nbsp;&amp;nbsp;&amp;nbsp; And if it is a simple query like all files containing the word "sausages" then there's nothing in that query to say and don't return any documents which are subject to an approval process.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I had a quick look at the review and approve workflow and it is a very simple example workflow.&amp;nbsp;&amp;nbsp; However if you wanted to you could extend it add more buisness rules to, for example, changes the access control of the document being reviewed so that user C can't see it until it is approved or add some properties to the document which userC can query against.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Mar 2010 21:52:16 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224351#M177481</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2010-03-10T21:52:16Z</dc:date>
    </item>
    <item>
      <title>Re: Should content be searchable when still not approved</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224352#M177482</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Isn't the answer that all not all properties and content is searchable by the search-textbox and advanced search in the standard GUI? Therefore one solution could be to configure another content-type and only give that contenttype properties that are not used by the searches the standard GUI provides.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It doesn't protect from all kinds of queries that you could define in a javascript but should sheild you from those the standards gui makes. It probably have a couple of other drawbacks too. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;//Roland&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Mar 2010 08:43:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224352#M177482</guid>
      <dc:creator>buurd</dc:creator>
      <dc:date>2010-03-11T08:43:18Z</dc:date>
    </item>
    <item>
      <title>Re: Should content be searchable when still not approved</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224353#M177483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You need to think "accessibility" – a document that has not been approved is not accessible to anybody outside of the editorial cycle. You implement accessibility rules using the security model of Alfresco.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Therefore, put draft documents into a space that is restricted to the editorial group. The final stage of approval is to copy/move the approved document to a place that is more public, and will appear in the results of searches.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Mar 2010 17:21:05 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/should-content-be-searchable-when-still-not-approved/m-p/224353#M177483</guid>
      <dc:creator>invictus9</dc:creator>
      <dc:date>2010-03-19T17:21:05Z</dc:date>
    </item>
  </channel>
</rss>

