Just to follow up - I looked at the rendered pages html source and tried
using the ID for the field as the querystring parameter I wanted to set. It
works, but as Kevin said the ID is interesting.
For custom fields you will be looking for something like
this:
JavaScript's 'onPageLoad' is the first thing that comes to my mind, although I
don't know right off hand how you could incorporate it with the RT API in
Mason. I am sure there is a way to set it with javascript or another language
for when the ticket page initially loads.
From:
On Tue, Nov 08, 2011 at 03:11:45PM -0500, Jim Lesinski wrote:
I understand how to set up default values for a field using a custom
scrip. However, it seems
a bit odd to me to load a ticket with no value, and then set it only if
the person opening a
ticket doesn't select a value.
It looks like RT-Extension-QuickCalls can set some values using querystring
parameters, but that doesn't seem to be working for custom fields. Is it
even possible to set values for custom fields using querystring params? If
you can, I may be able to use that.
On Tue, Nov 8, 2011 at 3:17 PM, Kevin
On Tue, Nov 08, 2011 at 04:55:13PM -0500, Jim Lesinski wrote:
It looks like RT-Extension-QuickCalls can set some values using
querystring parameters, but
that doesn't seem to be working for custom fields. Is it even possible to
set values for
custom fields using querystring params?
Thanks Kevin. What do you mean by interesting? Can you provide an example of
the format or where I can find the values I should use?
Thanks,
Jim Lesinski
On Nov 8, 2011, at 7:11 PM, Kevin Falcone falc...@bestpractical.com wrote:
On Tue, Nov 08, 2011 at 04:55:13PM -0500, Jim Lesinski wrote: