I'm trying to figure out how to make the regexp in JEMH match multiple values for a field.
So the field will select how ever many options are chosen in that email.
I've tried a few configs with multiple regexp expressions (only the last one gets it's value entered)
I've used the (Charger - AC|Charger - Car): True which doesn't give me any value despite getting a match on both values.
(Charger - AC): True,(Charger - Car): True and (Charger - AC,Charger - Car): True just gives me a does not match.
the text it's checking against is:
Type of Device\t Type of Request\t Accessories\n Aircard: False\t New Activation: False\t Charger - AC: True\n Cell Phone: False\t Replacement Device: True\t Charger - Car: True\n Blackberry: False\t \t Case for device: True\n
The supported fields page says use a comma, but I can't see any thing suggesting how the comma is used. Or it simply won't do what I'm after.
Hi Jason,
Regexps are split on comma characters, so you can't use a literal comma in a regexp but you can use \x2c instead (wiki)
JEMH Regexp Field Processor has a field for determining matches, (match one or match many), values matching a given expression are then set against the target field, eg CSV results in a split on the comma generating many values, which could then populate a select custom field.
Its probably easier if you're having problems to log a support ticket, with your Profile XML and an example email, exported from JEMH auditing so that it can be reproduced. Lay out what you want as final field values...
ends up this was related to the Capture Group correctly pulling out values, but the Aliases that those values were supposed to match on to 'translate' to JIRA options, were not right, included text not captured, hence no Alias match, and no set option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.