Email routing Operation

[Paul Morrow]

In order to automatically update a request by email I set up the attached routing rule and set it 1 in the list of rules.

It is meant to capture emails sent to the service desk with subject Re: IN00000678 or Re: SR00000678

No luck. On looking at the rule again I see the Reference for the REGEX is missing and I can't seem to make stay there no matter how many times I enter it.

What have I to tweak to make it work.

[Dan Munns]

Hi @Paul Morrow

Our update regex rule is: REGEX_MATCH(subject, '.*[a-zA-Z]{2}[0-9]{8}.*')

This picks up FW: IN00000123, FW: SR00000123, RE:, Ref:, and everything else I have thrown at it.

I think since the update to emails the reference isn't used for certain actions (like update) as they have to be as you have them pictured anyway so why not make it default.

Hope that helps

Dan

[Paul Morrow]

Nope - this doesn't stick around either. Tried to make a new rule and on clicking "Create" the Reference section returns to blank.

[Paul Morrow]

I've raised this with the Hornbill service desk in case there is something wrong with my instance.

[Dan Munns]

You need to set the rule exactly the same as in my screenshot.

It works and the ref is blank. You should be putting the regex_match into the rule expression field.

Ignore the reference field and send an email with a valid reference number (IN00000101 for example) in the subject line and it will add the email as an update on the calls timeline.

[Paul Morrow]

No difference, still doesn't work. Email are just processed by the next rule in the list.

[Dan Munns]

Are you trying to update a ticket where you are not the customer?

I think I remember seeing a post about having issues with that.

[Paul Morrow]

Hi Dan

This is one of those head melts because I know it's working for the likes of yourself.

Tried it both as customer/assigned to different owner and as customer and owner. Email always just lands in the Inbox unprocesses.

[Victor]

@Paul Morrow you need a value for the reference field. Otherwise your rule will always trigger a failure (https://wiki.hornbill.com/index.php/Email_Routing_Rules: Note: For logOrUpdateIncident, logOrUpdateServiceRequest and updateRequest operations the Reference field is a mandatory parameter). Try and use this: [a-zA-Z]{2}[0-9]{8} in the reference field and see if it makes any difference.

[Paul Morrow]

Already tried but it does not stay in the reference field. On create or save the field returns to blank.

[Dan Munns]

@Victor,

When I try and type in the field nothing shows up. It is like it instantly deletes the characters as i type them.

But for me the rules still work with the reference blank.

[Victor]

@Paul Morrow @Dan Munns just had a chat with dev, this is something they noticed this morning too (unable to edit/save routing configuration). They working to have it fixed. Apologies for the inconveniences.

[Gary@ADL]

On ‎02‎/‎02‎/‎2017 at 2:17 PM, Dan Munns said:

Are you trying to update a ticket where you are not the customer?

I think I remember seeing a post about having issues with that.

@Dan Munns

theirs a setting somewhere which you can enable to allow tickets to be updated by email by other/external users I believe

[Paul Morrow]

@Victor Any update on this issue Victor. Noticed latest Service Manager Update but no fix for email routing included.

[Victor]

@Paul Morrow it will be in the next update

EDIT: I mean next Service Manager update