Re: Using dynamic field in notifications when creating ticket

Anthony F McInerney <[email protected]> Wed, 12 Feb 2020 20:19:32 +0000
Newsgroups gmane.comp.otrs.user
Message-ID <CALoKiCpu3w8URHHxYfjWXYF6U38ArQGv+PBT6HsdRZqjPpMBZQ@mail.gmail.com>
--===============3733864751256691814==
Content-Type: multipart/alternative; boundary="000000000000605146059e66b17f"

--000000000000605146059e66b17f
Content-Type: text/plain; charset="UTF-8"

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.



On Wed, 12 Feb 2020 at 09:06, Alexis HAUSER <[email protected]>
wrote:

> 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/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs
>

--000000000000605146059e66b17f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Alexis,<div><br></div><div>You want the followup magic<=
/div><div>I think &lt;OTRS_TICKET_DynamicField_Myfield&gt; should map to=C2=
=A0X-OTRS-FollowUp-DynamicField instead of X-OTRS-DynamicFIeld</div><div><b=
r></div><div>I believe that&#39;s correct (but i haven&#39;t got access to =
my otrs right now, some vicious googling on the forums will throw some up e=
ventually)</div><div><br></div><div>Cheers</div><div>Ant.</div><div><br></d=
iv><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Wed, 12 Feb 2020 at 09:06, Alexis HAUSER &lt;<a href=3D"mailto:al=
[email protected]">[email protected]</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0=
)"><div>Hi,<br></div><div><br></div><div>I tried to use dynamic fields in n=
otifications, using the following syntax : &lt;OTRS_TICKET_DynamicField_Myf=
ield&gt;<br></div><div>It worked for escalation notifications and others th=
ings, but it seems that the dynamic fields don&#39;t get any value when the=
 notification is sent after creating a new ticket.<br></div><div>It&#39;s r=
eplaced instead with &quot;-&quot;.<br></div><div><br></div><div>Any idea h=
ow I can update the dynamic fields values before the notification of a new =
ticket creation is sent ?<br></div><div><br></div><div>Regards<br></div><di=
v>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>

--000000000000605146059e66b17f--

--===============3733864751256691814==
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

--===============3733864751256691814==--