That’s exactly what I did. And it seems to be working now! Thanks
Ibrar Bajwa Remedy Analyst Brookfield Corporate Operations Technology Services 1 Adelaide Street East, Suite 1400, Toronto, ON M5C 2V9 T 416.649.8249, F 416.649.8245 [email protected] [cid:[email protected]] View Important disclosures and information about our e-mail policies here<http://www.brookfield.com/emaildisclaimer>. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Kemes, Lisa Sent: Tuesday, December 20, 2011 8:56 AM To: [email protected] Subject: Re: [$$ $$] wrap in email templates ** Could it be that you have colons in your details field? I know that if our email engine sees a colon where it shouldn't be, it thinks it's a field and then errors out. Change your colons to hyphens and see if that works... Thanks! Lisa ________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Boyd, Rebecca Sent: Monday, December 19, 2011 6:37 PM To: [email protected]<mailto:[email protected]> Subject: Re: [$$ $$] wrap in email templates ** Try: [\$\$ <your text here> \$\$] On Mon, Dec 19, 2011 at 2:48 PM, Bajwa, Ibrar <[email protected]<mailto:[email protected]>> wrote: Hello Everyone! I am having issues with using a auto-generating ticket via email for incidents. I have narrowed down the issue to tickets that multiple lines in the 'details'. It seems as if any tickets that have multiple lines in 'details' wrapped with [$$ text $$] is not accepted by remedy for creating the ticket via email. However, details that are simple single line do seem to be generating. Below is an example of what works and what doesn't. I have tried with $$] on next line and last line in the template of the email. <DOES NOT WORK> ... Details !1000000151!: [$$Event Name: A Service Incident has been reported URL: https:// Event originator: servername Event Severity: 3 Event received: whatever date Event description: This event will be sent any time a service incident is reported. A service incident is generated when it is determined that a serviceable event has occurred based upon analysis of system-initiated events. User Action: Refer to the Recommended Action under the event details section.$$] <DOES WORK> ... Details !1000000151!: Event Name: A Service Incident has been reported (Type 4). Any assistance would be appreciated. If you require more details, just ask away. Ibrar Bajwa Remedy Analyst Brookfield Corporate Operations Technology Services 1 Adelaide Street East, Suite 1400, Toronto, ON M5C 2V9 T 416.649.8249<tel:416.649.8249>, F 416.649.8245<tel:416.649.8245> [email protected]<mailto:[email protected]> View important disclosures and information about our e-mail policies http://www.brookfield.com/emaildisclaimer. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org> attend wwrug12 www.wwrug12.com<http://www.wwrug12.com> ARSList: "Where the Answers Are" -- Rebecca Boyd Application Administrator Wake Forest University _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
<<inline: image3579d8.GIF>>
