data.sql

jsp程序开发系统

INSERT INTO admin_help_cat VALUES (12,'Users',0);
INSERT INTO admin_help_cat VALUES (13,'Reports',0);
INSERT INTO admin_help_cat VALUES (14,'Statistics',0);
INSERT INTO admin_help_entry VALUES (8,13,'<I>[Optional]</I></P> <P>Use this field to restrict the tickets returned by\r\nthis statistic based on a function of time.</P> <P>Each of these selections\r\nmakes use of the <I>Search Length or Interval</I> option on this form.\r\nDepending on your selection, the effect of that field changes:</P> \r\n\r\n<P><I>[interval]</I>: Interval-based options cause the statistic to divide the\r\nreport\'s date range into blocks of time (specified in the <I>Search Length or\r\nInterval</I> field). The result is a list of ticket counts that match the\r\nsearch criteria in each block. This produces tables or graphs that show, for\r\nexample, how many tickets each technician closed over the past day, week,\r\nmonth, or even just the past few hours.</P>\r\n\r\n<P><I>[length]</I>: Length-based options cause the statistic to search only for\r\ntickets that match some time-based criteria. This produces tables or graphs\r\nthat show, for example, how many tickets went unanswered for over eight\r\nhours.</P>\r\n\r\n<P>DeskPro offers several different options for searching by or iterating over\r\ntime:</P>\r\n\r\n<P><U>Ticket Opened</U><BR> <I>[interval]</I> Specify a fairly short interval,\r\nsuch as one day, and use this option to produce a list of tickets opened for\r\nreport each day. This selection does not require (and ignores) any selections\r\nin the <I>1st</I> and <I>2nd Variable</I> fields.</P>\r\n\r\n<P><U>Ticked Closed</U><BR> <I>[interval]</I> Specify a fairly short interval,\r\nsuch as one day, and use this option to produce a list of tickets closed for\r\nreport each day. This selection does not require (and ignores) any selections\r\nin the <I>1st</I> and <I>2nd Variable</I> fields.</P>\r\n\r\n<P><U>Ticket Replied</U><BR> <I>[interval]</I> Specify a fairly short interval,\r\nsuch as one day, and use this option to produce a list of tickets that have\r\nreceived a response (from either a technician or a user) for each report day.\r\nThis selection does not require (and ignores) any selections in the <I>1st</I>\r\nand <I>2nd Variable</I> fields.</P>\r\n\r\n<P><U>Ticket Reopened</U><BR> <I>[interval]</I> Specify a fairly short\r\ninterval, such as one day, and use this option to produce a list of tickets\r\nthat have been reopened for each report day. This selection does ont require\r\n(and ignores) any selections in the <I>1st</I> and <I>2nd Variable</I>\r\nfields.</P>\r\n\r\n<P><U>1st Ticket Reply (less than)</U><BR> <I>[length]</I> Specify a short\r\nduration, like eight hours, and use this option to produce a list of all\r\ntickets within the report\'s run that were responded to within eight hours of\r\ntheir creation (i.e. \"answered quickly\").</P>\r\n\r\n<P><U>1st Ticket Reply (greater than)</U><BR> <I>[length]</I> Specify a short\r\nduration, like eight hours, and use this option to produce a list of all\r\ntickets within the report\'s run that were <I>not</I> responded to within\r\neight hours of their creation (i.e. \"answered slowly\").</P>\r\n\r\n<P><U>Ticket Lifetime (less than)</U><BR> <I>[length]</I> Specify a moderate\r\nduration, such as two days, and use this option to produce a list of all\r\ntickets that were opened and subsequently closed (i.e. \"resolved quickly\") over\r\na period shorter than two days. Note that re-opened tickets are also\r\nconsidered -- the time considered here is the length of time between the\r\n<I>initial</I> ticket creation and the ticket\'s final closing date. Open\r\ntickets are also considered unless the statistic is set to search only \r\nclosed tickets.</P>\r\n\r\n<P><U>Ticket Lifetime (greater than)</U><BR> <I>[length]</I> Specify a moderate\r\nduration, such as two days, and use this option to produce a list of all\r\ntickets that were opened and subseuqnetly closed (i.e. \"resolved slowly\") over\r\na period longer than two days. Note that re-opened tickets -- the time\r\nconsidered here is the length of time between the <I>initial</I> ticket\r\ncreation and the ticket\'s final closing date. Open tickets are also considered\r\nunless the statistic is set to search only closed tickets.',5,'Date Affects');
INSERT INTO admin_help_entry VALUES (9,13,'<I>[Required]</I></P> <P>Use this field to specify how you want the resulting\r\ndata displayed on the report:</P>\r\n\r\n<P><U>Data (Show a Simple Table)</U><BR> The statistic is shown as a simple\r\ntable with row (and, if a <I>2nd Variable</I> is specified, column) headers,\r\nand the resulting ticket counts. This option supports both single and double\r\nvariable searches.</P>\r\n\r\n<P><U>Bar Graph</U><BR> The statistic is shown as a bar graph. This option\r\nsupports both single and double variable searches.</P>\r\n\r\n<P><U>Pie Chart</U><BR> The statistic is shown as a pie chart. This option\r\nsupports only single variable searches (if a second variable is provided,\r\nit is ignored).</P>\r\n\r\n<P><U>CSV File</U><BR> The statistic is provided as a CSV file. This\r\noption supports both single and double variable searches.</P>\r\n\r\n<P><B>Note:</B> CSV File statistics are mutually exclusive; a CSV File\r\nstatistic must be the only statistic in a report. While a report can contain\r\nany number of statistics of any type, if any of them is a CSV File statistic,\r\nit will be generated and presented, and all other statistics in the report\r\n(including other CSV File statistics) will be ignored. This is because CSV\r\nfiles, by definition, can only specify a single \"table\" in each file.',4,'Display Type');
INSERT INTO admin_help_entry VALUES (10,13,'<I>[Required]</I></P> <P> Use this field to provide a detailed description of\r\nthe statistic. This is shown beneath the statistic\'s chart or graph for all\r\ndisplay types except CSV File.',3,'Description');
INSERT INTO admin_help_entry VALUES (11,13,'<I>[Required]</I></P> <P> Use this field to specify the statistic\'s title.\r\nThis is shown in the report definition and selection pages, and also as\r\na subtitle for the statistic on each report.',2,'Title');
INSERT INTO admin_help_entry VALUES (12,13,'<P>This form allows you to define a new statistic (or edit an existing one).\r\nSet or alter the fields shown on this page and select \"Create/Edit Statistic\"\r\nto add or edit the statistic.</P>',1,'New/Edit Form');
INSERT INTO admin_help_entry VALUES (13,13,'<I>[Optional]</I></P> <P> Use this field to specify the desired search length\r\nor interval for use with the Date Affects field. Multiple values may be entered\r\nhere and added to the list; the resulting list defines the length or interval.',6,'Search Length/Interval');
INSERT INTO admin_help_entry VALUES (14,13,'<I>[Required]</I></P> Use this field to specify which ticket attribute should\r\nbe used for first-level ticket counts. This variable becomes the \"X Axis\" of\r\nthe chart or graph produced by the statistic.</P>\r\n\r\n<P>In most cases, if only this variable is specified the resulting chart or\r\ngraph will be one-dimensional. That is, you will see only one row of\r\ncounts.</P>',7,'1st Variable');
INSERT INTO admin_help_entry VALUES (15,13,'<I>[Optional]</I></P> Use this field to specify which ticket attribute should\r\nbe used for second-level ticket counts. This variable becomes the \"X Axis\" of\r\nthe chart or graph produced by the statistic.</P>\r\n\r\n<P>If specified, another set of queries is performed after the first variable\r\nhas been processed -- one query per value returned by the first variable.\r\nThe rows of results returned by these queries becomes the \"Y Axis\" of the\r\nchart or graph produced by the statistic.</P>\r\n\r\n<P>This variable will be ignored under certain circumstances, including when\r\nthe statistic Display Type is set to Pie Chart.</P>',8,'2nd Variable');
INSERT INTO tech_internal_help_cat VALUES (11,'Users',0);
INSERT INTO tech_internal_help_cat VALUES (5,'User Notes',1);
INSERT INTO tech_internal_help_cat VALUES (6,'Calendar',1);
INSERT INTO tech_internal_help_cat VALUES (7,'Tickets - Starting New',0);
INSERT INTO tech_internal_help_cat VALUES (8,'Quick Replies',0);
INSERT INTO tech_internal_help_cat VALUES (9,'Tickets - Viewing and Responding',0);
INSERT INTO tech_internal_help_cat VALUES (10,'Tickets - Searching',0);
INSERT INTO tech_internal_help_cat VALUES (12,'Private Messages',0);
INSERT INTO tech_internal_help_cat VALUES (13,'Settings',0);
INSERT INTO tech_internal_help_cat VALUES (14,'FAQ',0);
INSERT INTO tech_internal_help_cat VALUES (15,'Resources',0);
INSERT INTO tech_internal_help_cat VALUES (16,'News',0);
INSERT INTO tech_internal_help_entry VALUES (12,11,'<I>[Optional]</I> These settings control automatic user expiration. Selecting \"never\" will disable automatic expiration for this user. Selecting \"# Tickets\" and entering a value will disable new ticket submissions by this user once this user has submitted the specified number of tickets (the value is decreased automatically as tickets are submitted; if \"# Tickets\" is selected and the value is zero, no new tickets can be submitted). Selecting \"On Date\" and providing a date will disable new ticket submissions by this user on and after the specified date.',1,'User Expires');
INSERT INTO tech_internal_help_entry VALUES (13,5,'Specifies whether this note will be visible to <I>all</I> technicians, or just you. If \"yes\", all technicians can view this note. If \"no\", only you can.',1,'Global');
INSERT INTO tech_internal_help_entry VALUES (14,6,'The calendar supports two kinds of events, <I>todo</I> and <I>ticket watch</I> events. A <I>todo</I> is an appointment set by you to complete a task or assignment. A <I>ticket watch</I> is a reminder to view a ticket on a certain date. You may also assign either type of event to another technician. On any calendar summary or list page, you can select to view both types of events, or to restrict the view to one type or the other. Select an option from the \"Viewing Event Types\" box to make this choice.',1,'Event Types');
INSERT INTO tech_internal_help_entry VALUES (15,6,'The title for this task on your calendar',3,'Events: Title');
INSERT INTO tech_internal_help_entry VALUES (16,6,'The task\'s due date.',4,'Events: Due Date');
INSERT INTO tech_internal_help_entry VALUES (17,6,'<I>[Optional]</I> The task\'s event time. To assign a time to a task, select the checkbox and specify the desired time.',5,'Events: Time');
INSERT INTO tech_internal_help_entry VALUES (18,6,'Descriptive text for this task.',6,'Events: Description');
INSERT INTO tech_internal_help_entry VALUES (19,6,'<I>[Optional]</I> E-mail reminders for this task can be sent to you, both on the due date and on up to two other days before the due date. Check the checkbox, and/or enter the number of days\' notice you\'d like to have for this task.',6,'Events: Reminders');
INSERT INTO tech_internal_help_entry VALUES (20,6,'Tasks can be assigned to more than one technician, including yourself. Select the technicians that should be assigned to this task here to assign this task to each of them.',7,'Events: Assignments');
INSERT INTO tech_internal_help_entry VALUES (21,6,'If you wish to send E-mail notifications to each technician assigned to this task immediately upon task creation, select \"Yes\" here.',8,'Events: Mail Now?');
INSERT INTO tech_internal_help_entry VALUES (22,6,'If this task is being assigned to multiple technicians, select how this task will be marked complete. If everyone assigned must complete the task before it is marked complete, select \"Yes\" here. If the task should be marked complete once <I>any</I> assigned technician has completed it, select \"No\" here.',9,'Events: Multiple or Single?');
INSERT INTO tech_internal_help_entry VALUES (23,6,'To receive an E-mail notification whenever anyone assigned to this task completes it, select \"Yes\" here.',10,'Events: E-mail on Completion?');
INSERT INTO tech_internal_help_entry VALUES (24,6,'Task repetition can be done with a variety of strategies. To specify a repeat strategy, select the radio box next to the desired repeat type, then enter or select the repeating interval.</P> <U>Daily Repeat</U><BR>Specify a value here to repeat the event every X days, where X is the value specified.</P>\n <U>Weekly Repeat</U><BR>Specify a value, and check days of the week here, to repeat the event every X weeks, where X is the value specified, on each checked day of each of those weeks.</P>\n<U>Monthly Repeat</U><BR>Specify a date and value here to repeat the event on the given date, each X months, where X is the value specified.</P>\n<U>Yearly Repeat</U><BR>Specify a date to repeat the event each year on the specified date.</P>\n<U>No Repeat</U><BR>Do not repeat the event.',11,'Events: Repeat Type');
INSERT INTO tech_internal_help_entry VALUES (25,6,'If the task is a repeating task, you can either let it repeat forever, or select a date to stop repeating the task. If an ending date is specified, no repeats of the task will be scheduled on or beyond that date.',12,'Events: Repeat End Date');
INSERT INTO tech_internal_help_entry VALUES (26,7,'<P><I>[Required]</I> Select the user that should own this new ticket. You can do this by entering a username, clicking \"find\" to search for a username (for both of these, check the first radio button), or by entering a new user\'s e-mail address (check the second radio botton) and filling in the user information fields below.</P>',0,'Specifying User');
INSERT INTO tech_internal_help_entry VALUES (27,7,'<P><I>[Recommended]</I> Enter the subject line for this ticket.</P>',0,'Subject');
INSERT INTO tech_internal_help_entry VALUES (28,7,'<P><I>[Required/optional depends on administrator\'s settings]</I> Select the category this ticket should be assigned to. If no technician is specified below and this category auto-assigns tickets, this ticket will be assigned to the category\'s technician.</P>',0,'Category');
INSERT INTO tech_internal_help_entry VALUES (29,7,'<P><I>[Required/optional depends on administrator\'s settings]</I> Select the priority this ticket should be assigned to. If no technician is specified below and this priority auto-assigns tickets, this ticket will be assigned to the priority\'s technician.</P>',0,'Priority');