Guest User

Untitled

a guest
Sep 11th, 2017
31
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.09 KB | None | 0 0
  1. <root>
  2. <field>
  3. <name>email</name>
  4. <datatype>Text</datatype>
  5. <required>true</required>
  6. <helptext>Email address of the requester. If no contact exists with this email address in freshservice, it will be added as a new contact.</helptext>
  7. <testdata>testtest@test.com</testdata>
  8. </field>
  9. <field>
  10. <name>requester_id</name>
  11. <datatype>Number</datatype>
  12. <required>false</required>
  13. <helptext>User-id of the requester. For existing contacts, requester_id can be passed instead of email.</helptext>
  14. <testdata>666666</testdata>
  15. </field>
  16. <field>
  17. <name>assoc_problem_id</name>
  18. <datatype>Number</datatype>
  19. <required>false</required>
  20. <helptext>id of the associated problem to the ticket.</helptext>
  21. <testdata>555555</testdata>
  22. </field>
  23. <field>
  24. <name>assoc_change_id</name>
  25. <datatype>Number</datatype>
  26. <required>false</required>
  27. <helptext>id of the change initiating the ticket.</helptext>
  28. <testdata>444444</testdata>
  29. </field>
  30. <field>
  31. <name>assoc_change_cause_id</name>
  32. <datatype>Number</datatype>
  33. <required>false</required>
  34. <helptext>id of the change causing the ticket.</helptext>
  35. <testdata>333333</testdata>
  36. </field>
  37. <field>
  38. <name>assoc_asset_id</name>
  39. <datatype>Number</datatype>
  40. <required>false</required>
  41. <helptext>id of the asset associated to the ticket.</helptext>
  42. <testdata>222222</testdata>
  43. </field>
  44. <field>
  45. <name>subject</name>
  46. <datatype>Text</datatype>
  47. <required>false</required>
  48. <helptext>Ticket subject.</helptext>
  49. <testdata>Test subject</testdata>
  50. </field>
  51. <field>
  52. <name>description</name>
  53. <datatype>Text</datatype>
  54. <required>false</required>
  55. <helptext>Plain text/HTML content of the ticket.</helptext>
  56. <testdata>This is a description</testdata>
  57. </field>
  58. <field>
  59. <name>status</name>
  60. <datatype>Number</datatype>
  61. <required>false</required>
  62. <helptext>Status of the ticket (Open: 2, Pending: 3, Resolved: 4, Closed: 5)</helptext>
  63. <testdata>2</testdata>
  64. </field>
  65. <field>
  66. <name>priority</name>
  67. <datatype>Number</datatype>
  68. <required>false</required>
  69. <helptext>Priority of the ticket(Low: 1, Medium: 2, High: 3, Urgent: 4)</helptext>
  70. <testdata>1</testdata>
  71. </field>
  72. <field>
  73. <name>source</name>
  74. <datatype>Number</datatype>
  75. <required>false</required>
  76. <helptext>The channel through which the ticket was created(Email: 1, Portal: 2, Phone: 3, Chat</helptext>
  77. <testdata>2</testdata>
  78. </field>
  79. <field>
  80. <name>deleted</name>
  81. <datatype>Boolean</datatype>
  82. <required>false</required>
  83. <helptext>Set as true if the ticket is deleted/trashed. Deleted tickets will not be considered in any views except "deleted" filter.</helptext>
  84. <testdata>false</testdata>
  85. </field>
  86. <field>
  87. <name>spam</name>
  88. <datatype>Boolean</datatype>
  89. <required>false</required>
  90. <helptext>Set as true if the ticket is marked as spam.</helptext>
  91. <testdata>false</testdata>
  92. </field>
  93. <field>
  94. <name>responder_id</name>
  95. <datatype>Number</datatype>
  96. <required>false</required>
  97. <helptext>ID of the agent to whom the ticket is assigned.</helptext>
  98. <testdata>111111</testdata>
  99. </field>
  100. <field>
  101. <name>group_id</name>
  102. <datatype>Number</datatype>
  103. <required>false</required>
  104. <helptext>Id of Group to which the ticket is assigned.</helptext>
  105. <testdata>123456</testdata>
  106. </field>
  107. <field>
  108. <name>ticket_type</name>
  109. <datatype>Number</datatype>
  110. <required>false</required>
  111. <helptext>Type property field as defined in ticket fields.</helptext>
  112. <testdata>Incident</testdata>
  113. </field>
  114. <field>
  115. <name>to_email</name>
  116. <datatype>Text</datatype>
  117. <required>false</required>
  118. <helptext>Email address to which the incoming ticket email was sent.</helptext>
  119. <testdata>toemail@email.com</testdata>
  120. </field>
  121. <field>
  122. <name>cc_email</name>
  123. <datatype>Text</datatype>
  124. <required>false</required>
  125. <helptext>Email address added in the 'cc' field of the incoming ticket email.</helptext>
  126. <testdata>cctest@email.com</testdata>
  127. <testdata>cctest2@email.com</testdata>
  128. </field>
  129. <field>
  130. <name>email_config_id</name>
  131. <datatype>Number</datatype>
  132. <required>false</required>
  133. <helptext>Id of email config which is used for this ticket (i.e., support@yourcompany.com/sales@yourcompany.com).</helptext>
  134. <testdata>support@yourcompany.com</testdata>
  135. </field>
  136. <field>
  137. <name>isescalated</name>
  138. <datatype>Boolean</datatype>
  139. <required>false</required>
  140. <helptext>Set to true if an escalation was sent</helptext>
  141. <testdata>false</testdata>
  142. </field>
  143. <field>
  144. <name>due_by</name>
  145. <datatype>Datetime</datatype>
  146. <required>false</required>
  147. <helptext>Ticket due-by time.</helptext>
  148. <testdata></testdata>
  149. </field>
  150. <field>
  151. <name>category</name>
  152. <datatype>Text</datatype>
  153. <required>false</required>
  154. <helptext>Ticket category.</helptext>
  155. <testdata>Software</testdata>
  156. </field>
  157. <field>
  158. <name>sub_category</name>
  159. <datatype>Text</datatype>
  160. <required>false</required>
  161. <helptext>Ticket sub category.</helptext>
  162. <testdata>subCategory</testdata>
  163. </field>
  164. <field>
  165. <name>item_category</name>
  166. <datatype>Text</datatype>
  167. <required>false</required>
  168. <helptext>Ticket item category.</helptext>
  169. <testdata>itemCategory</testdata>
  170. </field>
  171. </root>
Add Comment
Please, Sign In to add comment