I would recommend using Dirk Papes HideGlobalScrips which allow you to
enable/disable global scrips per queue basis using radio buttons. It¹s a
great extension to an already great ticketing system
You can also add the scrip to RT core so it¹s turns up in the ScripCondition
and ScripAction dropdown menus. That way you don¹t need to copy-paste your
long file into the user defined fields all the time. Instructions should be
available on the wiki, I just can¹t find it right now.
R, JohanOn 5/20/08 5:02 PM, “Forrest Blount” email@example.com wrote:
I have a scrip that has a large amount of text matching expressions which will
likely be changed on semi-regular basis. This scrip will be applied to
several queues, but not to all of our queues, so it would save a lot of time
if it could be applied (like a custom field) to each queue, instead of created
as a separate instance in each queue. My understanding is that RT (3.6.4)
only allows scrips to work on either global or queue based levels. If I’m
correct, I’d like to accomplish something similar by moving the scrip code
into a perl file that could be included on a permanent basis in a scrip for
each appropriate queue, allowing all of the future changes to be made in the
If this is possible I have a few questions:
- Where should the file be placed to avoid problems on future upgrades?
- Does the scrip in RT need any additional commands other than “do file.pl” in
the action cleanup code?
Thanks in advance for any help you can provide!
Community help: http://wiki.bestpractical.com
Commercial support: firstname.lastname@example.org
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/