As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
<extension> <modules> <module> <id>Customization applied to sites' document library.</id> <auto-deploy>true</auto-deploy> <components> <component> <scope>template</scope> <region-id>title</region-id> <source-id>site/{site}/documentlibrary</source-id> <sub-components> <sub-component id="default"> <evaluations> <evaluation id="guaranteedToHide"> <render>false</render> </evaluation> </evaluations> </sub-component> </sub-components> </component> </components> </module> </modules> </extension>
Hello,the source ID for the documentlibrary template is simply "documentlibrary", not the ID of the full page. If you use this for a template-scoped sub-component you should find it in working order.RegardsAxel
<extension> <modules> <module> <id>Customizations applied to sites' document library.</id> <auto-deploy>true</auto-deploy> <components> <component> <scope>template</scope> <region-id>title</region-id> <source-id>documentlibrary</source-id> <sub-components> <sub-component id="default"> <evaluations> <evaluation id="guaranteedToHide"> <render>false</render> </evaluation> </evaluations> </sub-component> </sub-components> </component> </components> </module> </modules> </extension>
Why in the examples I have taken as model […]the value of <source-id> is defined with the ID of the full page rather than simply as you have said? The only difference I appreciate between the documentation tutorial and my scenario is the scope. The question would be actually, when should be used the full source id and when not and why?