<?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: control of available types in share UI and advanced search UI in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/control-of-available-types-in-share-ui-and-advanced-search-ui/m-p/302475#M255605</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;BR /&gt;&lt;SPAN&gt;There's nothing that I know of out of the box.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;But then the wonders of opensource make it so that you can build it yourself.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The easiest specialize-type restriction to implement would be the one based on the user. And it would only remove it from the share UI. Not block it at the background level.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The way I'd do it would be to add an optional attribute in the config where you declare your folders.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You'll then be able to define your models visibility this way:&lt;/SPAN&gt;&lt;BR /&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;&lt;BR /&gt;&amp;lt;config evaluator="string-compare" condition="DocumentLibrary"&amp;gt;&lt;BR /&gt;&amp;lt;types&amp;gt;&lt;BR /&gt; &amp;lt;type name="custom:groupAType" visible="GROUP_groupA" /&amp;gt;&lt;BR /&gt; &amp;lt;type name="custom:groupBType" visible="GROUP_groupB" /&amp;gt;&lt;BR /&gt;&amp;lt;/types&amp;gt;&lt;BR /&gt;&amp;lt;/config&amp;gt;&lt;BR /&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Then you'll need to extend both of the files that retrieves it to actually take that attribute in consideration.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;That would be&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;change-type.get.js&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;config.lib.js&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(It actually depends on your Alfresco version)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For the location-dependant specialise-type restriction, you'll also need to extend some client-side stuff because to retrieve the subtypes it currently only pass the current type, and not the current nodeRef.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Feb 2014 14:59:05 GMT</pubDate>
    <dc:creator>scouil</dc:creator>
    <dc:date>2014-02-18T14:59:05Z</dc:date>
    <item>
      <title>control of available types in share UI and advanced search UI</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/control-of-available-types-in-share-ui-and-advanced-search-ui/m-p/302474#M255604</link>
      <description>I've defined many different content models inside the same alfresco instance. Now users can change the types of the documents with the newly creadted types. They also have many new customs search forms in the "advanced search" menu.Now my questions are : - is it possible to control the visibility/av</description>
      <pubDate>Mon, 17 Feb 2014 16:23:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/control-of-available-types-in-share-ui-and-advanced-search-ui/m-p/302474#M255604</guid>
      <dc:creator>jservajean</dc:creator>
      <dc:date>2014-02-17T16:23:11Z</dc:date>
    </item>
    <item>
      <title>Re: control of available types in share UI and advanced search UI</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/control-of-available-types-in-share-ui-and-advanced-search-ui/m-p/302475#M255605</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;BR /&gt;&lt;SPAN&gt;There's nothing that I know of out of the box.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;But then the wonders of opensource make it so that you can build it yourself.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The easiest specialize-type restriction to implement would be the one based on the user. And it would only remove it from the share UI. Not block it at the background level.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The way I'd do it would be to add an optional attribute in the config where you declare your folders.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You'll then be able to define your models visibility this way:&lt;/SPAN&gt;&lt;BR /&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;&lt;BR /&gt;&amp;lt;config evaluator="string-compare" condition="DocumentLibrary"&amp;gt;&lt;BR /&gt;&amp;lt;types&amp;gt;&lt;BR /&gt; &amp;lt;type name="custom:groupAType" visible="GROUP_groupA" /&amp;gt;&lt;BR /&gt; &amp;lt;type name="custom:groupBType" visible="GROUP_groupB" /&amp;gt;&lt;BR /&gt;&amp;lt;/types&amp;gt;&lt;BR /&gt;&amp;lt;/config&amp;gt;&lt;BR /&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Then you'll need to extend both of the files that retrieves it to actually take that attribute in consideration.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;That would be&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;change-type.get.js&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;config.lib.js&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(It actually depends on your Alfresco version)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For the location-dependant specialise-type restriction, you'll also need to extend some client-side stuff because to retrieve the subtypes it currently only pass the current type, and not the current nodeRef.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2014 14:59:05 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/control-of-available-types-in-share-ui-and-advanced-search-ui/m-p/302475#M255605</guid>
      <dc:creator>scouil</dc:creator>
      <dc:date>2014-02-18T14:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: control of available types in share UI and advanced search UI</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/control-of-available-types-in-share-ui-and-advanced-search-ui/m-p/302476#M255606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks for the clue !&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I'll try something like that&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Feb 2014 16:29:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/control-of-available-types-in-share-ui-and-advanced-search-ui/m-p/302476#M255606</guid>
      <dc:creator>jservajean</dc:creator>
      <dc:date>2014-02-18T16:29:48Z</dc:date>
    </item>
  </channel>
</rss>

