on 05-11-2011 7:42 PM
Hi everyone,
In Service Desk Iu2019m trying to get an automated email sent out when the issueu2019s u201CStatusu201D changes.
The problem I have is that I want the email to only be generated if the status value has CHANGED (for example u2013 from u201CNewu201D to u201CIn Processu201D).
We've only gotten it up to this point (following a tutorial I found online).
When a user hits u201CSaveu201D it checks if the ticket status equals a particular value that I specify (for example: u201CIn Processu201D).
So if the ticket status = u201CIn Processu201D an email is sent.
Here lies the problem.
As long as the ticket status is u201CIn Processu201D, even if no changes are made but the user hits u201CSaveu201D, Service Desk will send the email.
I want to set it up so that Service Desk only sends the email if it detects the CHANGE from u201CNewu201D to u201CIn Processu201D.
Is that possible?
Hi Laurence,
You are on the right track. The technique you are looking for was introduced in note 1275036, which introduced the BAdI implementation you need. Check that note out and see if it is what you are looking for.
Jon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Jon!
Thanks for your awesome reply.
I just got it configured yesterday thanks to the your reply.
However I'm still getting the same issue (emails sent even if the status wasn't changed).
So I'm going to look into 2 things:
1. Did I set it up properly (double check my settings)
2. Did Inactivating the old setup not work
Thanks for your reply. I'll get back to you if it works!
Cheers,
Laurence
I've had great success with the implementation of badi recommended in note 865619. Also, this badi is usable in both Service Desk as well as ChaRM ticket types.
Cheers,
Pranav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.