RELATED IDEAS
Include more email information
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
Customer users and partners working with multiple environments |
What impact would it make? |
Better understanding and call to action when the emails include more precise data - for example, why did I get this email? From which environment do they come? |
How should it work? |
Add customer and environment name within the email notification Add more information about where the X number of entities awaiting my attention is in the workflow Possibility of selecting/deselecting email notifications (either entirely or per workflow or per user and workflow (should it be part of the creator or doer role?)) |
Why is it needed? |
When emails are sent without understanding of why, and users get several per day, there is a high risk of them losing value and get disregarded. |
Additional feedback, background or context:
I get several emails per day:
Upon checking them, I can't tell from which environment they come (is it test or prod? business unit (customer safename) a or b?)
Does the minus in the email indicate entities that have been added or removed from the assignment? Are the 7 entities awaiting my attention in the same assignment?
See also this question in the community: https://community.inriver.com/hc/en-us/community/posts/14430826050332-E-Mail-notification-for-assignments-created-via-Workflow
We fully support this request! From our experience, users often get multiple emails for the same workflow because each trigger point sends a notification. Since the emails already show all trigger points, one email per workflow would be enough.
What would make them really useful:
One email per workflow is enough, even if multiple trigger points exist.
Clearly show which workflow triggered the email.
Indicate which environment (test/QA/prod).
This would make workflow notifications much clearer and reduce unnecessary email noise.