/build/static/layout/Breadcrumb_cap_w.png

Can you force Ticket Save Event

Hi Guys,

I have created a process that creates 3 Stages of Child Tickets. I have also created CTR's that push fields from the parent to the children on the parent's save.  These rules push certain values to each child ticket created. One the Stage 1 Child Tickets the rules work just fine.  I save the parent, it creates children, and pushes the appropriate data down to them.  The problem occurs with the Stage 2 Child Tickets.  When I close all of the Stage 1 Tickets and Stage 2 kicks off, it doesn't trigger the save event for the parent ticket and it doesn't push down the values for the children. I know I could work around this by running my CTR's from the child queue and having them pull the values on the Child Saves. I'm hoping to force the Parent Save Event to avoid having a process that involves a bunch of CTR's in 2 different queues for the same process. Mostly because I am running a process with that creates children in 4 different queues and would make keeping track of my CTR's pretty convoluted across all the queues.  Is there a way that I can force the Parent Ticket to save again after the Stage 2 Tickets kick off?

My current thought is that I could make a rule that changes the Parent Resolution upon a particular Child Save. But am totally uncertain as to what might kick off a save other than pressing the pretty blue save button.  Any thoughts?

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: svmay 8 years ago
Red Belt
2

Top Answer

I don't know if this can help you. I have a custom rule that close the parent ticket when the child ticket get closed.
Maybe it helps you and gives you an idea for solving your problem.

sql-select:
SELECT		HD_TICKET.ID,
HD_TICKET.TITLE,
HD_TICKET.SUMMARY,
HD_TICKET.OWNER_ID,
HD_TICKET.SUBMITTER_ID,
HD_TICKET.HD_STATUS_ID,
CHILDSTATUS.STATE,


PARENT.TITLE,
PARENT.SUMMARY,
PARENT.OWNER_ID,
PARENT.HD_STATUS_ID,
PARENTSTATUS.STATE

FROM HD_TICKET

LEFT JOIN HD_STATUS AS CHILDSTATUS
ON CHILDSTATUS.ID = HD_TICKET.HD_STATUS_ID
LEFT JOIN HD_TICKET AS PARENT
ON PARENT.ID = HD_TICKET.PARENT_ID
LEFT JOIN HD_STATUS AS PARENTSTATUS
ON PARENTSTATUS.ID = PARENT.HD_STATUS_ID

WHERE HD_TICKET.IS_PARENT = 0 AND
PARENT.HD_QUEUE_ID = 13 AND
CHILDSTATUS.STATE = 'closed'

sql-update:

UPDATE	HD_TICKET PARENT, HD_TICKET, HD_STATUS

SET
PARENT.HD_STATUS_ID = HD_STATUS.ID,
PARENT.RESOLUTION = 'Closed',
PARENT.TIME_OPENED = IF(HD_STATUS.STATE = 'opened', NOW(), PARENT.TIME_OPENED),
PARENT.TIME_CLOSED = IF(HD_STATUS.STATE = 'closed', NOW(), PARENT.TIME_CLOSED),
PARENT.TIME_STALLED = IF(HD_STATUS.STATE = 'stalled', NOW(), PARENT.TIME_STALLED),
PARENT.SATISFACTION_RATING = IF(HD_STATUS.STATE = 'closed', NULL, PARENT.SATISFACTION_RATING),
PARENT.SATISFACTION_COMMENT = IF(HD_STATUS.STATE = 'closed', NULL, PARENT.SATISFACTION_COMMENT)

WHERE HD_STATUS.NAME = 'Closed' AND
PARENT.HD_QUEUE_ID = HD_STATUS.HD_QUEUE_ID AND
PARENT.ID = HD_TICKET.PARENT_ID AND
HD_TICKET.ID = (<TICKET_IDS>)






Comments:
  • Thank you for the answer, It does provide some help. I have figured out a way around the problem after going through on-site training. But your code actually answers another question I had yet to ask. So, Thanks! - antbarrone 8 years ago
    • Its nice to know, that I could help you! - svmay 8 years ago
    • Hi antbarrone, how did you solve that problem - What did the trainer told you, how you can achieve that? I´ m standing in front of the same problem, where I must have a "save-event" in order to get other ticket-rules working. When I change for example items of a another ticket in the database, the next ticket rule does not recognizes that things have changed. I believe the changes are "catched" by the "HD_TICKET_CHANGE" / "HD_TICKET_CHANGE_FIELD" table. I´ m not aware if there is some kind of "API-Call" to trigger a "save-event" on a ticket... - jimbeam128 4 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ