Histórico da Página
| HTML |
|---|
<div id="main-content" class="wiki-content group">
<h1 id="TemplatesdeE-mailCustomizados-Índice">Index</h1>
<p>
<style type='text/css'>/*<![CDATA[*/
div.rbtoc1412695840628 {
padding: 0px;
}
div.rbtoc1412695840628 ul {
list-style: none;
margin-left: 0px;
}
div.rbtoc1412695840628 li {
margin-left: 0px;
padding-left: 0px;
}
/*]]>*/
</style>
<div class='toc-macro rbtoc1412695840628'>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>1</span> <a
href='#TemplatesdeE-mailCustomizados-Objetivo'>Objective</a></li>
<li><span class='TOCOutline'>2</span> <a
href='#TemplatesdeE-mailCustomizados-Introdução'>Introduction</a>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>2.1</span> <a
href='#TemplatesdeE-mailCustomizados-Impactosgerais'>General
impacts</a></li>
<li><span class='TOCOutline'>2.2</span> <a
href='#TemplatesdeE-mailCustomizados-ImpactosnoscódigosJAVA'>Impacts
on JAVA codes</a></li>
<li><span class='TOCOutline'>2.3</span> <a
href='#TemplatesdeE-mailCustomizados-Impactosnosarquivosfísicosdetemplate'>Impacts
on template physical files</a></li>
<li><span class='TOCOutline'>2.4</span> <a
href='#TemplatesdeE-mailCustomizados-Impactosnoupdatedaversão1.3.0'>Impacts
on version 1.3.0 update</a></li>
</ul></li>
</ul>
</div>
</p>
<h1 id="TemplatesdeE-mailCustomizados-Objetivo">Objective</h1>
<p>The goal of this guide is to inform the impacts, solutions and
changes made in the version 1.3.0 email default templates. </p>
<h1 id="TemplatesdeE-mailCustomizados-Introdução">Introduction</h1>
<p>
<span>E-mail template codes have had their names changed to
facilitate maintenance and for the standardization of nomenclature.</span>
</p>
<p>
<span><br /></span>
</p>
<p>
<strong>Example:</strong>
</p>
<p>
An event that was called <strong>APPROVE_TASK</strong> and had the
template code <strong>TPL105</strong>, now has the code <strong>TPLAPPROVE_TASK.</strong>
Note that the nomenclature pattern is prefixed <strong>TPL</strong> +
<strong>(event code).</strong>
</p>
<p>
A file named <strong>TPL105-pt.html</strong> was renamed to <strong>TPLAPPROVE_TASK-pt.html</strong>
</p>
<p>
That new standard facilitated the maintenance of the template.
Previously it was necessary to access the <em>html</em> file to map
what template was being changed.
</p>
<p> </p>
<p> </p>
<h3 id="TemplatesdeE-mailCustomizados-Impactosgerais">General
impacts</h3>
<p>The codes and the names of the template physical files have been
changed into Fluig default.</p>
<p>The template HTML codes have been changed to follow a standard.</p>
<p>These changes can affect customers and third-party applications
that use custom templates.</p>
<div class="aui-message hint shadowed information-macro">
<p class="title">Note</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
<p>
<em>Default system events are pre-registered events on Fluig.
Events that the client created are not considered default.</em>
</p>
</div>
</div>
<div class="aui-message warning shadowed information-macro">
<p class="title">Note</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>
<em>This change affects <em>only </em>the Fluig default events
</em>
</p>
</div>
</div>
<p>   </p>
<p> </p>
<h3 id="TemplatesdeE-mailCustomizados-ImpactosnoscódigosJAVA">Impacts
on JAVA codes</h3>
<p>The functions that specified any event code need to be changed
to the new standard.</p>
<p> </p>
<p>
<strong>For example:</strong>
</p>
<p>
An event that was called <strong>APPROVE_TASK</strong> and had the
template code <strong>TPL105</strong>, now has the code <strong>TPLAPPROVE_TASK.</strong> 
</p>
<ul style="list-style-type: square;">
<li>Note that the nomenclature pattern is prefixed <strong>TPL</strong> + <strong>(event
code).</strong></li>
</ul>
<div class="aui-message hint shadowed information-macro">
<p class="title">Note</p>
<span class="aui-icon icon-hint">Icon</span>
<div class="message-content">
<p>
<em>When the code is neither specified nor found, Fluig uses
the e-mail default template.</em>
</p>
</div>
</div>
<p>
<span><br /></span>
</p>
<p>
<span>Example of JAVA calling for the event <strong>APPROVE_TASK</strong></span><span
style="font-size: 10.0pt; line-height: 13.0pt;">:</span>
</p>
<div class="code panel pdl" style="border-width: 1px;">
<div class="codeContent panelContent pdl">
<pre class="theme: Confluence; brush: java; gutter: false"
style="font-size: 12px;">notifier.notify("APPROVE_TASK", "TPL105", parameters, recipients, "text/html");</pre>
</div>
</div>
<p>
<span><br /></span>
</p>
<p>
<span>Example of the new standard:</span>
</p>
<div class="code panel pdl" style="border-width: 1px;">
<div class="codeContent panelContent pdl">
<pre class="theme: Confluence; brush: java; gutter: false"
style="font-size: 12px;">notifier.notify("APPROVE_TASK", "TPLAPPROVE_TASK", parameters, recipients, "text/html");</pre>
</div>
</div>
<p> </p>
<p>If you have questions about what the new template code is, the
following EXCEL file maps the new codes with the old ones.</p>
<p>
<a href="attachments/146969092/147097582.xlsx">Mappings of updates
to old templates</a>
</p>
<div class="aui-message warning shadowed information-macro">
<p class="title">Note</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>
<em>The templates created and customized by the customer that
are not Fluig default events have not been affected.</em>
</p>
</div>
</div>
<p> </p>
<p> </p>
<h3
id="TemplatesdeE-mailCustomizados-Impactosnosarquivosfísicosdetemplate">Impacts
on template physical files</h3>
<p>The default template files have also had their names changed.
Those who used the default now have their own template with the
following standard:</p>
<p>
A file named <strong>TPL105-pt.html</strong> of event <strong>APPROVE_TASK </strong>
was renamed to <strong>TPLAPPROVE_TASK-pt.html</strong>
</p>
<p>
The event <strong>APPROVE_TASK_RESPONSABLE,</strong> which
had no template now has the <strong>TPL<strong>APPROVE_TASK_RESPONSABLE</strong></strong>-<strong>pt.html.</strong>
</p>
<div class="aui-message warning shadowed information-macro">
<p class="title">Note</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>
<em>The templates created and customized by the customer that
are not Fluig default events have not been affected.</em>
</p>
</div>
</div>
<p>   </p>
<p> </p>
<h3 id="TemplatesdeE-mailCustomizados-Impactosnoupdatedaversão1.3.0">Impacts
on version 1.3.0 update</h3>
<p>
To update the Fluig installation to version 1.3.0, the default
templates are moved from the folder <strong>tempaltes\tpl
</strong>(template default folder) to the folder <strong><span
style="font-size: 10.0pt; line-height: 13.0pt;">templates\tplmail_backup</span></strong><span
style="font-size: 10.0pt; line-height: 13.0pt;"> and the
new default templates in the new version and new nomenclature pattern
are added again. Therefore, if the client has changed any physical
file of a default event, that file will be in the backup folder and
the client will have to update the event template again.</span>
</p>
<p>
<strong><br /></strong>
</p>
<p>
<strong>Example:</strong>
</p>
<p>
If the client, in the previous version, changed to the event <strong>CREATE_DOCUMENT</strong>
the default template file for <strong>template_create_document-pt.html.</strong> The
update process will delete this file and will replace it with the new
default file  <strong>TPLCREATE_DOCUMENT-pt.html</strong><strong> </strong>and
move the file <strong>template_create_document-pt.html </strong>to
the backup folder. 
</p>
<p>
For the user to go back to their version, it is only necessary to
update the file <strong>template_create_document-pt.html </strong>again.
</p>
<div class="aui-message warning shadowed information-macro">
<p class="title">Note</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>
<em>The templates created and customized by the customer that
are not the system default events have not been affected.</em>
</p>
</div>
</div>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
</div>
|
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas