[otrs-cvs] SystemMonitoring/doc/en SystemMonitoring.xml,1.5,1.6
"CVS commits notifications of OTRS.org" <[email protected]> Tue, 28 May 2013 09:49:41 +0000
| Newsgroups | gmane.comp.otrs.cvs |
|---|---|
| Message-ID | <[email protected]> |
Comments:
Update of /home/cvs/SystemMonitoring/doc/en
In directory lancelot:/tmp/cvs-serv12350/doc/en
Modified Files:
SystemMonitoring.xml
Log Message:
Added documentation for missnaming of dynamic fields and error messages for missnamed dynamic fields.
Author: rs
Index: SystemMonitoring.xml
===================================================================
RCS file: /home/cvs/SystemMonitoring/doc/en/SystemMonitoring.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -2 -u -d -r1.5 -r1.6
--- SystemMonitoring.xml 28 May 2013 09:47:58 -0000 1.5
+++ SystemMonitoring.xml 28 May 2013 09:49:36 -0000 1.6
@@ -210,5 +210,5 @@
A dynamic field (type ticket) to store the affected host.
The field name have to be named like free text fields (TicketFreeTextField[1..16]) because of downward compatibility.
- For example: TicketFreeTextField1.
+ For example: '1' for TicketFreeTextField1.
</para>
<para>Default: '1'</para>
@@ -232,5 +232,5 @@
A dynamic field (type ticket) to store the service.
The field name have to be named like free text fields (TicketFreeTextField[1..16]) because of downward compatibility.
- For example: TicketFreeTextField2.
+ For example: '2' for TicketFreeTextField2.
</para>
<para>Default: '2'</para>
@@ -241,5 +241,5 @@
A dynamic field (type article) to store the state.
The field name have to be named like free text fields (ArticleFreeTextField[1..16]) because of downward compatibility.
- For example: ArticleFreeTextField1.
+ For example: '1' for ArticleFreeTextField1.
</para>
<para>Default: '1'</para>
---------------------------------------------------------------------
OTRS mailing list: cvs-log - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/cvs-log
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/cvs-log