<?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: Surf Extension - edit-metadata forms component override in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266980#M220110</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;the hasAspect evaluator is not a Surf evaluator but a Share Documentlibrary one - that is a huge difference. Surf requires a bean which is a SubComponentEvaluator type and registered via a Spring context - it would know the hasAspect evaluator, but that one is of a different type for a different purpose.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There currently is no Surf sub-component evaluator defined by default which can handle the nodeRef URL parameter and check that for a specific aspect. You would have to implement you own and properly register this in a Spring context file to be able to use it in Surf.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 May 2012 08:42:45 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2012-05-04T08:42:45Z</dc:date>
    <item>
      <title>Surf Extension - edit-metadata forms component override</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266979#M220109</link>
      <description>In the edit-metadata page I want to use a special form if the document has a specific aspect applied. For what I can tell by mere forms config you cannot do this based on aspect, only on document type.So instead looking into surf extension, if I can do something like&amp;lt;extension&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;modules&amp;amp;g</description>
      <pubDate>Thu, 03 May 2012 12:09:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266979#M220109</guid>
      <dc:creator>loftux</dc:creator>
      <dc:date>2012-05-03T12:09:28Z</dc:date>
    </item>
    <item>
      <title>Re: Surf Extension - edit-metadata forms component override</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266980#M220110</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;the hasAspect evaluator is not a Surf evaluator but a Share Documentlibrary one - that is a huge difference. Surf requires a bean which is a SubComponentEvaluator type and registered via a Spring context - it would know the hasAspect evaluator, but that one is of a different type for a different purpose.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There currently is no Surf sub-component evaluator defined by default which can handle the nodeRef URL parameter and check that for a specific aspect. You would have to implement you own and properly register this in a Spring context file to be able to use it in Surf.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 May 2012 08:42:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266980#M220110</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2012-05-04T08:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: Surf Extension - edit-metadata forms component override</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266981#M220111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I came up with a solution that I wrote about in my blog&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="http://loftux.com/2012/05/04/select-metadata-edit-form-based-on-aspect/" rel="nofollow noopener noreferrer"&gt;http://loftux.com/2012/05/04/select-metadata-edit-form-based-on-aspect/&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 May 2012 11:13:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266981#M220111</guid>
      <dc:creator>loftux</dc:creator>
      <dc:date>2012-05-04T11:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: Surf Extension - edit-metadata forms component override</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266982#M220112</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;A different approach made possible by the new flexibility in Share customization. Nice one…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Based on the use case you explained in your blog, you might have also used a form filter (and possibly a guard policy) on the Repository tier to ensure read-only behavior on a lower level, so to avoid URL-based hacks and partially redundant form configuration. But of course, as you stated, such type of security was not warranted in your case.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 May 2012 11:28:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/surf-extension-edit-metadata-forms-component-override/m-p/266982#M220112</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2012-05-04T11:28:17Z</dc:date>
    </item>
  </channel>
</rss>

