File: dynamicfields.xml

package info (click to toggle)
otrs2-doc 20120224-1
  • links: PTS
  • area: main
  • in suites: wheezy
  • size: 36,060 kB
  • sloc: xml: 57,412; sh: 126; makefile: 12
file content (78 lines) | stat: -rw-r--r-- 3,621 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
<!-- $Id: dynamicfields.xml,v 1.2 2012/02/23 12:52:55 mg Exp $ -->

<chapter id="dynamicfields">
    <title>Dynamic Fields</title>
    <section id="dynamicfields-introduction">
        <title>Introduction</title>
        <para>
            A dynamic field is a special kind of field in OTRS, created to extend the
            information stored on a ticket or article. These fields are not fixed in the system and
            they can appear only in specific screens, they can be mandatory or not, and their
            representation in the screens depends on the field type defined at their creation time
            according to the data to be held by the field. For example, there are fields to hold a text, a
            date, a selection of items, etc.
        </para>
        <para>
            Dynamic fields are the evolution of TicketFreeText TicketFreeKey TicketFreeTime,
            ArticleFreeText and ArticleFreeKey fields that where commonly used in OTRS 3.0 and
            before. The limitation of these "Free Fields" was that they can be defined up to 16
            (text or dropdown) fields and 6 time fields for a ticket and 3 (text or dropdown)
            fields for each article only, not more.
        </para>
        <para>
            Now with dynamic fields the limitation in the number of fields per ticket or article is
            removed, you can create as many dynamic fields you like either for ticket or articles.
            And beyond that, the framework behind the dynamic fields is prepared to handle custom
            fields for other objects rather than just ticket and articles.
        </para>
        <para>
            This new framework that handles the dynamic fields is build using a modular approach,
            where each kind of dynamic field can be seen as a plug-in module for the framework.
            This means that the variety of dynamic fields can be easily extended by public OTRS modules,
            OTRS Feature Add-ons, OTRS custom developments, and other custom developments.
        </para>
        <para>
            The following dynamic field types are included with this release:
            <itemizedlist>
                <listitem>
                    <para>
                        Text (one line of text)
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Textarea (multiple lines of text)
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Checkbox
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Dropdown (single choice, multiple values)
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Multiselect (multiple choice, multiple values)
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Date
                    </para>
                </listitem>
                <listitem>
                    <para>
                        Date / Time
                    </para>
                </listitem>
            </itemizedlist>
        </para>
    </section>
    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="dynamicfields-configuration.xml" />
</chapter>