topic Re: Correct use of processTemplate in Alfresco Archive

Correct use of processTemplate

lordzoster — Thu, 20 Feb 2014 01:08:41 GMT

HalloI have an RTF freemarker template which I fill with some arbitrary data, and then save into a folder different than origin.The file saves correctly but without any modification - just the original template.Moreover, I don't understand the meaning of the node against which I am expected to call

Re: Correct use of processTemplate

mitpatoliya — Thu, 20 Feb 2014 06:00:30 GMT

save outputFile after operation
outputFile.save();

and may be you also need to change this
outputFile.content.content=result;

Re: Correct use of processTemplate

lordzoster — Wed, 26 Feb 2014 13:30:00 GMT

Thank you for replying, the output file gets already created anyway.
The point is that I cannot understand the nodes involved, even in the Javascript API cookbook example:
<em>Executes a template from the repository against the current Document node:</em>
<javascript>
var template = "<h3>Document name is ${document.name}</h3>" +
"The ID argument: ${args['id']}";
var args = new Array()
args["id"] = "01234-56789";
var result = document.processTemplate(template, args);
// save the template result content to a new node in my home space
var outputFile = userhome.createFile("output.txt");
outputFile.content = result;
</javascript>

Here we have:
1. a template;
2. an outputFile;
3. and a document "against which the template is processed". What does this mean?
What is the meaning of "executing a template against a Document node"? What's the role of the Document node the template is processed against to?
Moreover, the outputFile is identical to the template: placeholders are not getting processed, they are output as is.

Re: Correct use of processTemplate

mitpatoliya — Mon, 03 Mar 2014 07:12:39 GMT

Template+Model=New Output File
This is the ideal scenario for any template processing language.
Now in Alfresco "document" is predefined object in alfresco context which points to current node which is being processed. So, in this case it is just being used to access APIs related to template processing.