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 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459
|
<?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-configuration.xml,v 1.4 2012/02/23 12:52:55 mg Exp $ -->
<section id="dynamicfields-configuration">
<title>Configuration</title>
<para>
By default, a clean installation of OTRS 3.1.x does not include any dynamic fields. If you
plan to use such fields in tickets or articles you need to create dynamic fields.
</para>
<para>
An updated installation from OTRS 3.0.x will have all the old "free fields" created as
dynamic fields for compatibility and data preservation. The following is the list of
dynamic fields that are created during the migration from OTRS 3.0.x to 3.1.x.
</para>
<para>
<itemizedlist>
<listitem>
<para>
TicketFreeKey[1-16] (TicketFreeKey1, TicketFreeKey2 ... TicketFreeKey16)
</para>
</listitem>
<listitem>
<para>
TicketFreeText[1-16]
</para>
</listitem>
<listitem>
<para>
TicketFreeTime[1-6]
</para>
</listitem>
<listitem>
<para>
ArticleFreeKey[1-16]
</para>
</listitem>
<listitem>
<para>
ArticleFreeText[1-16]
</para>
</listitem>
</itemizedlist>
</para>
<note>
<para>
During the migration procedure from OTRS 3.0.x to OTRS 3.1.x all the old
"free fields" data and configuration are migrated to the new dynamic fields
architecture. Any custom development around the old "free fields" has to be
updated to use the new dynamic field framework.
</para>
<para>
The migration of the configuration include the field itself and the screen
configurations to hide, show or show field as mandatory for each screen.
</para>
</note>
<para>
The configuration of a dynamic field is split in two parts, to add a new dynamic field or
manage an existing one you need to navigate into the "Admin" panel in the "Dynamic Fields"
link. To show, show as mandatory or hide a dynamic field in one screen you need to change
the OTRS settings in the "SysConfig" screen.
</para>
<section id="dynamicfields-configuration-add">
<title>Adding a Dynamic Field</title>
<para>
Click in the "Admin" button located in the navigation bar, then click on the "Dynamic
Field" link inside "Ticket Settings" box located in the lower center of the screen.
The dynamic fields overview will display as follows:
</para>
<para>
<screenshot>
<screeninfo>Dynamic fields overview screen, empty</screeninfo>
<graphic srccredit="Adminarea dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-overview-empty.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic fields overview screen, empty.</emphasis>
</para>
<para>
Notice that this screen will change as you add more dynamic fields to list all created
dynamic fields. This screen might already have some fields if the installation was
updated from an older version of OTRS.
</para>
<para>
The Actions in the side bar at the left of the screen describes two possibilities:
Article and Ticket, each one has it's own dropdown selection of dynamic fields.
</para>
<note>
<para>
The installation of an OTRS package could add more objects to the Action side bar.
</para>
</note>
<itemizedlist>
<para>
The general procedure to create a dynamic field is:
</para>
<listitem>
<para>
Click on the desired dynamic field object dropdown in the Action side bar.
</para>
</listitem>
<listitem>
<para>
Click on the dynamic field type that you want to add from the list.
</para>
</listitem>
<listitem>
<para>
Fill the configuration.
</para>
</listitem>
<listitem>
<para>
Save.
</para>
</listitem>
</itemizedlist>
<para>
The configuration dialogs for the dynamic fields are split in two parts, the upper
section is common among all the fields and the lower part might be different from one
type of dynamic field to another.
</para>
<itemizedlist>
<para>
General dynamic field settings:
</para>
<listitem>
<para>
Name: Mandatory, unique, only letters and numbers are allowed.
</para>
<para>
This is the internal name of the field, used for example to show or hide a
field in one screen. Any modification on field name (not recommended) will need
manual a update on the "SysConfig" settings where the field is referenciated.
</para>
</listitem>
<listitem>
<para>
Label: Mandatory.
</para>
<para>
This is field name to be displayed in the screens, it supports translations.
</para>
<note>
<para>
Label translations have to be added manually to language translations files.
</para>
</note>
</listitem>
<listitem>
<para>
Field order: Mandatory.
</para>
<para>
Defines the relative order in which the field will be displayed in the screen,
by default each new field has the last position, a change in this setting will
affect the other of the other created dynamic fields.
</para>
</listitem>
<listitem>
<para>
Validity: Mandatory.
</para>
<para>
An invalid dynamic field will not be displayed in any screen, no matter if is
configured to displayed.
</para>
</listitem>
<listitem>
<para>
Field type: Mandatory, Read only.
</para>
<para>
Shows the current selected field type.
</para>
</listitem>
<listitem>
<para>
Object type: Mandatory, Read only.
</para>
<para>
Shows the scope of field.
</para>
</listitem>
</itemizedlist>
<note>
<para>
To illustrate each specific field type settings a few fields will be added in our example. These new
fields will be referenciated in later sections.
</para>
<para>
For the following examples all the dynamic fields will be created for the Ticket object
if you need to create a dynamic field for Article object, just chose the field from the
Article dropdown list.
</para>
</note>
<table>
<title>The following fields will be added into the system:</title>
<tgroup cols='3' align='left' colsep='1' rowsep='1'>
<thead>
<row>
<entry>Name</entry>
<entry>Label</entry>
<entry>Type</entry>
</row>
</thead>
<tbody>
<row>
<entry>Field1</entry>
<entry>My Field 1</entry>
<entry>Text</entry>
</row>
<row>
<entry>Field2</entry>
<entry>My Field 2</entry>
<entry>Textarea</entry>
</row>
<row>
<entry>Field3</entry>
<entry>My Field 3</entry>
<entry>Checkbox</entry>
</row>
<row>
<entry>Field4</entry>
<entry>My Field 4</entry>
<entry>Dropdown</entry>
</row>
<row>
<entry>Field5</entry>
<entry>My Field 5</entry>
<entry>Multiselect</entry>
</row>
<row>
<entry>Field6</entry>
<entry>My Field 5</entry>
<entry>Date</entry>
</row>
<row>
<entry>Field7</entry>
<entry>My Field 6</entry>
<entry>Date / Time</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section id="dynamicfields-configuration-text">
<title>Text Dynamic Field Configuration</title>
<para>
Text dynamic field is used to store a single line string.
</para>
<itemizedlist>
<para>
Text dynamic field settings:
</para>
<listitem>
<para>
Default value: Optional.
</para>
<para>
This is the value to be shown by default in the edit screens (like New Phone
Ticket or Ticket Compose).
</para>
</listitem>
<listitem>
<para>
Show link: Optional.
</para>
<para>
If set, the field value will be converted into a clickable link for
display screens (like ticket zoom or overviews).
</para>
<para>
For example, if "Show link" is set to "http://www.otrs.com", clicking on the
filled value will make your browser to open the OTRS web page.
</para>
<note>
<para>
The use of $LQData{"NameX"} in the Set link value, where NameX is the
name of the field will add the field value as part of the link
reference.
</para>
</note>
</listitem>
</itemizedlist>
<para>
<screenshot>
<screeninfo>Dynamic field Text configuration dialog</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-configuration-text.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic field Text configuration dialog.</emphasis>
</para>
</section>
<section id="dynamicfields-configuration-textarea">
<title>Textarea Dynamic Field Configuration</title>
<para>
Textarea dynamic field is used to store a multiple line string.
</para>
<itemizedlist>
<para>
Textarea dynamic field settings:
</para>
<listitem>
<para>
Number of rows: Optional, integer.
</para>
<para>
Used to define the height of the field in the edit screens (like New Phone
Ticket or Ticket Compose).
</para>
</listitem>
<listitem>
<para>
Number of cols: Optional, Integer.
</para>
<para>
This is value is used to define the width of the field in the edit screens.
</para>
</listitem>
<listitem>
<para>
Default value: Optional.
</para>
<para>
This is the value to be shown by default in the edit screens (it can be a
multiple line text).
</para>
</listitem>
</itemizedlist>
<para>
<screenshot>
<screeninfo>Dynamic field Textarea configuration dialog</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-configuration-textarea.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic field Textarea configuration dialog.</emphasis>
</para>
</section>
<section id="dynamicfields-configuration-checkbox">
<title>Checkbox Dynamic Field Configuration</title>
<para>
Checkbox dynamic field is used to store true or false value, represented by a checked
or unchecked check box.
</para>
<itemizedlist>
<para>
Checkbox dynamic field settings:
</para>
<listitem>
<para>
Default value: Mandatory.
</para>
<para>
This is the value to be shown by default in the edit screens (like New Phone
Ticket or Ticket Compose), the default value for this field is closed selection
that can be Checked or Unchecked.
</para>
</listitem>
</itemizedlist>
<para>
<screenshot>
<screeninfo>Dynamic field Checkbox configuration dialog</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-configuration-checkbox.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic field Checkbox configuration dialog.</emphasis>
</para>
</section>
<section id="dynamicfields-configuration-dropdown">
<title>Dropdown Dynamic Field Configuration</title>
<para>
Dropdown dynamic field is used to store a single value, from a closed list.
</para>
<itemizedlist>
<para>
Dropdown dynamic field settings:
</para>
<listitem>
<para>
Possible values: Mandatory.
</para>
<para>
List of values to choose. when add a new value is necessary to specify the
Key (internal value) and the Value (display value).
</para>
</listitem>
<listitem>
<para>
Default value: Optional.
</para>
<para>
This is the value to be show by default in the edit screens (like New Phone
Ticket or Ticket Compose), the default value for this field is closed selection
defined by the Possible values.
</para>
</listitem>
<listitem>
<para>
Add empty value: Mandatory, (Yes / No).
</para>
<para>
If this option is activated an extra value is defined to show a "-" in the list
of possible values, this special value is empty internally.
</para>
</listitem>
<listitem>
<para>
Translatable values: Mandatory, (Yes / No).
</para>
<para>
This setting is used mark the possible values of this field to be translated.
Only the display values are translated, internal values are not affected, the
translation of the values needs to be manually added to the language files.
</para>
</listitem>
<listitem>
<para>
Show link: Optional.
</para>
<para>
If set, the field value will be converted into a clickable HTP link for
display screens (like Zoom or overviews).
</para>
<para>
For example, if Show link is set to "http://www.otrs.com", clicking on the
filed value will make your browser to open the OTRS web page.
</para>
<note>
<para>
The use of $LQData{"NameX"} in the Set link value, where NameX is the
name of the field will add the field value as part of the link
reference.
</para>
</note>
</listitem>
</itemizedlist>
<para>
<screenshot>
<screeninfo>Dynamic field Dropdown configuration dialog</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-configuration-dropdown.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic field Dropdown configuration dialog.</emphasis>
</para>
</section>
<section id="dynamicfields-configuration-multiselect">
<title>Multiselect Dynamic Field Configuration</title>
<para>
Multiselect dynamic field is used to store a multiple values, from a closed list.
</para>
<itemizedlist>
<para>
Multiselect dynamic field settings:
</para>
<listitem>
<para>
Possible values: Mandatory.
</para>
<para>
List of values to choose. when add a new value is necessary to specify the
Key (internal value) and the Value (display value).
</para>
</listitem>
<listitem>
<para>
Default value: Optional.
</para>
<para>
This is the value to be show by default in the edit screens (like New Phone
Ticket or Ticket Compose), the default value for this field is closed selection
defined by the Possible values.
</para>
</listitem>
<listitem>
<para>
Add empty value: Mandatory, (Yes / No).
</para>
<para>
If this option is activated an extra value is defined to show a "-" in the list
of possible values, this special value is empty internally.
</para>
</listitem>
<listitem>
<para>
Translatable values: Mandatory, (Yes / No).
</para>
<para>
This setting is used mark the possible values of this field to be translated.
Only the display values are translated, internal values are not affected, the
translation of the values needs to be manually added to the language files.
</para>
</listitem>
</itemizedlist>
<para>
<screenshot>
<screeninfo>Dynamic field Multiselect configuration dialog</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-configuration-multiselect.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic field Multiselect configuration dialog.</emphasis>
</para>
</section>
<section id="dynamicfields-configuration-date">
<title>Date Dynamic Field Configuration</title>
<para>
Date dynamic field is used to store a date value (Day, Month and Year).
</para>
<itemizedlist>
<para>
Date dynamic field settings:
</para>
<listitem>
<para>
Default date difference: Optional, Integer.
</para>
<para>
Number of seconds (positive or negative) between the current date and the
selected date to be show by default in the edit screens (like New Phone
Ticket or Ticket Compose).
</para>
</listitem>
<listitem>
<para>
Define years period: Mandatory (Yes / No).
</para>
<para>
Used to set a defined number of years in past and future from current date in
the year select of this field, If set to Yes the following options are
available:
</para>
<para>
<itemizedlist>
<listitem>
<para>
Years in the past: Optional, Positive integer.
</para>
<para>
Define the number of years in past from current day to display in
the year selection for this dined in edit screens.
</para>
</listitem>
<listitem>
<para>
Years in the future: Optional, Positive integer.
</para>
<para>
Define the number of years in future from current day to display in
the year selection for this dined in edit screens.
</para>
</listitem>
</itemizedlist>
</para>
</listitem>
<listitem>
<para>
Show link: Optional.
</para>
<para>
If set, the field value will be converted into a clickable HTP link for
display screens (like Zoom or overviews).
</para>
<para>
For example, if Show link is set to "http://www.otrs.com", clicking on the
filed value will make your browser to open the OTRS web page.
</para>
<note>
<para>
The use of $LQData{"NameX"} in the Set link value, where NameX is the
name of the field will add the field value as part of the link
reference.
</para>
</note>
</listitem>
</itemizedlist>
<para>
<screenshot>
<screeninfo>Dynamic field Date configuration dialog</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-configuration-date.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic field Date configuration dialog.</emphasis>
</para>
</section>
<section id="dynamicfields-configuration-datetime">
<title>Date / Time Dynamic Field Configuration</title>
<para>
Date / Time dynamic field is used to store a date time value (Minute, Hour, Day, Month
and Year).
</para>
<itemizedlist>
<para>
Date / Time dynamic field settings:
</para>
<listitem>
<para>
Default date difference: Optional, Integer.
</para>
<para>
Number of seconds (positive or negative) between the current date and the
selected date to be show by default in the edit screens (like New Phone
Ticket or Ticket Compose).
</para>
</listitem>
<listitem>
<para>
Define years period: Mandatory (Yes / No).
</para>
<para>
Used to set a defined number of years in past and future from current date in
the year select of this field, If set to Yes the following options are
available:
</para>
<para>
<itemizedlist>
<listitem>
<para>
Years in the past: Optional, Positive integer.
</para>
<para>
Define the number of years in past from current day to display in
the year selection for this dined in edit screens.
</para>
</listitem>
<listitem>
<para>
Years in the future: Optional, Positive integer.
</para>
<para>
Define the number of years in future from current day to display in
the year selection for this dined in edit screens.
</para>
</listitem>
</itemizedlist>
</para>
</listitem>
<listitem>
<para>
Show link: Optional.
</para>
<para>
If set, the field value will be converted into a clickable HTP link for
display screens (like Zoom or overviews).
</para>
<para>
For example, if Show link is set to "http://www.otrs.com", clicking on the
filed value will make your browser to open the OTRS web page.
</para>
<note>
<para>
The use of $LQData{"NameX"} in the Set link value, where NameX is the
name of the field will add the field value as part of the link
reference.
</para>
</note>
</listitem>
</itemizedlist>
<para>
<screenshot>
<screeninfo>Dynamic field Date / Time configuration dialog</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-configuration-datetime.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic field Date / Time configuration dialog.</emphasis>
</para>
</section>
<section id="dynamicfields-configuration-edit">
<title>Editing a Dynamic Field</title>
<para>
A filled dynamic field overview screen (with the previous examples) should look like:
</para>
<para>
<screenshot>
<screeninfo>Dynamic field overview screen filled with sample data</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-overview-filled.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Dynamic field overview screen filled with sample data.</emphasis>
</para>
<para>
To change or edit a dynamic field you must have at least one field defined, select an
already added field from the dynamic fields overview screen and update it's settings.
</para>
<note>
<para>
Not all the dynamic field settings can be changed, the Field type and Object type
are fixed from the selection of the field and they can't be changed.
</para>
<para>
It is not recommended to change the field internal name, but the label can be
changed at any time. If internal name is changed all "SysConfig" settings that
has a reference to that particular field needs to be updated as well as user
preferences (if defined).
</para>
</note>
</section>
<section id="dynamicfields-configuration-show">
<title>Showing a Dynamic Field on a Screen</title>
<para>
To display a dynamic field on a particular screen there are two mandatory conditions:
</para>
<orderedlist>
<listitem>
<para>
The dynamic field must be valid.
</para>
</listitem>
<listitem>
<para>
The dynamic field must be set to 1 or 2 in the configuration of the screen.
</para>
</listitem>
</orderedlist>
<itemizedlist>
<para>
Follow this steps to show a dynamic field in a screen
</para>
<listitem>
<para>
Be sure that the dynamic field is set to valid, you can see the validity of the
field from the dynamic field overview screen. Set to valid by editing the field
if necessary.
</para>
</listitem>
<listitem>
<para>
Open the "sysconfig" and select "Ticket" from the dropdown list in the Actions
side bar located in the left part of the screen.
</para>
<note>
<para>
You can also search for "DynamicField" in the search box above or the
"sysconfig" key directly if you already know it.
</para>
</note>
</listitem>
<listitem>
<para>
Locate the setting sub-group for the screen that you are looking for and click
on it. For example "Frontend::Agent::Ticket::ViewPhoneNew".
</para>
</listitem>
<listitem>
<para>
Search for the setting that ends with "###DynamicField". For example
"Ticket::Frontend::AgentTicketPhone###DynamicField".
</para>
</listitem>
<listitem>
<para>
If the setting is empty or does not have the required dynamic filed name, click
on the "+" button to add a new entry. For example Key: Field1, Content: 1.
</para>
<para>
If the setting already has the dynamic field name listed be sure that is set to
"1" to display the field or to "2" to display it as mandatory.
</para>
</listitem>
<listitem>
<para>
Save the configuration by clicking in the "Update" button and the bottom of the
screen and navigate to the screen where you want the field to be displayed.
</para>
</listitem>
</itemizedlist>
<section id="dynamicfields-configuration-show-examples">
<title>Show Examples</title>
<para>
The following are "sysconfig" configurations examples to show or hide dynamic
fields on different screens.
</para>
<para>
<example id="Field1-PhoneTicket-Normal">
<title>Activate Field1 in New Phone Ticket Screen.</title>
<para>
<itemizedlist>
<listitem>
<para>
<emphasis>Group:</emphasis>
Ticket
</para>
</listitem>
<listitem>
<para>
<emphasis>Sub-group:</emphasis>
Frontend::Agent::Ticket::ViewPhoneNew
</para>
</listitem>
<listitem>
<para>
<emphasis>Setting:</emphasis>
Ticket::Frontend::AgentTicketPhone###DynamicField
</para>
</listitem>
<listitem>
<para>
<emphasis>Value:</emphasis>
</para>
<para>
<informaltable>
<thead>
<row>
<entry>Key</entry>
<entry>Content</entry>
</row>
</thead>
<tbody>
<row>
<entry>Field1</entry>
<entry>1</entry>
</row>
</tbody>
</informaltable>
</para>
</listitem>
</itemizedlist>
</para>
<para>
<screenshot>
<screeninfo>Field1 in New Phone Ticket Screen.</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-agentticketphone-field1.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Field1 in New Phone Ticket Screen.</emphasis>
</para>
</example>
</para>
<para>
<example id="Field1-PhoneTicket-Mandatory">
<title>Activate Field1 in New Phone Ticket Screen as mandatory.</title>
<para>
<itemizedlist>
<listitem>
<para>
<emphasis>Group:</emphasis>
Ticket
</para>
</listitem>
<listitem>
<para>
<emphasis>Sub-group:</emphasis>
Frontend::Agent::Ticket::ViewPhoneNew
</para>
</listitem>
<listitem>
<para>
<emphasis>Setting:</emphasis>
Ticket::Frontend::AgentTicketPhone###DynamicField
</para>
</listitem>
<listitem>
<para>
<emphasis>Value:</emphasis>
</para>
<para>
<informaltable>
<thead>
<row>
<entry>Key</entry>
<entry>Content</entry>
</row>
</thead>
<tbody>
<row>
<entry>Field1</entry>
<entry>2</entry>
</row>
</tbody>
</informaltable>
</para>
</listitem>
</itemizedlist>
</para>
<para>
<screenshot>
<screeninfo>Field1 in New Phone Ticket Screen as mandatory.</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-agentticketphone-field1-mandatory.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Field1 in New Phone Ticket Screen as mandatory.</emphasis>
</para>
</example>
</para>
<para>
<example id="AllFields-PhoneTicket">
<title>Activate several fields in New Phone Ticket Screen.</title>
<para>
<itemizedlist>
<listitem>
<para>
<emphasis>Group:</emphasis>
Ticket
</para>
</listitem>
<listitem>
<para>
<emphasis>Sub-group:</emphasis>
Frontend::Agent::Ticket::ViewPhoneNew
</para>
</listitem>
<listitem>
<para>
<emphasis>Setting:</emphasis>
Ticket::Frontend::AgentTicketPhone###DynamicField
</para>
</listitem>
<listitem>
<para>
<emphasis>Value:</emphasis>
</para>
<para>
<informaltable>
<thead>
<row>
<entry>Key</entry>
<entry>Content</entry>
</row>
</thead>
<tbody>
<row>
<entry>Field1</entry>
<entry>1</entry>
</row>
<row>
<entry>Field2</entry>
<entry>1</entry>
</row>
<row>
<entry>Field3</entry>
<entry>1</entry>
</row>
<row>
<entry>Field4</entry>
<entry>1</entry>
</row>
<row>
<entry>Field5</entry>
<entry>1</entry>
</row>
<row>
<entry>Field6</entry>
<entry>1</entry>
</row>
<row>
<entry>Field7</entry>
<entry>1</entry>
</row>
</tbody>
</informaltable>
</para>
</listitem>
</itemizedlist>
</para>
<para>
<screenshot>
<screeninfo>Several fields in New Phone Ticket Screen as mandatory.</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-agentticketphone-allfields.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Several fields in New Phone Ticket Screen as mandatory.</emphasis>
</para>
</example>
</para>
<para>
<example id="SomeFields-PhoneTicket">
<title>Deactivate some fields in New Phone Ticket Screen.</title>
<para>
<itemizedlist>
<listitem>
<para>
<emphasis>Group:</emphasis>
Ticket
</para>
</listitem>
<listitem>
<para>
<emphasis>Sub-group:</emphasis>
Frontend::Agent::Ticket::ViewPhoneNew
</para>
</listitem>
<listitem>
<para>
<emphasis>Setting:</emphasis>
Ticket::Frontend::AgentTicketPhone###DynamicField
</para>
</listitem>
<listitem>
<para>
<emphasis>Value:</emphasis>
</para>
<para>
<informaltable>
<thead>
<row>
<entry>Key</entry>
<entry>Content</entry>
</row>
</thead>
<tbody>
<row>
<entry>Field1</entry>
<entry>1</entry>
</row>
<row>
<entry>Field2</entry>
<entry>0</entry>
</row>
<row>
<entry>Field3</entry>
<entry>1</entry>
</row>
<row>
<entry>Field4</entry>
<entry>0</entry>
</row>
<row>
<entry>Field5</entry>
<entry>1</entry>
</row>
<row>
<entry>Field6</entry>
<entry>0</entry>
</row>
<row>
<entry>Field7</entry>
<entry>1</entry>
</row>
</tbody>
</informaltable>
</para>
</listitem>
</itemizedlist>
</para>
<para>
<screenshot>
<screeninfo>Some deactivated fields in New Phone Ticket Screen as mandatory.</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-agentticketphone-somefields.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Some deactivated fields in New Phone Ticket Screen as mandatory.</emphasis>
</para>
</example>
</para>
<para>
<example id="Field1-TicketZoom">
<title>Activate Field1 in Ticket Zoom Screen.</title>
<para>
<itemizedlist>
<listitem>
<para>
<emphasis>Group:</emphasis>
Ticket
</para>
</listitem>
<listitem>
<para>
<emphasis>Sub-group:</emphasis>
Frontend::Agent::Ticket::ViewZoom
</para>
</listitem>
<listitem>
<para>
<emphasis>Setting:</emphasis>
Ticket::Frontend::AgentTicketZoom###DynamicField
</para>
</listitem>
<listitem>
<para>
<emphasis>Value:</emphasis>
</para>
<para>
<informaltable>
<thead>
<row>
<entry>Key</entry>
<entry>Content</entry>
</row>
</thead>
<tbody>
<row>
<entry>Field1</entry>
<entry>1</entry>
</row>
</tbody>
</informaltable>
</para>
</listitem>
</itemizedlist>
</para>
<para>
<screenshot>
<screeninfo>Field1 in Ticket Zoom Screen.</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-agentticketzoom-field1.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Field1 in Ticket Zoom Screen.</emphasis>
</para>
</example>
</para>
<para>
<example id="Field1-TicketOverviewSmall">
<title>Activate Field1 in Ticket Overview Small Screens.</title>
<para>
<itemizedlist>
<listitem>
<para>
<emphasis>Group:</emphasis>
Ticket
</para>
</listitem>
<listitem>
<para>
<emphasis>Sub-group:</emphasis>
Frontend::Agent::TicketOverview
</para>
</listitem>
<listitem>
<para>
<emphasis>Setting:</emphasis>
Ticket::Frontend::OverviewSmall###DynamicField
</para>
</listitem>
<listitem>
<para>
<emphasis>Value:</emphasis>
</para>
<para>
<informaltable>
<thead>
<row>
<entry>Key</entry>
<entry>Content</entry>
</row>
</thead>
<tbody>
<row>
<entry>Field1</entry>
<entry>1</entry>
</row>
</tbody>
</informaltable>
</para>
</listitem>
</itemizedlist>
</para>
<para>
<screenshot>
<screeninfo>Field1 in Ticket Overview Small Screen.</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-ticketoverviewsmall-field1.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Field1 in Ticket Overview Small Screen.</emphasis>
</para>
<para>
This setting affects: Escalation View, Locked View, Queue View, Responsible
View, Status View and Watch View screens.
</para>
</example>
</para>
</section>
</section>
<section id="dynamicfields-configuration-event-defaut">
<title>Setting a Default Value by a Ticket Event Module</title>
<para>
A ticket event (e.g. TicketCreate) can trigger a value set for a certain field, if the
field does not have a value yet.
</para>
<note>
<para>
By using this method this default value, is not seen in the edit screen
(e.g. New Phone Ticket) since the value is set after the creation of the ticket.
</para>
</note>
<para>
To activate this feature is necessary to enable the following setting:
"Ticket::EventModulePost###TicketDynamicFieldDefault".
</para>
<example id="Field1-EventDefault">
<title>Activate Field1 in TicketCreate event.</title>
<para>
<itemizedlist>
<listitem>
<para>
<emphasis>Group:</emphasis>
Ticket
</para>
</listitem>
<listitem>
<para>
<emphasis>Sub-group:</emphasis>
Core::TicketDynamicFieldDefault
</para>
</listitem>
<listitem>
<para>
<emphasis>Setting:</emphasis>
Ticket::TicketDynamicFieldDefault###Element1
</para>
<note>
<para>
This configuration can be set in any of the 16
Ticket::TicketDynamicFieldDefault###Element settings.
</para>
<para>
If more that 16 fields needs to be set up a custom XML file must
be places in $OTRS_HOME/Kernel/Config/files directory to extend
this feature.
</para>
</note>
</listitem>
<listitem>
<para>
<emphasis>Value:</emphasis>
</para>
<para>
<informaltable>
<thead>
<row>
<entry>Key</entry>
<entry>Content</entry>
</row>
</thead>
<tbody>
<row>
<entry>Event</entry>
<entry>TicketCreate</entry>
</row>
<row>
<entry>Name</entry>
<entry>Field1</entry>
</row>
<row>
<entry>Value</entry>
<entry>a new value</entry>
</row>
</tbody>
</informaltable>
</para>
</listitem>
</itemizedlist>
</para>
</example>
</section>
<section id="dynamicfields-configuration-preferences-defaut">
<title>Set a Default Value by User Preferences</title>
<para>
The dynamic field default value can be overwritten with a user defined value stored in
the user preferences.
</para>
<para>
Using this method, the default value of the field will be shown on any screen where the
field is activated (if the field does not have already a different value).
</para>
<para>
The "sysconfig" setting "PreferencesGroups###DynamicField" located in the
"Frontend::Agent::Preferences" Sub-group. This setting is an example of how to create
an entry in the User Preferences screen to set an exclusive dynamic field default value
for the selected user. The limitation of this setting is that it only admits one
dynamic field. if two or more fields will use this feature is necessary to create a
custom XML configuration file to add more settings similar to this one.
</para>
<note>
<para>
Remember, if more settings are added in a new XML each setting name needs to be
unique in the system and different than "PreferencesGroups###DynamicField". for
example: PreferencesGroups###101-DynamicField-Field1,
PreferencesGroups###102-DynamicField-Field2, PreferencesGroups###My-Field1,
PreferencesGroups###My-Field2, etc.
</para>
</note>
<example id="Field1-UserPreference">
<title>Activate Field1 in the User preferences.</title>
<para>
<itemizedlist>
<listitem>
<para>
<emphasis>Group:</emphasis>
Ticket
</para>
</listitem>
<listitem>
<para>
<emphasis>Sub-group:</emphasis>
Frontend::Agent::Preferences
</para>
</listitem>
<listitem>
<para>
<emphasis>Setting:</emphasis>
PreferencesGroups###101-DynamicField-Field1
</para>
</listitem>
<listitem>
<para>
<emphasis>Value:</emphasis>
</para>
<para>
<informaltable>
<thead>
<row>
<entry>Key</entry>
<entry>Content</entry>
</row>
</thead>
<tbody>
<row>
<entry>Event</entry>
<entry>TicketCreate</entry>
</row>
<row>
<entry>Active</entry>
<entry>1</entry>
</row>
<row>
<entry>Block</entry>
<entry>Input</entry>
</row>
<row>
<entry>Column</entry>
<entry>Other Settings</entry>
</row>
<row>
<entry>Data:</entry>
<entry>$Env{"UserDynamicField_Field1"}</entry>
</row>
<row>
<entry>Key:</entry>
<entry>My Field 1</entry>
</row>
<row>
<entry>Label:</entry>
<entry>Default value for: My Field 1</entry>
</row>
<row>
<entry>Module:</entry>
<entry>Kernel::Output::HTML::PreferencesGeneric</entry>
</row>
<row>
<entry>PrefKey:</entry>
<entry>UserDynamicField_Field1</entry>
</row>
<row>
<entry>Prio:</entry>
<entry>7000</entry>
</row>
</tbody>
</informaltable>
</para>
</listitem>
</itemizedlist>
</para>
<para>
<screenshot>
<screeninfo>Field1 in User preferences screen.</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-userpreferences.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Field1 in User preferences screen.</emphasis>
</para>
</example>
</section>
<section id="dynamicfields-configuration-updating">
<title>Updating from OTRS 3.0</title>
<para>
During the update from OTRS 3.0 there is an special step that is very important
and must not be skipped, there is an script file named "DBUpdate-to-3.1.pl" under the
"$OTRS_HOME/scripts" that must be called at the precise time in the update procedure
(please refer to UPGRADING file for more details).
</para>
<para>
The script mentioned above is in charge to get all the "Free fields" configurations
and creates their dynamic field substitute, it also gathers each "Free field" data
from every ticket and article and move it to the dynamic fields format. It also read
the screen configuration for "Free fields" and port it to the dynamic fields format.
</para>
<note>
<para>
All the "Free fields" configurations are keep in the system but they are not used
anymore, they are placed under the group "Z_Deprecated", and the might be removed
in further versions of OTRS.
</para>
<para>
While the updating script tries to be very precise migrating the screen
configurations it is always good to do a manual fine tuning. Please note that
"Free fields" TicketFreeKey[1-16] and TicketFreeText[1-16] came always in pair in
OTRS 3.0 systems (and before). This is not longer necessary it could be that
the TicketFreeKey field is not necessary anymore for a particular TicketFreeText
field.
</para>
</note>
<para>
The dynamic fields overview screen from clean OTRS 3.0.x updated to 3.1.x should look
like:
</para>
<para>
<screenshot>
<screeninfo>Updated dynamic field overview screen page1</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-overview-update-page1.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Updated dynamic field overview screen page2.</emphasis>
</para>
<para>
<screenshot>
<screeninfo>Updated dynamic field overview screen page1</screeninfo>
<graphic srccredit="dynamicfields - screenshot" scale="40" fileref="screenshots/dynamicfields-overview-update-page2.png"></graphic>
</screenshot>
</para>
<para>
<emphasis>Figure: Updated dynamic field overview screen page2.</emphasis>
</para>
<para>
Please note that the new dynamic field named "TicketFreeText2" has the label "Product",
this is because the default configuration from this "Free field" in OTRS 3.0.x
specifies that "TicketFreeKey2" has a fixed value of "Product". in this case the
dynamic field "TicketFreeKey2" is not needed anymore and it can be manually set to
invalid.
</para>
<para>
It might me also a very good idea to set the label value of each valid migrated field
to a text that describes better the use of the field in the system.
</para>
</section>
</section>
|