Incident Management Rules GUI Improvement/Issues

We have encountered a few bugs/quirks with creating/editing/managing Incident Management Rules.

Bugs

1. When attempting to edit an ELSEIF clause, the changes will not be accepted, and the only way around this has been to delete the clause and re-add it.

2. When creating more than 1 ELSEIF clause, the ESLEIF get's inserted between the first IF and the next clause, rather than at the end, which makes it almost impossible to craft your logic one step after the other.

3. When using Regex in the match input, and then accepting the changes, the match is converted to UPPER CASE, including when a "\s" was used. For those of us that "speak" regex, this is not friendly, nor does it represent the intent.

Enhancements

1. Allow for "nested" IF statements. For instance, what if you want to check if the Alarm is a "Service" But then you want to look for 1 condition, and then another, but both for a "Service". The only alternative is to add an ELSEIF that again checks if the Alarm is a "Service", and add the other condition.

2. All for OR statements, which would allow checking for 1 condition OR another. Again, it is possible to achieve this with adding another ELSEIF and checking all the necessary conditions, but clumsy and not "programmatic"