nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

User cannot access Favorites links within ShareDox Outlook Client

FC_Aqui

The following prompt is received:-

Something went wrong during communication with Alfresco. Contact your support representative.

In the Emailmanager.log the following error is received at the same time:-

<message>102824931 Wrapped Exception (with status template): 10281512024 Access Denied. You do not have the appropriate permissions to perform this operation.</message>

Note that within the ShareDox internet browser the user has no problems accessing Favorites

Find more posts tagged with

Alfresco Content Services

Comments

jljwoznica

Although not familiar with the ShareDox Outlook Client - this looks to be a permissions error. Can this user access their Favorites through Alfresco Share?

FC_Aqui

Hello, thanks for your reply.

I was thinking the same so I asked the user to try and access their favourites from Alfresco using the web browser. They had no problems so it seems to be an issue with access from the Outlook add-on.

jljwoznica

I am not familiar with the ShareDox outlook client. It is possible that there is something wrong in the API calls being used to access the repository.

FC_Aqui

The error with the user shortcuts are only happening for this user. I am unable to replicate this particular error.

However for all users browsing to anything other than Full Repository in the Repository Selector also produces the same pop up error.

I realise this is probably a seperate problem however I mention this to possibly help identify the original issue.

How would the API calls problem be investigated? Would this require changes by Alfresco rather than anything I could do?