Why doesn't the notification tell the user what item they were mentioned in?

When tagging a user in a Document's comment log, their notification tells them they were mentioned but doesn't tell them what document or offer a link in the notification to take them to that document.  

Are we missing a field when creating a document or missing additional information in the comment log when tagging a user?

Parents
  • Hi Jason, I just tested this and it looks like you found a bug! This is specific to the Documents module. If you add a Comment Log entry on a different module, such as Cases, it includes a link to the case in the Related To field on the notification.

    I would recommend submitting a case to Sugar's Support group so they can submit a bug for this; that way, it will be clear that the bug was found externally and is impacting your use of Sugar.

    Good find, and sorry you had to stumble on it!

    -Brenda

  • Hi 

    Was this resolved?


    I am having the same issue, however, this is happening for all modules including Tasks and Cases 

    Enterprise 12.0.3

    Test email received does not include a URL link to the Case or Task

  • can you tell me the bpm set up that you used to send an email?  I am stuck. Are you using the main module for tasks and then what?  help 

  • Hi  ,

    I believe the email that  is referencing is enabled by the 'Email on Mention' setting found in each user's profile:

    When that setting is enabled, users receive an email like you see in Taufique's post when they are tagged in a Comment Log post on a record. I am not aware of any way to use SugarBPM to notify users based on comment log mentions.

     - Is the issue that you are looking a plain text for the generated email? I believe the record name is hyperlinked if you are viewing the HTML version of the email sent by Sugar.

    Chris

  • didn't want to tag them just wanted to create a way when someone is assigned to a task that they get a reminder email.  Would be nice to get a pop up alert also :)

  • Hi  ,

    Sugar natively handles sending emails on assigned user changes if you have the 'Assignment Notifications' option enabled found under Admin > System Email Settings and the users have the 'Email on Assignment' option enabled under their profile. Some customers don't prefer to do that though because that means users receive emails for records in any module being assigned where they only care about alerts for a few key modules.

    You are on the right track with SugarBPM if you want to only send alerts for a specific module (or specific types of records within a module). At its foundation, I recommend the process definition have 2 start events:

    1. One for new records only
    2. One for all update records where the assigned user value changes

    Then, you would have both of those start events feed into a send message event to send an email to the assigned user on the task:

    The basic process definition would look like the following:

    This only covers email alerts. If you wanted to go to your ideal use case of generating a pop-up alert, then our plug-in, Upsert Notifications, gives you the capability to do just that! With Upsert Notifications, you can draft a notification template and define how you want the notification to be delivered. By default all notification templates are delivered to the targeted user's notification center in Sugar (the bell icon next to their avatar in the top right of the application). You can also choose to have notifications to be sent via email and/or pop-up alerts in Sugar. Once you have the template created, you can then inject that into your SugarBPM process definition so your users receive the timely alerts they can take immediate action on.

    Let me know if you would like a more in-depth demo of the plug-in!

    Chris

Reply
  • Hi  ,

    Sugar natively handles sending emails on assigned user changes if you have the 'Assignment Notifications' option enabled found under Admin > System Email Settings and the users have the 'Email on Assignment' option enabled under their profile. Some customers don't prefer to do that though because that means users receive emails for records in any module being assigned where they only care about alerts for a few key modules.

    You are on the right track with SugarBPM if you want to only send alerts for a specific module (or specific types of records within a module). At its foundation, I recommend the process definition have 2 start events:

    1. One for new records only
    2. One for all update records where the assigned user value changes

    Then, you would have both of those start events feed into a send message event to send an email to the assigned user on the task:

    The basic process definition would look like the following:

    This only covers email alerts. If you wanted to go to your ideal use case of generating a pop-up alert, then our plug-in, Upsert Notifications, gives you the capability to do just that! With Upsert Notifications, you can draft a notification template and define how you want the notification to be delivered. By default all notification templates are delivered to the targeted user's notification center in Sugar (the bell icon next to their avatar in the top right of the application). You can also choose to have notifications to be sent via email and/or pop-up alerts in Sugar. Once you have the template created, you can then inject that into your SugarBPM process definition so your users receive the timely alerts they can take immediate action on.

    Let me know if you would like a more in-depth demo of the plug-in!

    Chris

Children