In Remedy, we often have difficulties when we want to validate user input, replace and split a string based on certain pattern, or even extract token from a string that matches a pattern. For instance, we often want to validate whether an email address is typed correctly, or whether a phone number is comply with our specific format. When we want to validate user input, we must create some filters to parse user input and check it against our desired rules. Unfortunately, that is not an easy task. Building complicated validation using Remedy filter is tedious and complicated task.

The things get even more complicated when, say, we want to process an incoming email in Remedy. Have you ever imagine how to split email subject based on colon character or how to get phone numbers that are buried somewhere inside the email body?

Actually, there is a technique that simplifies those activities. That is using regular expression. Unfortunately, there is no built in regular expression functionality in Remedy.

This API filter plug-in tries to address those problems. Using this filter plug-in, we can validate user input using regular expression, split a string based on certain separator, or extract token from a string.

first of all, your jar location file is "C:/BMCSoftware/ARSystem/pluginsvr/regexfilterapi-3.0.jar" but you write it in your pluginsvr_config.xml file as "C:/BMC Software/ARSystem/pluginsvr/regexfilterapi-3.0.jar". So, remove the space in "BMC Software".

I notice that in your pluignsvr_config.xml, you write (with space after dot)

id.co.mii.filterplugin. SplitRegexFilterPlugin

id.co.mii.filterplugin. ExtractRegexFilterPlugin

id.co.mii.filterplugin. ReplaceRegexFilterPlugin

It must not contain any spaces. It must be

id.co.mii.filterplugin.SplitRegexFilterPlugin

id.co.mii.filterplugin.ExtractRegexFilterPlugin

id.co.mii.filterplugin.ReplaceRegexFilterPlugin

Note:there are some errors in the documentation. I checked the documentation of this plugin and it contains spaces as well. I will revise the documentation and reupload it.

That was the error. Changed the files, restarted the service and it's now running. Thank you for this valuable contribution.

I'm creating a def file so the call to the filter api is made using a service wich can be easier to many people (including me), and also can unitarily test the functionality or the regular expression used.

Also I will publish this plug in and the def file on my blog, citing you (if you don't have any inconvenience).