Think you can achieve this with the following:
$(Find(Subject, "**Auto Generated Email**") != -1)
The Find() function searches for param 2 within param 1, if it cannot find this, then it returns -1. So we are basically saying: Only continue if this string is in the subject.
This appears to propagate after save, if you would want this to populate before save, then a calculation rule may be what you are looking for (potentially a few problems with this though - let me know if you want this and I can look into it further).
I actually thought of this based on your response to Request Offering, Request Form: CurrentUserField("DN") does not work
I agree rhaa, your expression seems fine.
How exactly did you test the trigger, and what is the expected outcome (does this set a field, show image on form, send notification etc.)?
Are there any other rules related to Subject/IsSecurityIncident which could conflict?
it's just a Checkbox, see yellow Highlight in scrreenshot below.
I just sent an Email: **Auto Generated Email** Test Mail .....
to our Incident Mailbox.
HEAT successfully createt an incident, but the checkbox value was false and not true.
I Checked Database and noticed that Field Value ist set to 0 (false) instead of NULL.
I was looking for some other Business Rules and found an Initialization Rule to set Value to false for this field.
I deactivated the Initialization Rule and testet again but it's still not working.
I also changed the Find function to a simplier Version that just searches for "Auto" but it still does not work work.
it works! Thank you!