Re: Using dynamic field in notifications when creating ticket
Alexis HAUSER <[email protected]> Mon, 17 Feb 2020 09:13:38 +0100 (CET)
| Newsgroups | gmane.comp.otrs.user |
|---|---|
| Message-ID | <1298651383.16944073.1581927218731.JavaMail.zimbra@imt-atlantique.fr> |
--===============5088957891246515563== Content-Type: multipart/alternative; boundary="=_0f95338d-2279-4310-b1b6-7f8377cd3e41" --=_0f95338d-2279-4310-b1b6-7f8377cd3e41 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, Actually, I may have done a mistake when doing my first test : using <OTRS_TICKET_DynamicField_MyField_value> works ! Regards Hi Alexis, You want the followup magic I think <OTRS_TICKET_DynamicField_Myfield> should map to X-OTRS-FollowUp-DynamicField instead of X-OTRS-DynamicFIeld I believe that's correct (but i haven't got access to my otrs right now, some vicious googling on the forums will throw some up eventually) Cheers Ant. Hi, I tried to use dynamic fields in notifications, using the following syntax : <OTRS_TICKET_DynamicField_Myfield> It worked for escalation notifications and others things, but it seems that the dynamic fields don't get any value when the notification is sent after creating a new ticket. It's replaced instead with "-". Any idea how I can update the dynamic fields values before the notification of a new ticket creation is sent ? Regards Alexis --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: [ http://otrs.org/ | http://otrs.org/ ] Archive: [ http://lists.otrs.org/pipermail/otrs | http://lists.otrs.org/pipermail/otrs ] To unsubscribe: [ http://lists.otrs.org/mailman/listinfo/otrs | http://lists.otrs.org/mailman/listinfo/otrs ] --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs --=_0f95338d-2279-4310-b1b6-7f8377cd3e41 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: arial, helvetica, sans-serif; font-s= ize: 12pt; color: #000000"><div>Hi,<br></div><div><br data-mce-bogus=3D"1">= </div><div>Actually, I may have done a mistake when doing my first test : u= sing <OTRS_TICKET_DynamicField_MyField_value> works !<br data-mce-bo= gus=3D"1"></div><div><br data-mce-bogus=3D"1"></div><div>Regards<br data-mc= e-bogus=3D"1"></div><div><br data-mce-bogus=3D"1"></div><div><br data-mce-b= ogus=3D"1"></div><div><br data-mce-bogus=3D"1"></div><div><br data-mce-bogu= s=3D"1"></div><div><br data-mce-bogus=3D"1"></div><div data-marker=3D"__QUO= TED_TEXT__"><div dir=3D"ltr">Hi Alexis,<br><div>You want the followup magic= </div><div>I think <OTRS_TICKET_DynamicField_Myfield> should map to&n= bsp;X-OTRS-FollowUp-DynamicField instead of X-OTRS-DynamicFIeld</div><br><d= iv>I believe that's correct (but i haven't got access to my otrs right now,= some vicious googling on the forums will throw some up eventually)</div><b= r><div>Cheers</div><div>Ant.</div><br><br></div><br><div class=3D"gmail_quo= te"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor= der-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style=3D"fo= nt-family:arial,helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"><div>= Hi,<br></div><br><div>I tried to use dynamic fields in notifications, using= the following syntax : <OTRS_TICKET_DynamicField_Myfield><br></div><= div>It worked for escalation notifications and others things, but it seems = that the dynamic fields don't get any value when the notification is sent a= fter creating a new ticket.<br></div><div>It's replaced instead with "-".<b= r></div><br><div>Any idea how I can update the dynamic fields values before= the notification of a new ticket creation is sent ?<br></div><br><div>Rega= rds<br></div><div>Alexis<br></div></div></div>-----------------------------= ----------------------------------------<br> OTRS mailing list: otrs - Webpage: <a href=3D"http://otrs.org/" rel=3D"nore= ferrer" target=3D"_blank">http://otrs.org/</a><br> Archive: <a href=3D"http://lists.otrs.org/pipermail/otrs" rel=3D"noreferrer= " target=3D"_blank">http://lists.otrs.org/pipermail/otrs</a><br> To unsubscribe: <a href=3D"http://lists.otrs.org/mailman/listinfo/otrs" rel= =3D"noreferrer" target=3D"_blank">http://lists.otrs.org/mailman/listinfo/ot= rs</a><br> </blockquote></div> <br>---------------------------------------------------------------------<b= r>OTRS mailing list: otrs - Webpage: http://otrs.org/<br>Archive: http://li= sts.otrs.org/pipermail/otrs<br>To unsubscribe: http://lists.otrs.org/mailma= n/listinfo/otrs<br></div></div></body></html> --=_0f95338d-2279-4310-b1b6-7f8377cd3e41-- --===============5088957891246515563== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs --===============5088957891246515563==--