Hi Mark Since you said it was originally Incidents, and then you changed it to work orders. If you are ok with using the Change Module, here are links to OOTB functionality that allow you to create schedules against CI's that will create Change Requests on a recurring schedule. If you use this, there would be no customization.
After all, an Incident is something that cannot be predicted, so I am guessing that this 'scheduled' ticket you talk about relates to a proactive kind of activity, like a change. It uses Change Templates, so you can have multiple tasks linked to the Change when it gets created if needed. Here are links to docs explaining this functionality. https://docs.bmc.com/docs/display/public/asset91/Working+with+maintenance+schedules+and+audit+schedules https://docs.bmc.com/docs/display/public/asset81/Working+with+maintenance+schedules+and+audit+schedules On Fri, Jan 20, 2017 at 8:07 AM, Hennigan, Sandra H CTR DSS DSS HQ (US) < [email protected]> wrote: > All, > > This is a fairly simple function using an Escalation to push data to > either the HPD:Interface_Create or the WOI:Interface_Create. Logging will > help you figure out the field mapping. I use a Staging form to collect the > data as we generate about 30 reoccurring Work Orders and a Staging form > record is added for each one that includes when the Work order should be > created - daily, weekly or monthly.. > > Sandra > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > [email protected]] On Behalf Of Jamie > Sent: Tuesday, January 17, 2017 10:34 AM > To: [email protected] > Subject: [Non-DoD Source] Re: Automated Ticket > > All active links contained in this email were disabled. Please verify the > identity of the sender, and confirm the authenticity of all links contained > within the message prior to copying and pasting the address to a Web > browser. > > > > > ---- > > We have similar functionality that you are describing that we use to > create Compliance Tickets on a daily, weekly, monthly, semi-annually, and > annually basis. We had this same functionality within 6.3 back in 2008 > when we were moving to 7.5 and were looking to stay out of the box. We > ended up putting this functionality within our Kinetic Data Request and > Task modules since we were using it for our service requests and have had > it there since. We use their task scheduled and a data table to determine > which tickets (with template) needs to be created based on their policy and > then use the Kinetic Task Engine to create the service request work order > and assign it to the proper group based on the template. We then have some > more process builder logic that gathers a "close down" type of approval > when the ticket is closed to ensure the proper evidence was added to the > ticket by the technician. > > I'm not that knowledgeable enough to do this within SRM with it being > pretty limited without customizing and creating a bunch of AIF forms and > workflow possibly. I just wanted to share with you a similar functionality > and how we accomplished it. > > ____________________________________________________________ > ___________________ > UNSUBSCRIBE or access ARSlist Archives at Caution-www.arslist.org "Where > the Answers Are, and have been for 20 years" > > ____________________________________________________________ > ___________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
