Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Ever wanted to add a field that does not exist in our out-of-the-box models and you thought: We , “We don’t need a smart model to do this. I just need to look at these certain words.? For this use-case we provide a predictor you can control through the predictor settings.

First add a tag field to your format. We choose the name email_coming_from with the tag options no_reply and info After. Then, add your specified rule as a regex in the predictor settings. On the swagger page of your server you can find the endpoint /predictor_settings/{scope}. The scope is the inbox/project for which you would want this predictor to run. Inside key_value_pairs::rule_config you can specify per tag_field which regexes you want to match for a given field_name. Note that the field_name and tag options have to match exactly (case sensitive). Otherwise the prediction will be empty. We created these rules to match no-reply@contract.fit and info@contract.fit respectively:

...