Hello again Robert,

Glad to hear you got a bit further in your project!

I just wanted to quickly add a couple of things in response to your comments - and save you from a few more headaches :)

1. Radiobuttons don't seem to work for incoming mail. I have reported that to Remedy.(no fix yet!)
2. Drop down menues don't seem to work for incoming mail. I have also reported that to Remedy. (no fix yet!)
3. Don't forget that all fields that are to be included in emails out to your customers/users HAVE to have Public rights, otherwise they will just be blank.

Just a few heads up on things that bugged my brains.

:)
Kenneth





LISTSERV@ARSLIST.ORG
Sent by: ARSLIST@ARSLIST.ORG

2003-06-13 23:39
Please respond to arslist

To: ARSLIST@ARSLIST.ORG
cc:
Subject: ARSLIST Digest - 12 Jun 2003 to 13 Jun 2003 - Special issue (#2003-207)


Hello Kenneth,
=20
thanks a lot for your detailed information!=20
We were now able to make a little tiny test form with being able to =
make use of the modify action :-) Yay :-)
=20
The major part I now understood that you need to make use of a template =
for outgoing mails and that by doing so the modify key gets being =
added. That wasn't clear to me up to now, how that modify key gets =
generated. That and that is it not required to first let the one who =
wants to do a modify action sending a query and getting an result and =
then applying the modify as reply to the result. That gave me a =
headache and would have basically rendered the whole thing useless for =
the given purpose :-)
=20
As for the user security key. We have set a dummy user, as you =
described, which gets used for all modify actions we do need, which =
seems to be just fine. I sense the advantage it may grant though, for a =
possible need of even tighter security. Though as for the bug you have =
described, the tighter security is not being made use of up to now then =
anyway.
=20
The overall reason as of why wanting to use the modify action is, that =
we are sending orders to external hardware suppliers from Remedy as =
email and we want to have some way to make sure that the email reached =
them. Therefore just letting them reply to the email and having =
something like a radio button at the Remedy request like "Received - =
Yes No" sounds like the way to go and usefull.
=20
=20
=20
Thanks again for the provided information! That helped a great way! =
Thanks!
=20
=20
Happy weekend everyone and happy Remedy'ing,
=20
Robert

**
Hi there Kenneth and good morning (over here at least that is :-)


Oh yes, noticed that one with the Public rights. At first everything was ok when sending the template to me personally (to my admin login name which is entered over at the User form with my email adress). That part did work and everything was included.

But as soon as sending the email to someone not registered as user, everything was blank. Well, can't say I was feeling that comfortable with setting the fields in question to Public, but *shrugs*. At first security is set very tight and when wanting to achieve things it gets loosened a little over time. That's just the way things seems to be sometimes, right? :-)

About the radio button. I was testing that with a radio button (yes no) and that seemed to work. In addition there was a filter with deleting the request when radio is set to yes (that was a test filter from a previous test - reused the form - I was a little bit surprised at first seing the request being gone :-)

But then I'm not sure about the rights, if Remedy recognized my User somehow and used Admin rights? As much as that is possible?? So have not tested with letting someone modify who is not registered at Remedy User (for that part only tested outgoing HTML in general).

Sooo, suppose will take some additional time till everything is set up and tested. Also the HTML sending. Not sure if everyone is being able to read the HTML mail that good. Let's see :-)


Thanks again and greetings from Germany!

Robert


-----Ursprungliche Nachricht-----
Von: Kenneth Hellervik [mailto:Kenneth.Hellervik@HYDRO.COM]
Gesendet: Montag, 16. Juni 2003 08:39
An: ARSLIST@ARSLIST.ORG
Betreff: Re: AW: Anyone understoot the Email Template Modify Action?



Hello again Robert,

Glad to hear you got a bit further in your project!

I just wanted to quickly add a couple of things in response to your comments - and save you from a few more headaches :)

1. Radiobuttons don't seem to work for incoming mail. I have reported that to Remedy.(no fix yet!)
2. Drop down menues don't seem to work for incoming mail. I have also reported that to Remedy. (no fix yet!)
3. Don't forget that all fields that are to be included in emails out to your customers/users HAVE to have Public rights, otherwise they will just be blank.

Just a few heads up on things that bugged my brains.

:)
Kenneth





LISTSERV@ARSLIST.ORG
Sent by: ARSLIST@ARSLIST.ORG

2003-06-13 23:39
Please respond to arslist



To: ARSLIST@ARSLIST.ORG
cc:
Subject: ARSLIST Digest - 12 Jun 2003 to 13 Jun 2003 - Special issue (#2003-207)


Hello Kenneth,
=20
thanks a lot for your detailed information!=20
We were now able to make a little tiny test form with being able to =
make use of the modify action :-) Yay :-)
=20
The major part I now understood that you need to make use of a template =
for outgoing mails and that by doing so the modify key gets being =
added. That wasn't clear to me up to now, how that modify key gets =
generated. That and that is it not required to first let the one who =
wants to do a modify action sending a query and getting an result and =
then applying the modify as reply to the result. That gave me a =
headache and would have basically rendered the whole thing useless for =
the given purpose :-)
=20
As for the user security key. We have set a dummy user, as you =
described, which gets used for all modify actions we do need, which =
seems to be just fine. I sense the advantage it may grant though, for a =
possible need of even tighter security. Though as for the bug you have =
described, the tighter security is not being made use of up to now then =
anyway.
=20
The overall reason as of why wanting to use the modify action is, that =
we are sending orders to external hardware suppliers from Remedy as =
email and we want to have some way to make sure that the email reached =
them. Therefore just letting them reply to the email and having =
something like a radio button at the Remedy request like "Received - =
Yes No" sounds like the way to go and usefull.
=20
=20
=20
Thanks again for the provided information! That helped a great way! =
Thanks!
=20
=20
Happy weekend everyone and happy Remedy'ing,
=20
Robert





This posting was submitted via the Web interface