Issue with the new CC: feature for notifications
This question may transform to an enhancement request if our understanding of the new cc: feature is correct.
In order to add cc: and bcc: to a notification, you must first select 'one email' instead of 'separate emails'. This works beautifully for instant notifications, but we recently got wrapped around the axle on an attempt in the digest variety.
We have an application that is fed with monthly data. We have a corresponding digest notification setup to send emails to an 'employee name' (user/group) field as a recipient on a field condition of 'status' = 'incomplete'. So assume there are maybe 3-5 records per employee that meet the criteria and there are roughly 12k employees that should receive notification.
This month, we thought it would be nice to cc: the employee's boss on the notification. However, to do so, we had to change the notification to 'one email'. Uh oh.... it wants to send ONE email to 12k employees in the To: line for all records meeting the condition! Job failed because it exceeded the number of addressees.
Sort of a shame that you cannot do cc: / bcc: on separate digest emails. We will think through an additional filter criteria that would solve our issue, but thought I'd share the scenario to see if any resident experts had any advice as to whether this is really a missed point with the cc: capability or if we missed something.
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite