Issue Summary

An alert is created in the GUI, using the "Create alert" button, then choosing an API integration. If that alert has uppercase or mixed case tags, the tags are converted to lowercase during alert field processing, and then later returned to the original case. This means if any searches/substitutions are being done against those tags in the integration, they will not work on the tags as originally entered, only on the lowercase version.

This is reproducible on the Data Center: yes

Steps to Reproduce

• Create an API integration
• In the integration, add the {{tags}} field to the Alert message field, for debug;
• Click in Show all properties and In Details, create a property "Mixed" that extracts from tags, searching for the tag "MixedCaseTag"
  {{tags.extract(/(MixedCaseTag)/)}}
• Still In Details, create a property "Lower" that extracts from tags, searching for the tag "mixedcasetag"
  {{tags.extract(/(mixedcasetag)/)}}
• Save and enable the integration
• In the Alerts list, use the "Create alert" button to create a new alert
• Choose the integration created above
• Add a tag: "MixedCaseTag"

Expected Results

The system should search and print the tag strings regardless of the letter case, thus, both the properties added, should have results.

Actual Results

Results - On the alert just created:

• There will be a tag "MixedCaseTag"
• In the description, you should see "[mixedcasetag]"
• The "Mixed" property will be empty
• The "Lower" property will have "mixedcasetag"
  

Workaround

It's possible to add a regex search in the tag extraction to ignore the letters' case:
tags.extract(/(?i)MixedCaseTag(?-i)/)

If you choose to apply this workaround, make sure to ignore the letters' case in your searching operation too.