Recurring Tickets - Revision history

Dina at 10:09, 20 January 2021

2021-01-20T10:09:25Z

← Older revision		Revision as of 10:09, 20 January 2021
Line 107:		Line 107:
	\|colspan="2"\|'''Additional fields'''		\|colspan="2"\|'''Additional fields'''
	On the right side bar and under the Details tab you can also set Source, Status, Priority, Resolution and other fields		On the right side bar and under the Details tab you can also set Source, Status, Priority, Resolution and other fields
			\|-
			\|Charges
			\|Define Charge records that will be automatically added under the newly created recurring Ticket. See more under [[Recurring_Tickets#Adding Charge in the Recurring Ticket Template\|Adding Charge in the Recurring Ticket Template]].
	\|-		\|-
	\|Activity Template		\|Activity Template
	\|Select an [[Activity_Templates_for_Tickets\|Activity Template]] ~~the~~ will be applied automatically on recurring ticket creation.		\|Select an [[Activity_Templates_for_Tickets\|Activity Template]] that will be applied automatically on recurring ticket creation.
	\|-		\|-
	\|Default Labels		\|Default Labels
Line 118:		Line 121:

	[[File:Recurring_ticket_template_automation_tab.png]]		[[File:Recurring_ticket_template_automation_tab.png]]

			==Adding Charge in the Recurring Ticket Template==

			The Ticket Template can optionally include Charge records that will be automatically added while creating a Ticket based on the template.



	==Recurring Settings for Ticket Template ==		==Recurring Settings for Ticket Template ==

Dina at 13:37, 8 July 2020

2020-07-08T13:37:23Z

← Older revision		Revision as of 13:37, 8 July 2020
Line 22:		Line 22:

	==Setting up the Recurring Tickets==		==Setting up the Recurring Tickets==
	Recurring Tickets are automatically created by the '~~CommitCRM~~ Server' Windows service.		Recurring Tickets are automatically created by the 'RangerMSP Server' Windows service.

	This Windows service must be installed on your server and must be running at all times in order for this feature to work.		This Windows service must be installed on your server and must be running at all times in order for this feature to work.

	If you already use the [[Email Connector]] or [[Alerts Server]] then you can skip this section as the ~~CommitCRM~~ Server service is already installed and there is nothing more you need to do besides defining the Recurring Ticket Templates.		If you already use the [[Email Connector]] or [[Alerts Server]] then you can skip this section as the RangerMSP Server service is already installed and there is nothing more you need to do besides defining the Recurring Ticket Templates.

	For installation instructions please review the [[Install Server_Service\|Service Setup Guide]].		For installation instructions please review the [[Install Server_Service\|Service Setup Guide]].
Line 66:		Line 66:
	\|-		\|-
	\| A Contract Series		\| A Contract Series
	\| ~~CommitCRM~~ will automatically pick the currently active Contract from the series when adding new recurring Ticket to the Account.		\| RangerMSP will automatically pick the currently active Contract from the series when adding new recurring Ticket to the Account.
	(*) If no valid Contract will be found, the system will create the Ticket linking to the System Global Contract.		(*) If no valid Contract will be found, the system will create the Ticket linking to the System Global Contract.
	\|-		\|-
Line 128:		Line 128:
	* [[Tickets]]		* [[Tickets]]
	* [[Recurring Charges]]		* [[Recurring Charges]]
	*[[Email Connector\|~~CommitCRM~~ Email Connector]]		*[[Email Connector\|RangerMSP Email Connector]]
	*[[Alerts Server\|~~CommitCRM~~ Alerts Server]]		*[[Alerts Server\|RangerMSP Alerts Server]]
	[[Category:Service Management]]		[[Category:Service Management]]
	[[Category:Work Flows]]		[[Category:Work Flows]]

Dina at 13:55, 22 March 2020

2020-03-22T13:55:38Z

← Older revision		Revision as of 13:55, 22 March 2020
Line 28:		Line 28:
	If you already use the [[Email Connector]] or [[Alerts Server]] then you can skip this section as the CommitCRM Server service is already installed and there is nothing more you need to do besides defining the Recurring Ticket Templates.		If you already use the [[Email Connector]] or [[Alerts Server]] then you can skip this section as the CommitCRM Server service is already installed and there is nothing more you need to do besides defining the Recurring Ticket Templates.

	For installation instructions please review the [[~~Install_CommitCRM_Server_Service~~\|Service Setup Guide]].		For installation instructions please review the [[Install Server_Service\|Service Setup Guide]].

Dina: /* Recurring Settings for Ticket Template */

2018-11-05T11:06:35Z

Recurring Settings for Ticket Template

← Older revision		Revision as of 11:06, 5 November 2018
Line 120:		Line 120:

	==Recurring Settings for Ticket Template ==		==Recurring Settings for Ticket Template ==
	#Set the Ticket recurrence cycle, i.e. how often and at what exact time of day the Ticket will be created. For example: <br>		#Set the Ticket recurrence cycle, i.e. how often and at what exact time of day the Ticket will be created. For example: <br><br>''Weekly, on Monday every 1 week at 10:00 AM.'' <br><br>The options change dynamically depending on whether you choose Daily, Weekly, Monthly, Annual type.
	''Weekly, on Monday every 1 week at 10:00 AM.''		#Set the expiration date for the Recurring Ticket. After this date the Ticket will stop being created. ‘Never Expire’ means that the Ticket will keep being created for an unlimited time.
	The options change dynamically depending on whether you choose Daily, Weekly, Monthly, Annual type.
	#Set the expiration date for the Recurring Ticket. After this date the Ticket will stop being created. ‘Never Expire’ means that the Ticket will keep being created for an unlimited time		[[File:Recurring_ticket_settings.png]]

	=See Also=		=See Also=

Dina: /* Configuring a recurring Ticket Template */

2018-11-05T11:03:53Z

Configuring a recurring Ticket Template

← Older revision		Revision as of 11:03, 5 November 2018
Line 39:		Line 39:
	The recurring Tickets are based on the templates that can be updated at any time and will affect the Tickets created on the next cycle.		The recurring Tickets are based on the templates that can be updated at any time and will affect the Tickets created on the next cycle.

			[[File:Recurring_ticket_template.png]]

	The following table describes the recurring Ticket Template fields:		The following table describes the recurring Ticket Template fields:

Dina: /* Configuring a recurring Ticket Template */

2018-11-05T11:00:05Z

Configuring a recurring Ticket Template

← Older revision		Revision as of 11:00, 5 November 2018
Line 48:		Line 48:
	! Description		! Description
	\|-		\|-
	\| Account(mandatory)		\| Account (mandatory)
	\| Select the Account for the recurring Ticket.		\| Select the Account for the recurring Ticket.
	\|-		\|-
Line 98:		Line 98:
	\|Specific Recipients		\|Specific Recipients
	\|-		\|-
	\|'''Description'''		\|'''Description''' (mandatory)
	(mandatory)
	\|Enter the Ticket Description		\|Enter the Ticket Description
	\|-		\|-

Dina at 10:57, 5 November 2018

2018-11-05T10:57:23Z

@@ Line 1: / Line 1: @@
 {{servicemanagement}}
 ==Introduction==
@@ Line 36: / Line 38: @@
 The recurring Tickets are based on the templates that can be updated at any time and will affect the Tickets created on the next cycle.

Dina: Created page with "{{servicemanagement}} ==Introduction== The Recurring Tickets allows to automate repeating tasks for customers such as: Daily ticket to verify customer backups. Weekly ti..."

2018-11-05T10:26:32Z

Created page with "{{servicemanagement}} ==Introduction== The Recurring Tickets allows to automate repeating tasks for customers such as: *Daily ticket to verify customer backups. *Weekly ti..."

New page

{{servicemanagement}}

==Introduction==

The Recurring Tickets allows to automate repeating tasks for customers such as:

*Daily ticket to verify customer backups.
*Weekly ticket to check antivirus scan reports.
*Monthly ticket to perform customer server maintenance.
*Monthly ticket to carry out preventive proactive maintenance on a server or other equipment.
*Annual ticket to install the new SSL certificates on the customer server.

New Tickets created automatically from recurring tickets templates get pushed automatically to the Open Tickets list.
You can add any number of recurring Tickets under each customer account.

[[File:Recurring_ticket_templates_list.png]]

Using the Recurring Tickets you will never need to remember to perform repeating jobs. You just need to configure a Ticket Template that will create new tickets automatically based on a recurring schedule. These tickets will remind you to perform the work and they already will include all details required for the job.

==Setting up the Recurring Tickets==
Recurring Tickets are automatically created by the 'CommitCRM Server' Windows service.

This Windows service must be installed on your server and must be running at all times in order for this feature to work.

If you already use the [[Email Connector]] or [[Alerts Server]] then you can skip this section as the CommitCRM Server service is already installed and there is nothing more you need to do besides defining the Recurring Ticket Templates.

For installation instructions please review the [[Install_CommitCRM_Server_Service|Service Setup Guide]].

== Configuring a recurring Ticket Template ==

Recurring ticket templates can be managed using the main Tickets window. You can also review customer specific templates under the customer Account Tickets tab.

The recurring Tickets are based on the templates that can be updated at any time and will affect the Tickets created on the next cycle.

Recurring Tickets - Revision history

Dina at 10:09, 20 January 2021

Dina at 13:37, 8 July 2020

Dina at 13:55, 22 March 2020

Dina: /* Recurring Settings for Ticket Template */

Dina: /* Configuring a recurring Ticket Template */

Dina: /* Configuring a recurring Ticket Template */

Dina at 10:57, 5 November 2018

Dina: Created page with "{{servicemanagement}} ==Introduction== The Recurring Tickets allows to automate repeating tasks for customers such as: *Daily ticket to verify customer backups. *Weekly ti..."

Dina: Created page with "{{servicemanagement}} ==Introduction== The Recurring Tickets allows to automate repeating tasks for customers such as: Daily ticket to verify customer backups. Weekly ti..."