Mark, I'd need to know more about the requirement to be sure, but .
You could define a Service Request for the re-occurring task and define a 'Next Action' date field and an interval. You would then calculate the Next Action date in the SRD. Then the only customization would be an escalation on the ServiceRequest form that submits a 'copy' of itself on the Next Action date. HTH, Joel Joel Sender * <mailto:jdsen...@earthlink.net> jdsen...@earthlink.net From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brittain, Mark Sent: Friday, January 13, 2017 6:43 AM To: arslist@ARSLIST.ORG Subject: Automated Ticket ** Hi All & TGIF the 13th, In our legacy Remedy 6,3 totally customized system, we had a custom form (Scheduled Ticket), like a ticket template, that included interval and next creation date. An escalation would run against the Scheduled Ticket form and if the next creation date was today, then a Trouble Ticket (e.g. Incident) would be created. Then based on the interval (e.g. weekly) the next creation date would be set in the Scheduled Ticket. When we moved to ITSM 7.6.04, I created a similar customization but based it on Work Orders. Now that we are moving to ITSM 9, I have been asked if there is a functionality within ITSM that can be leveraged rather than doing this heavy customization. If there is a way, that would be great. If anyone has done something similar, it would be great to hear about. Thanks Mark Mark Brittain | Systems Engineer | 315.634.9337 125 Elwood Davis Road | Syracuse NY 13212 Navisite _ARSlist: "Where the Answers Are" and have been for 20 years_ --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
