Link to Item/File in Thin Client as a file/item property

[j_spiradek]

Hyper link to an element in TC as a property of an element or file.
If there is a property, you could export it to other systems (XLS, ERP).

[j_spiradek]

Examples links:

General link to Item:

http://localhost/AutodeskTC/localhost/MFG#/Entity/Details?id=mSVRFTTpMQVRFU1Q6MTI&itemtype=Item
Link to Revision A:

http://localhost/AutodeskTC/localhost/MFG#/Entity/Details?id=vSVRFTTpISVNUT1JZOjE1&itemtype=Item
Link to Revision B:

http://localhost/AutodeskTC/localhost/MFG#/Entity/Details?id=vSVRFTTpISVNUT1JZOjI1&itemtype=Item

[ihayesjr]

Thanks for posting the idea. If you have multiple Thin Clients in your environment, which Thin Client would this property use?

[j_spiradek]

Hi Irvin.

I'm not sure if I understand the question well, but the link used for a particular revision (A, B, ...)

Jakub.

[ihayesjr]

Hi Jakub,

Let me try to clarify.

In your link is the server name of the Thin Client (locahost).

http://localhost/AutodeskTC/localhost/MFG#/Entity/Details?id=vSVRFTTpISVNUT1JZOjI1&itemtype=Item

In large environments, there could be multiple Thin Clients installed.

How does one choose which Thin Client should show up in this link?

[j_spiradek]

Now I understand. I didn't think about this, maybe the server address which is the publisher on replication environment?

In a replicated environment this can be a problem, there will be no problem with a single server.

Jakub.

[Anonymous]

I was looking for this very thing not that long ago.  We need to pass the link to our ERP system so the shop can open the released pdfs in thin client.  This would be very helpful to have it as an existing property.

[ihayesjr]

Implemented in Vault 2025.2 Update