Changes between Version 29 and Version 30 of TicketToSalesforcePlugin


Ignore:
Timestamp:
Feb 8, 2011, 1:27:12 PM (4 years ago)
Author:
chriswolf
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketToSalesforcePlugin

    v29 v30  
    102102
    103103== Known Issues ==
    104  Even though the case number is numerical, you must enter it with whatever leading zeros are
    105     configured in Salesforce for this field, since the query treats this as a string
     104   * Even though the case number is numerical, you must enter it with whatever leading zeros are
     105     configured in Salesforce for this field, since the query treats this as a string
    106106
    107 This plugin comes with a `TicketValidator` which checks if the entered case number actually
    108     exists in Saleforce, but also if case number is blank - so if you are using the
    109     [wiki:TicketValidatorPlugin] you will !get two warning messages,
    110     "case number required" upon attempting to submit a ticket without a case number.
     107   * This plugin comes with a `TicketValidator` which checks if the entered case number actually
     108     exists in Saleforce, but also if case number is blank - so if you are using the
     109     [wiki:TicketValidatorPlugin] you will !get two warning messages,
     110     "case number required" upon attempting to submit a ticket without a case number.
    111111
    112112== Screen Shots ==