New menu for the configuration of notifications

SVN:trunk[237]
This commit is contained in:
Denis Flaven
2010-01-12 10:13:33 +00:00
parent 3b8928bf74
commit 2565d21c40

View File

@@ -997,4 +997,59 @@ text-align:left;
<parent_id>1</parent_id>
<user_id>0</user_id>
</menuNode>
<menuNode id="45">
<name>Notifications</name>
<label>Configuration of the Notifications</label>
<hyperlink>UI.php</hyperlink>
<icon_path></icon_path>
<template>&lt;div class=&quot;page_header&quot; style=&quot;padding:0.5em;&quot;&gt;
&lt;h1&gt;Configuration of the &lt;span class=&quot;hilite&quot;&gt;Notifications&lt;/span&gt;&lt;/h1&gt;
&lt;/div&gt;
&lt;itoptoggle name=&quot;Help&quot; open=&quot;true&quot;&gt;
&lt;div style=&quot;padding: 1em; font-size:1.25em;background: #E8F3CF;margin-top: 0.25em;&quot;&gt;
&lt;img src=&quot;../images/bell.png&quot; style=&quot;margin-top: -60px; margin-right: 10px; float: right;&quot;&gt;
&lt;p&gt;In iTop the notifications are fully customizable. They are based on two sets of objects: &lt;i&gt;triggers and actions&lt;/i&gt;.&lt;/p&gt;
&lt;p&gt;&lt;i&gt;&lt;b&gt;Triggers&lt;/b&gt;&lt;/i&gt; define when a notification will be executed. There are 3 types of triggers for covering 3 differents phases of an object life cycle:
&lt;ol&gt;
&lt;li&gt;the &apos;OnCreate&apos; triggers get executed when an object of the specified class is created&lt;/li&gt;
&lt;li&gt;the &apos;OnStateEnter&apos; triggers get executed before an object of the given class enters a specified state (coming from another state)&lt;/li&gt;
&lt;li&gt;the &apos;OnStateLeave&apos; triggers get executed when an object of the given class is leaving a specified state&lt;/li&gt;
&lt;/ol&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;i&gt;&lt;b&gt;Actions&lt;/b&gt;&lt;/i&gt; define the actions to be performed when the triggers execute. For now there is only one kind of action consisting in sending an email message.
Such actions also define the template to be used for sending the email as well as the other parameters of the message like the recipients, importance, etc.
&lt;/p&gt;
&lt;p&gt;To be executed, actions must be associated to triggers.
When associated with a trigger, each action is given an &apos;order&apos; number, specifying in which order the actions are to be executed.&lt;/p&gt;
&lt;/div&gt;
&lt;/itoptoggle&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;itoptabs&gt;
&lt;itoptab name=&quot;Triggers&quot;&gt;
&lt;h3&gt;Available Triggers&lt;/h3&gt;
&lt;table&gt;
&lt;tr&gt;
&lt;td style=&quot;vertical-align:top;width:50%;padding:1em;&quot;&gt;
&lt;h4&gt;When entering a state&lt;/h4&gt;
&lt;itopblock BlockClass=&quot;DisplayBlock&quot; type=&quot;list&quot; asynchronous=&quot;false&quot; encoding=&quot;text/oql&quot;&gt;SELECT TriggerOnStateEnter&lt;/itopblock&gt;
&lt;/td&gt;
&lt;td style=&quot;vertical-align:top;width:50%;padding:1em;&quot;&gt;
&lt;h4&gt;When leaving a state&lt;/h4&gt;
&lt;itopblock BlockClass=&quot;DisplayBlock&quot; type=&quot;list&quot; asynchronous=&quot;false&quot; encoding=&quot;text/oql&quot;&gt;SELECT TriggerOnStateLeave&lt;/itopblock&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;/itoptab&gt;
&lt;itoptab name=&quot;Actions&quot;&gt;
&lt;h3&gt;Available Actions&lt;/h3&gt;
&lt;itopblock BlockClass=&quot;DisplayBlock&quot; type=&quot;list&quot; asynchronous=&quot;false&quot; encoding=&quot;text/oql&quot;&gt;SELECT ActionEmail&lt;/itopblock&gt;
&lt;/itoptab&gt;
&lt;/itoptabs&gt;
</template>
<type>administrator</type>
<rank>2</rank>
<parent_id>1</parent_id>
<user_id>0</user_id>
</menuNode>
</Set>