Entity Manager | Non accessible Entities | Comments Extension

[yuri]

For workflows, "object": true should do the trick, I believe.

[rabii]

It should be fine, hence this is not a core entity the comment entity is added from the extension, so it shouldn't cause any issues AFAIK.

[harrytruman]

yuri Thanks for the heads up. I wasn't able to use this entity in a workflow anyway. I'm restoring back to original.

[yuri]

Note for whomever deicides to do this change. In most cases, an entity type is not customizable on purpose. Hence, issues may occur. I recommend not doing this.

[harrytruman]

Hi rabii, Cheers to you! Thanks for quick help.

[rabii]

Hey harrytruman

You just need to create a scope file for the comment entity, create a file called Comment.json under custom\Espo\Custom\Resources\metadata\scopes and paste in the code below:

{
    "layouts": true,
    "customizable": true
}​ 

After that clear cache and rebuild the system, then the comment entity will be editable.

Cheers

[harrytruman]

Hi Everyone,

I'm trying to set up a notification workflow with this comments module to notify users of the followed target record. Basically, I want users to be notified of new comments only in the records they follow. GitHub - mozkomor05/espocrm-comments-extension: Comments extension make it possible to add collapsable comment threads to any entity.

I need to access the comments entity on the entity manager (see screenshot) but it appears to be installed as a core entity and thus, cannot be accessed through the entity manager. Is there a way to change this in the backend? It's not a critical system file so I don't mind playing around with it.

Thanks everyone for the help.

mozkomor