Hi Garrett,
This is a keyword used in Email Templates by the email engine, this is why it
is forms part of the Filter qualification by BMC.
e.g. Action: Submit
As is one of the label / value pairs if using email templates to create
requests, one can assume BMC placed this in there so as not to be able to
double create and entry via RBE if you used the old incoming Email Templates as
well.
You could actually narrow the qualification down even further to check for the
use of an Email Template by add in some additional label / value pairs that
would be present with an incoming Template request:
e.g. ('Message Type' = "Incoming") AND (NOT ('Plain Text Body' LIKE
"%Action:%")) AND (NOT ('Plain Text Body' LIKE "%Schema:%")) AND (NOT ('Plain
Text Body' LIKE "%Server:%"))
If you are not using the incoming Email Template functionality at all, then
there should be no issue in using what BMC have recommended.
Kind Regards,
Carl Wilson
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Garrett Sitter
Sent: 08 February 2016 15:22
To: [email protected]
Subject: Email System Issue - Emails not Appending to Worklog
Hello everyone,
We've been having problems recently with certain email messages not appending
to the worklog properly even though they meet the required RBE rules. After
doing some logging, we were able to narrow down the problem to the following
filter:
INT:RBEEML:Email-S920-PushRBEMessage
Out of the box, the Run If qualification for this filter causes it to execute
if the following condition is met:
('Message Type' = "Incoming") AND (NOT ('Plain Text Body' LIKE "%Action:%"))
This is causing problems for us, as several of our service requests contain a
question with the phrase "Action:". As a result, any emails in reply to the
assignment notification email (or any email that contains the phrase "Action:")
will not to append to the worklog, as they fail to meet the qualification of
the above filter and do not get pushed to the RBE. As a workaround, we have
changed "Action:" to "Action :" on the affected service requests.
BMC Support has advised us that it is OK to remove the latter half of the
qualification, changing it to the following:
('Message Type' = "Incoming")
So far, I haven't run into any issues in our dev environment, but I am not
confident at all in the support I received from BMC. They spent weeks before
this was discovered trying to convince me that the problem stemmed from a
licensing issue, which I knew was not the case. As such, I'm a bit hesitant to
implement this modification and potentially break the email system in our
production environment based on their advice. I figured I'd double check with
the List to make sure that making this modification would not cause any issues.
Is there any workflow-related reason that emails with the phrase "Action:" in
the body need to be filtered?
Thanks in Advance,
Garrett Sitter
Service Management
State Employees’ Credit Union
919-376-2911
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers
Are, and have been for 20 years"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
