[E.Gómez]

Hello
We're doing ticket validations via TSA with two simple buttons at solution mail, as documented here
(https://wiki.easyvista.com/xwiki/bin/vie...fusalemail)

This solutions ir right but "ugly" because Easyvista places into solution field his own TSA codes. Example of actual content of solution field (firs line is Solution text and other lines is email subject + body from TSA)
----------
Egina

S121748 - Solucion aceptada








@OPERATION@='SOLVE'

@RFC_NUMBER@='S121748'

@CHOICE@='1'
-------

There is any way to avoid EV copy this text into solution field? or some way for cleaning?


thanks

[ABBE Philippe]

(10-04-2019, 03:55 AM)egomez Wrote: Hello
We're doing ticket validations via TSA with two simple buttons at solution mail, as documented here
(https://wiki.easyvista.com/xwiki/bin/vie...fusalemail)

This solutions ir right but "ugly" because Easyvista places into solution field his own TSA codes. Example of actual content of solution field (firs line is Solution text and other lines is email subject + body from TSA)
----------
Egina

S121748 - Solucion aceptada  








@OPERATION@='SOLVE'

@RFC_NUMBER@='S121748'

@CHOICE@='1'
-------

There is any way to avoid EV copy this text into solution field? or some way for cleaning?


thanks

Hello,
We use another field to store "public resolution" (http://www.global.easyvista.com/evconnec...resolution) then all that store in SD_REQUEST.DESCRIPTION ("Resolution" field) are hide to humain.

Remember that SD_REQUEST.DESCRIPTION store all AM_ACTION.COMMENT (pb with spelling/technicien vocabulary/TSA/etc...)

P.ABBE