<?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 Templating, Workflow, and Previews Question in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/templating-workflow-and-previews-question/m-p/4073#M499</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The &lt;/SPAN&gt;&lt;A href="http://www.alfresco.org/mediawiki/index.php/Template_Guide" rel="nofollow noopener noreferrer"&gt;templating system&lt;/A&gt;&lt;SPAN&gt; looks very intriguing, but raises one workflow question.&amp;nbsp; If the templates are stored in the repository (as opposed to fixed in the classpath), will any future admin component contain a preview step?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am not talking so much about having a workflow by which a template change can be rejected or approved by a higher class of user, but a step that runs a given Model against the Template, so the user can see the results before committing it to the repository?&amp;nbsp; Setting aside malicious users, it is still simple either in Freemarker or XSLT for an inexperienced user to get unexpected results, or to write a template that throws some manner of exception.&amp;nbsp; Will there be any means for admins to catch these mistakes before committing them, or, if this is a concern, is the best option to keep templates in the classpath instead of allowing them to be administerable?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Greg Ludington&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Oct 2005 16:34:53 GMT</pubDate>
    <dc:creator>gludington</dc:creator>
    <dc:date>2005-10-04T16:34:53Z</dc:date>
    <item>
      <title>Templating, Workflow, and Previews Question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/templating-workflow-and-previews-question/m-p/4073#M499</link>
      <description>The templating system looks very intriguing, but raises one workflow question.&amp;nbsp; If the templates are stored in the repository (as opposed to fixed in the classpath), will any future admin component contain a preview step?I am not talking so much about having a workflow by which a template change can</description>
      <pubDate>Tue, 04 Oct 2005 16:34:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/templating-workflow-and-previews-question/m-p/4073#M499</guid>
      <dc:creator>gludington</dc:creator>
      <dc:date>2005-10-04T16:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: Templating, Workflow, and Previews Question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/templating-workflow-and-previews-question/m-p/4074#M500</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;That's an interesting question. I see what you mean, if someone edits an active template and then saves it back to the repo then anything using the template will immediately change without a chance for previewing it first. So yes, I think we will have to think about some way to preview changes - as otherwise it will cause the issues you highlight.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm not sure what the best option is yet, I think having the templates in the repo is very powerful, but obviously it creates the issues you mention, so a preview function would probably work best.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Oct 2005 09:47:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/templating-workflow-and-previews-question/m-p/4074#M500</guid>
      <dc:creator>kevinr</dc:creator>
      <dc:date>2005-10-06T09:47:42Z</dc:date>
    </item>
  </channel>
</rss>

