Release Management System

Pattabi

Here’s what I am thinking. Please let me know if this is possible:

I would like to use the Onshape release management system after a part is released. I have set up a few property categories to select the right manufacturing process. For example, if a part is marked as Sheet Metal in the properties, I would like the system to automatically create and attach a DXF file to the same document and STL file if the part is marked as 3D Printed when the part is released.

Also, when the part is updated, the document should automatically update with the new revision. The main idea is to keep all related files in one place, so anyone looking for specific data can find everything directly in the Onshape document without switching between different platforms.

I know Onshape currently doesn’t offer this service. Are there any apps that provide this feature? Please let me know your thoughts on this.

Thanks in advance!

Caden_Armstrong

Onshape natively can't do this, but the API has something called "webhooks" where an integrated application can receive notifications when certain things happen - such as a release - which could then trigger actions in your application. Its certainly not low hanging fruit, but it is possible.

https://onshape-public.github.io/docs/app-dev/webhook/

But from a workflow standpoint - if you export a DXF and upload it after a release, the file is always going to lag behind the release. If you go to some version, the DXF file in that version won't be of that version - it will be the previous version. It makes more sense to export/upload the DXF file before the release happens so that the file matches the model.

Caden_Armstrong

Onshape natively can't do this, but the API has something called "webhooks" where an integrated application can receive notifications when certain things happen - such as a release - which could then trigger actions in your application. Its certainly not low hanging fruit, but it is possible.

https://onshape-public.github.io/docs/app-dev/webhook/

But from a workflow standpoint - if you export a DXF and upload it after a release, the file is always going to lag behind the release. If you go to some version, the DXF file in that version won't be of that version - it will be the previous version. It makes more sense to export/upload the DXF file before the release happens so that the file matches the model.

Pattabi

Hi @Caden_Armstrong,

Thanks for the suggestion. I guess it makes sense to do the step before the release. The only reason I wanted to do it after the release is that I don’t want to proceed without knowing if the part is approved or not. But you’ve made a valid point — I’ll consider doing it before releasing.

I’m new to the Onshape API. Can you guide me on how to set up webhooks or share any videos that explain the process?

Caden_Armstrong

I've linked the documentation,

https://onshape-public.github.io/docs/app-dev/webhook/

As far as I know that is the only resource on the subject area.