Ignore emails with subject match to (regular expression)

 
Author
Message
SysAider
12
 
I am wanting for more insite on this Field. How do you use multiple regular expressions in this filed or what does this filed support. I created a regular express for the three phrases I want to ignore but it stopped it from created Service Requests from all email.
SysAid Wiz
2449
 
Hello awhiting

To seperate the phrases you would like SysAid will ignore, you need to use the | sign.
For example:
out of office|spam|viagra

Best regards
Haim
Pushing IT forward
SysAider
12
 
Thanks That Worked.
Super SysAider
60
 
How about ignoring emails with blank subject lines (which translate into no Title in the SR)?
SysAid Wiz
2449
 
wallerkr wrote:How about ignoring emails with blank subject lines (which translate into no Title in the SR)?


Very good question, not sure about it, and to be sure I'v asked one of our R&D guys to assist, so you should receive a reply soon.

Best regards.
Haim
Pushing IT forward
SysAid Wiz
1768
 
Did you get an answer from R&D, Is it possible to ignore blank emails?
Super SysAider
60
 
No, nothing yet.
SysAid Wiz
2449
 
Hey guys.
Sorry for not posting it earlier.

The ignore expression currently does not support blank subjects as ignored (tried it, and it was blocking all the emails), I'v forwarded this issue to our R&D and I hope we will see this option in one of the next releases.

Best regards.
Haim
Pushing IT forward
Super SysAider
60
 
Haim,

I think I found the correct expression for blank lines - "^$" (without the quotes of course ). I am by no means a regex guru - just persistent at Googling.

I can still create SRs with non-blank subject lines, except for the other expressions I am blocking. My expression entry is "^$|\b[1-9][0-9]{2}\b|#\b[1-9][0-9]{2}\b", which blocks blank subject lines, lines containing only numbers 001 thru 999, and the same number range with a "#" in front (it's a long story but a source of contention for me). All of my SRs are at least 4 digits so this doesn't affect them.

Actually, I went back and "learned" a little more about regex (translation: Google) and modified my regular expression entry to the following (each "|" separated expression on a new line to read easier here):

^$ ->blank line

^[Ss]tore # [0-9]{3} ->
^[Ss]tore #[0-9]{3} ->-> Store (or store) # 000-999; variations of # space nnn, #nnn, or just nnn
^[Ss]tore [0-9]{3} ->

^[Ss]tore # [0-9]{2} ->
^[Ss]tore #[0-9]{2} ->-> Store (or store) #00-99; variations of # space nn, #nn, or just nn
^[Ss]tore [0-9]{2} ->

^# [0-9]{3}$ ->
^#[0-9]{3}$ ->
^[0-9]{3}$ ->-> Same as above for numbers only
^# [0-9]{2}$ ->
^#[0-9]{2}$ ->
^[0-9]{2}$ ->

We have over 200 stores that send emails in and some are new to computers, email structure, etc. (amazing, but true); others just don't want to follow the rules. I implemented these filters to stop emails from generating SR's that required unnecessary edits on our part to process (for example, you can create a SR with no title via email integration but when an admin edits the SR he/she HAS to put in a title or they cannot save the changes). The store number thing is pretty much me being anal about looking on my Blackberry and seeing SR numbers and just a store number for the description of the request.

This message was edited 2 times. Last update was at Feb. 02, 2009 03:19 PM

SysAider
6
 
Hello Haim,

I actually want to do it the other way round. I want to exclude everything that does not have a "#" in the subject. This ensures, that I can receive answers to existing requests, but new requests cannot be created via the email integration.

Best Regards

Marc
SysAid Customer Relations
1092
 
Hello Opti,

SysAid must have the # sign in order to identify if this SR is already open in the system or not.
But I would not go to the extreme of removing the text completely because it does help the receiver he could understand from the text what action was don’t on the SR.

Have a nice day,
Itay
Best Regards,
Itay