Giorgio Maggiolo

Hi Vincent, AHHHHHHHHH!!! I did not noticed that I didn't configured the email... My bad! Thanks a lot :D Giorgio

Howdy! I was testing the 3.0.2 before going to production and I found a strange behavior for test notification: if I set the following notification: in "Being tested", the notification does not start: But if I set it in production, everything works propertly. I have this behavior only, as far as I know, I'm still testing everything, for this notification. BR, Giorgio EDIT: in the second screenshot, the first notification uses the email notification shown in the first screenshot

Howdy! I was testing the 3.0.2 before going to production and I found a strange behavior for test notification: if I set the following notification: in "Being tested", the notification does not start: But if I set it in production, everything works propertly. I have this behavior only, as far as I know, I'm still testing everything, for this notification. BR, Giorgio

Glad to be helpful :D We're all on the same boat ;) I'm having some problems with the notification to the customer (some "Errors: Some recipients were invalid." when email sent to the user), but probably due to our installation.

Hi Brendan, I was stuck with your same problem, but there is a passage in the Microsoft documentation that is pretty difficult to see: https://learn.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth#use-client-credentials-grant-flow-to-authenticate-imap-and-pop-connections After the app registration creation and the first sync, you should go to API permissions (in the App registration) and add the mail-related permissions...

BTW, when you create the token, be sure to use the credentials of the mail you're using and not of a global admin. As far as it worked on our installation, the token is created ONLY for the account you are using to authorize the operation

Hi Mark, I was stuck with your same problem, but there is a passage in the Microsoft documentation that is pretty difficult to see. After the app registration creation and the first sync, you should go to API permissions (in the App registration) and add the mail-related permissions to the one configured. BR, Giorgio

Hi Vincent, it's ok for me that the 2nd level support sees all the tickets (I have used the Allowed Organizations on their users so that they can see only the tickets of the orgs that are using). The problem is that doing so, if a service is "provided" by an organization that is not allowed for them, they cannot see it. So I was wandering whether was necessary the use of the "Provider" attribute inside the service class (that would be an easy way to resolve my specific case, but i don't know the...