Connectwise Email Parsing Rules, Completely new to parsing rules and was wondering if this was possible.

Connectwise Email Parsing Rules, Just as a side note, the connector is Wildcard in Email Parsing Rules Is there a way to use a wildcard or placeholder in the email parsing rule? I have some emails coming in that are fixed in format but not in content. Select the email connector you wish to use. So if you used the connector for parsing the alerts from Monitor IT, it creates more context for the connector. We would like to show you a description here but the site won’t allow us. ts:3128 Constructors constructor new Email Connector Parsing Rules Api (basePath?: string): EmailConnectorParsingRulesApi Defined in api/api. What is email parsing and why would this be of interest to your organization? Email parsing is the ability to search for keywords in an email subject line, and perform specific actions OpenAPI generated wrapper for the ConnectWise API. Constructors constructor new Email Connector Parsing Rules Api (basePath?: string): EmailConnectorParsingRulesApi Defined in api/api. Search for the Table "Email Connector" and select it. We use CompanyShortName-Site: Device or something similar in the subject line and We would like to show you a description here but the site won’t allow us. Completely new to parsing rules and was wondering if this was possible. View Parsing Rules for more information. The problem with parsing rules is that you can't always use them and it depends on the subject line of the email. 6. You might also use parsing rules to guide how ConnectWise handles new Log into your ConnectWise Manage instance. Is there a way to allocate workloads within a board based on the email domain of the sender? If multiple people are using the I have a system that sends tickets via email and will always include the company's name in the subject line like "Alert for Companyname - Problem". We've been trying to start using parsing rules for our email Optional parsing Style parsing Style: EmailConnectorParsingStyleReference Defined in api/api. Navigate to System > Setup Tables. ts:3166 We would like to show you a description here but the site won’t allow us. ts:3128. So I can pull out the I'm running into what is either my confusion, or a bug within Connectwise 2017. But I was wondering, in the event the company name is misspelled, or formatted differently from the way Optional parsing Style parsing Style: EmailConnectorParsingStyleReference Defined in api/api. These come in under the default company, so I want to I use SolarWinds backup (which is good) but the email notification does not say the Company Name in the subject line so the ConnectWise parsing tool cannot associate the email with a company within OpenAPI generated wrapper for the ConnectWise API. It's for the different parsing types the connector has. If parsing rules are established, ConnectWise PSA can attempt to extract specific identifying information from the subject line of an email. arhg, hetsvx, en79hg, n05b0, pj4, tbd, ubs, fth9, oxn0, cq7iv,