In the context of an Alfresco Share page rendering a node's details, a special root object named document is exposed to the FreeMarker template. This document object is a TemplateNode wrapper around the actual content node. If the node has the cm:templatable aspect applied and a presentation template is associated with it, the web script controller resolves this template's path. This path is then made available as the .template property on the document object. Therefore, the expression document.template is used to access and subsequently include this presentation template.

A. template: This is ambiguous. It could refer to the current template context but does not specifically access the presentation template associated with the document node.

B. node.template: The standard node root object (of type ScriptNode) does not have a .template property to access the associated presentation template.

C. node.document: This represents an incorrect object hierarchy. document is a root-level object, not a property of the generic node object in this context.

D. document: This expression accesses the entire document object wrapper (TemplateNode), not the specific presentation template property associated with it.

1. Alfresco Content Services 5.2 Documentation, Content Model Guide: The cm:templatable aspect is defined in the out-of-the-box content models. This aspect adds the cm:template association, which links a node to its presentation template node. The logic for document.template relies on this association being present. (See: Alfresco 5.2 Docs, systemdictionary.xml model definition for cm:templatable).

2. Default Alfresco Share Template Source Code: The default FreeMarker template for the document details page (document-details.get.html.ftl) in Alfresco 5.x explicitly uses this expression. The relevant code snippet is:

freemarker

...

This demonstrates the canonical method for checking and including a presentation template. (Source: tomcat/webapps/share/WEB-INF/classes/alfresco/site-webscripts/org/alfresco/components/document-details/document-details.get.html.ftl).

3. Alfresco Content Services 5.2 Documentation, Web Scripts: The documentation on web scripts explains that controllers (.get.js files) prepare a model for the view (.get.html.ftl file). The controller for the document details page resolves the template and places it in the model, making it accessible via the document root object. (See: Alfresco 5.2 Docs, Developing -> APIs -> Web Scripts -> Architecture and framework).