As the installing admin, I want to be able to use setup wizard to fill blank flow variable with an email address to receive any errors.
Remove the Hardcoded Email: Line ~230 in Unsubscribe_Contacts.flow-meta.xml (jrymph@salesforce.com) is a guaranteed failure. You must replace this with a dynamic variable, a Custom Metadata Type, or leave it blank for the admin to configure.
*Bug found by claude code, if you cannot find evidence of this in code, mark as resolve.
ACCEPTANCE CRITERIA
AC1: The hardcoded string jrymph@salesforce.com is completely removed from Unsubscribe_Contacts.flow-meta.xml (specifically around Line ~230).
AC2: The flow is updated to use one of the following dynamic solutions for the error recipient:
A Custom Metadata Type field.
A blank flow variable that the admin sets during the setup wizard.
A dynamic system variable (e.g., the running Admin's email).
AC3: The Admin Setup Guide is updated to include instructions on how the subscriber should configure the error notification recipient.
AC4: A static code analysis scan (e.g., Checkmarx or Salesforce Code Analyzer) runs clean against the flow without flagging any hardcoded email addresses.
As the installing admin, I want to be able to use setup wizard to fill blank flow variable with an email address to receive any errors.
Remove the Hardcoded Email: Line ~230 in Unsubscribe_Contacts.flow-meta.xml (jrymph@salesforce.com) is a guaranteed failure. You must replace this with a dynamic variable, a Custom Metadata Type, or leave it blank for the admin to configure.
*Bug found by claude code, if you cannot find evidence of this in code, mark as resolve.
ACCEPTANCE CRITERIA
AC1: The hardcoded string jrymph@salesforce.com is completely removed from Unsubscribe_Contacts.flow-meta.xml (specifically around Line ~230).
AC2: The flow is updated to use one of the following dynamic solutions for the error recipient:
A Custom Metadata Type field.
A blank flow variable that the admin sets during the setup wizard.
A dynamic system variable (e.g., the running Admin's email).
AC3: The Admin Setup Guide is updated to include instructions on how the subscriber should configure the error notification recipient.
AC4: A static code analysis scan (e.g., Checkmarx or Salesforce Code Analyzer) runs clean against the flow without flagging any hardcoded email addresses.