ManualScrips - Revision history

Blaine at 18:51, 2 April 2019

2019-04-02T18:51:01Z

← Older revision		Revision as of 14:51, 2 April 2019
Line 119:		Line 119:
	Prev: [[ManualRights]] --- Up: [[UserManual]] --- Next: [[ManualApache]]		Prev: [[ManualRights]] --- Up: [[UserManual]] --- Next: [[ManualApache]]
	[[Category:RT User Manual]]		[[Category:RT User Manual]]
			[[Category:RT44]]

Craigkai at 12:51, 21 March 2019

2019-03-21T12:51:04Z

← Older revision		Revision as of 08:51, 21 March 2019
Line 5:		Line 5:
	== Scrips ==		== Scrips ==

	Official docs can be found here: https://docs.bestpractical.com/rt/~~4.4.4~~/customizing/scrip_conditions_and_action.html		Official docs can be found here: https://docs.bestpractical.com/rt/latest/customizing/scrip_conditions_and_action.html

	A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.		A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.

Craigkai at 12:50, 21 March 2019

2019-03-21T12:50:14Z

← Older revision		Revision as of 08:50, 21 March 2019
Line 4:		Line 4:

	== Scrips ==		== Scrips ==

			Official docs can be found here: https://docs.bestpractical.com/rt/4.4.4/customizing/scrip_conditions_and_action.html

	A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.		A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.
Line 58:		Line 60:
	Note: don't create a global scrip using the "On Create" condition and the "Create Ticket" scrip action. This will create a loop.		Note: don't create a global scrip using the "On Create" condition and the "Create Ticket" scrip action. This will create a loop.

			User Defined Condition:
			$self->ScripObj RT::Scrip,
			$self->TicketObj RT::Ticket,
			$self->TransactionObj RT::Transaction,
	=== Table 2: Actions ===		=== Table 2: Actions ===

Line 105:		Line 111:
	\|}		\|}

	~~Not clear what the difference is between Auto Reply and Notify Requestors~~		Custom Action Commit/Preparation Code:
			$self->ScripActionObj RT::ScripAction,
	~~===~~ Custom ~~condition ===~~		$self->ScripObj RT::Scrip,
			$self->TemplateObj RT::Template,
	~~You can customize conditions to fit your needs better. It would be good to find some information about the condition syntax. It would be good if there were reference information inserted here~~, ~~too.~~		$self->TicketObj RT::Ticket,
			$self->TransactionObj RT::Transaction,
	----

	Prev: [[ManualRights]] --- Up: [[UserManual]] --- Next: [[ManualApache]]		Prev: [[ManualRights]] --- Up: [[UserManual]] --- Next: [[ManualApache]]
	[[Category:RT User Manual]]		[[Category:RT User Manual]]

Admin: 9 revisions imported

2016-04-06T20:14:31Z

9 revisions imported

← Older revision		Revision as of 16:14, 6 April 2016
(No difference)

62.116.226.72: /* Scrips */

2013-06-19T09:41:36Z

Scrips

← Older revision		Revision as of 05:41, 19 June 2013
Line 5:		Line 5:
	== Scrips ==		== Scrips ==

	A ~~script~~ performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.		A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.

	=== Table 1: Conditions ===		=== Table 1: Conditions ===

213.47.84.12: /* Scrips */

2013-06-14T11:39:57Z

Scrips

← Older revision		Revision as of 07:39, 14 June 2013
Line 5:		Line 5:
	== Scrips ==		== Scrips ==

	A ~~scrip~~ performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.		A script performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.

	=== Table 1: Conditions ===		=== Table 1: Conditions ===

75.146.18.33:

{% if message %}

← Older revision Revision as of 15:09, 20 April 2012
Line 106: Line 106:

Not clear what the difference is between Auto Reply and Notify Requestors
Not clear what the difference is between Auto Reply and Notify Requestors

=== Table 3: Templates ===

{| border="1"

|- valign="top"

| Template name

| What the user sees

|- valign="top"

| Global template: Autoreply

| A form letter saying a ticket has been created and what the ticket's ID is.

|- valign="top"

| Global template: Transaction

| A form letter saying a ticket has been updated or changed in some way.

|- valign="top"

| Global template: Admin Reply

| A form letter saying a watcher sent a message and what the message was. Includes a URL linking to the message in RT.

|- valign="top"

| Global template: Reply

| A form letter saying a watcher sent a message and what the message was.

|- valign="top"

| Global template: Admin Comment

| A form letter saying a watcher sent a message and what the message was. Includes a URL linking to the message in RT and a note that says the requestor cannot see the message.

|- valign="top"

| Global template: Status Changed

| A form letter saying a ticket's status (open, new, stalled, etc.) has been changed.

|- valign="top"

| Global template: Resolved

| A form letter saying a ticket has been resolved.

|}

=== Custom condition ===
=== Custom condition ===

128.95.87.46: /* Custom condition */

2011-11-22T00:44:57Z

Custom condition

← Older revision		Revision as of 20:44, 21 November 2011
Line 138:		Line 138:
	=== Custom condition ===		=== Custom condition ===

	You can customize conditions to fit your needs better. It would be good to find some information about the condition syntax.		You can customize conditions to fit your needs better. It would be good to find some information about the condition syntax. It would be good if there were reference information inserted here, too.

	----		----

165.21.15.150: /* Scrips */

2011-07-26T09:51:00Z

Scrips

← Older revision		Revision as of 05:51, 26 July 2011
Line 5:		Line 5:
	== Scrips ==		== Scrips ==

	A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.		A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.

	=== Table 1: Conditions ===		=== Table 1: Conditions ===

	{\| border="1"		{\| border="1"

BillCole: /* Scrips */

2010-12-23T00:26:31Z

Scrips

← Older revision		Revision as of 20:26, 22 December 2010
Line 5:		Line 5:
	== Scrips ==		== Scrips ==

	A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>.		A scrip performs some action when some conditions are met. Many actions use a template. You can read a scrip as a sentence like: When <condition>, do <action> with <template>. When creating a Scrip, it is helpful to make the "Description" field a user-friendly phrase such as "Send replies to Requestor and Cc users" because users see that description in '''bold''' on the ticket update composition page.

	=== Table 1: Conditions ===		=== Table 1: Conditions ===

   {% if message %}
@@ Line 106: / Line 106: @@
 Not clear what the difference is between Auto Reply and Notify Requestors
 === Custom condition ===