We are facing an issue while sending email attachments to an external application (such as Paragon). Whenever we try to open the attachment from Case Notes, we receive the error: “Error sending email: CMIS Access is disabled.”

General
1

We are facing an issue while sending email attachments to an external application (such as Paragon). Whenever we try to open the attachment from Case Notes, we receive the error: “Error sending email: CMIS Access is disabled.” This issue is occurring only in the Production region. Lower environments (DEV/QA) are working as expected. Has anyone experienced this issue before, or can help identify the root cause? how to avoid this error ? really apprciate if we you could help on this issue .

2

This looks like a CMIS/repository configuration issue in Pega, not an external application issue.

If DEV/QA work and Production fails usually means one of these is different in Production:

  • attachment repository configuration,
  • repository permissions,
  • CMIS-related settings,
  • case path that resolves to CMIS/WebStorage differently in Production

compare the attachment storage setup, CMIS enablement, repository permissions, and any patch/version differences between environments.

Pega has documented CMIS-related attachment errors when the content retrieval path differs from the expected repository setup, so check the exact rule path used when opening the attachment from Case Notes.

3

Thanks for your email.

We are not using a CMIS integration rule in our application. Upon verification, we confirmed that a CMIS content repository is also not configured in the application context.

For file storage, we have selected Client File Storage.

However, we are still encountering an issue when opening any attachment from correspondence emails. Whenever the email is opened (attachment viewed from the pyBody / case correspondence), we receive the following error:

“CMIS Access is disabled”

This issue is occurring despite CMIS not being explicitly configured or used. We would like to understand why the system is attempting to access CMIS and how this can be resolved.

4

When you mentioned that you selected ‘Client File Storage’, does that mean the application is intended to store attachments in file storage / repository-based storage rather than CMIS?

I am assuming you are selecting either Web storage provider or a repository.

image
image482×533 22.3 KB

The important thing to verify is whether Production is using the same content storage configuration as DEV/QA, because the Application rule’s Integration > Content management settings determine where attachments are stored and sourced. If those differ, the runtime path for opening correspondence attachments can differ as well, which could explain the “CMIS Access is disabled” error.

if you are using a repository/file-storage approach, the content storage and content sourcing should be aligned to the same backend so Pega stores and retrieves attachments consistently. They are conceptually different settings, but if they point to different places you can end up with runtime resolution issues. For this error, I would compare the Application rule content management settings in Production vs DEV/QA and confirm that both storage and sourcing are configured consistently