Is it possible to share a dashboard with a role and suppress the invite email

[michaelcory]

Would like to create a Dashboard to replace the Change Overview portal page link (Under the Change Application Menu).   Need to share the Dashboard with the ITIL role, but don't want to send an invite email to the 600+ users that have the ITIL role. 

Any way to suppress the email that triggers after clicking the invite button on the Sharing function from the Dashboard or some other way to Share the Dashboard without triggering 600+ emails?

[pagdenl]

I added a group back in and then quickly went to the emails logs and deleted the emails.  Not a solution but it worked.

[michaelcory]

Thanks pagdenl,

The solution provided by Adam Stout (Business Rule) actually works very well.  We've been using the BR to suppress the emails.  I included the link to Adam's post below:

email send ignore for the subject "dashboard has been shared with you

[Bill_Collins]

Michael, There is almost always a way around SNC trying to force our hand.  I came upon your post attempting to define another issue related to adding role access via the dashboard ui.  I'll give you an answer first and also post my found "bug."

To add a role without using the invite structure, go to the dashboard record via dashboard administration module or using the Dashboard Properties link in the dashboard menu. Configure client scripts for the record form and turn off the client script titled "Hide sections when canvas is active."  You will now see the access form section and related list for permissions.  Add your roles in the "Dashboard Permissions" related list and you are done.  No email is sent.

My issue: If I attempt to add a role permission via the dashboard UI, e.g., admin, and there are many users with "admin" in there name, the list has max entries and does not display the role.

[Adam Stout]

In London, the notification is now optional to send (there is a checkbox that allows you to decide everytime you share).  Be very careful about modifying OOTB forms since it may cause you upgrade issues later on.  You need to do it sometimes, but I try to avoid it if I can.

[Bill_Collins]

Of course, but getting on my soapbox, I think all the talk at K18 about OOC is silly [emphasis added].

It's certainly not Fred's vision.  We have an incredibly powerful tool (because of its configurability) and we are just supposed to leave it alone.  As I recall from 2006, SNC had applied for a patent on the upgrade path and the customer update table process.  The folks who get themselves into these issues suffer because.

1. they do not regularly upgrade.

2. they are modifying UI aspects

3. they are getting really essoteric

4. code-heads are making it (the configuration) way more difficult than it should be.  See #3.

5. SNC has too many cooks in the kitchen

6. SNC has rebuilt a few apps from the ground up and the migration planning was poor, e.g., SLA V1, V2.

7. SNC is writing too many UI Pages and not using the native UI, e.g., workbenches, planning boards, dashboards.  It becomes form over function.  That breaks shit.  I don't want to be controlled. 🙂

BTW: Is this notification now configurable?  I do not see it in the notification table.  If not, why?