Some of our alerts are now available for cloning using the same ID#, which means multiple subscriptions of the same alert but with different variables and/or sending to different recipients can now be facilitated!
Now available for these alerts: ID17, ID20, ID23, ID55, ID75, ID84, ID219, ID261, ID348, ID387, ID407, ID424, ID437, ID438, ID489, ID501, ID536, ID577, ID715, ID768, ID815, ID570, ID820
(We are doing our best to identify which alerts are best candidates for our new cloning feature.)
Any alert available for cloning MUST have at least one variable that contains a different value from its other cloned subscriptions. If more than one subscription is running, the cloning will only work if that variable is different for each cloned subscription. Not all variables need to be different.
When subscribing to a clone-able alert, you must first subscribe to the alert and then after that subscription is saved, you will see an option for 2nd subscription via PLUS (+) sign:
Some alerts will have specified variable(s) designated for clone distinction. For example, ID20 requires that either Variable3 OR Variable4 be different between the clones:
While ID768 doesn't specify a variable clone distinction, Variable7 has four different options. You could then, for example, set one subscription with value of 1 (Worst by GM Dollars) and another with value of 3 (Best by GM Dollars) which would result in two separate alert emails.
Or perhaps you want ID768 to fire differently based on Contract Type. You can set VariableX with designated Contract Types:
You can determine which email output from the alert is which clone by looking at the email footer. You will see ID# followed by A, B, C, etc (a letter for each clone).
Currently, the max amount of clones is as many letters there are in the alphabet (26)!
Please note, email sending limits imposed by your email server could create issues. So if you are not seeing the expected output, please email firstname.lastname@example.org and we can check for errors.
If you have had any customizations in place for the alert (which removes you from the auto revision stream), you will NOT have access to the cloning functionality for that alert.