Version 26.0.0.2 - Have had this problem forever, and it is bugging me again. The incoming new service request header is appending an extra subject and places the TKTNO filed in the middle or at the end of the subject. We expect it to be in the front of the subject.
Examples:
Original incoming request: "My test ticket subject, ticketno SHOULD be placed in front [TKT-0500-25051]"
Autoreply: "RE: My test ticket subject, ticketno SHOULD be placed in front [TKT-0500-25051] My test ticket subject, ticketno SHOULD be placed in front"
TEMPLATE: Ticket - Auto Response to Client (Email-to-Ticket) Custom (Default)
SUBJECT: [TKT-<CMTLBLDATA_FLDTKTTICKETNO>] <CMTLBLDATA_FLDTKTCLCPROBLEMFIRSTLINE>
Obviously, the autoreply subject appearance is not professional. We have to clean up our manual replies before sending, but this breaks the chain and creates a new chain.
Manually sending an email from this template works as expected, the subject is just jumbled with the automation.
Examples:
Original incoming request: "My test ticket subject, ticketno SHOULD be placed in front [TKT-0500-25051]"
Autoreply: "RE: My test ticket subject, ticketno SHOULD be placed in front [TKT-0500-25051] My test ticket subject, ticketno SHOULD be placed in front"
TEMPLATE: Ticket - Auto Response to Client (Email-to-Ticket) Custom (Default)
SUBJECT: [TKT-<CMTLBLDATA_FLDTKTTICKETNO>] <CMTLBLDATA_FLDTKTCLCPROBLEMFIRSTLINE>
Obviously, the autoreply subject appearance is not professional. We have to clean up our manual replies before sending, but this breaks the chain and creates a new chain.
Manually sending an email from this template works as expected, the subject is just jumbled with the automation.

Comment