Attachments, Specification Documents, Documents and Engineering Documents...

Hello,
maybe someone can point me in the right direction to better understand those different object (or same object named different):

In ENOVIA Product Structure Editor, you can add to Physical Product, a Specification Documents and an Attachments; for both, just select a file from filesystem and for both a new object Document type has been created.
In ENOVIA Relations, for Physical Product, both Specifications Documents and an Attachments are correctly display: Specification Documents as specification docs relation (1 items) and Attachments as attachment relation (1 item) and

On Rich client, if you explore same Physical Product and Show Attached Documents, nothing is added to tree.

On Rich client, you can add to Physical Product, a Documents and an Engineering Documents:
- For Documents, a new object Document type has been created.
- For Engineering Documents, a new object Engineering_Document type has been created.
Both Documents and Engineering Documents are added to tree

Back in ENOVIA Relations, for Physical Product, all four Specification Documents, Attachments, Documents and Engineering Documents are displayed: Attachments as attachment relation (1 item), Specification Documents, Documents and Engineering Documents as specification docs relation (3 items).

Back in ENOVIA Product Structure Editor:
- in Specification Documents tab, new object Document type previously created on Rich client has been added
- in Attachments tab, still present only the initial attachment object.

So, seems to be no place where all different objects are visible (except for ENOVIA Relations)

Can someone please explain this different objects type and the reason behind this different representation in widget and rich client?

Thanks,
Mauro


@ND , @RH