Onshape Best Practices

Objective: To learn about best practices when using our Onshape integration.

Difficulty: Easy

In this article you will find:

1. Administration of the Onshape Plugin
2. Releasing from Onshape to Duro

Duro and Onshape each have their own release workflows and means of managing revisions and approvals for changes to components and assemblies. This article details Duro's recommended approach to these topics to maintain the performance of both systems and ensure all data is syncing correctly between the two platforms.

---

Administration of the Onshape Plugin

Duro's Onshape plugin and Onshape should be accessed via the same user email within a single browser window.

Note that your password to log in to the Onshape plugin may be different than your password to log in to Duro's PLM web client: use your plugin password to access Duro through the Onshape plugin.

Resetting Webhooks

When the webhooks disconnect, someone who is an administrator of both Onshape and Duro must reset them. Following the reset, users who are non-admins of either or both softwares will be able to use the plugin.

When resetting the webhook, admins should wait until the plugin refreshes and the connection restored modal appears.

Onshape partner spotlight: Duro

Releasing from Onshape to Duro

Direct releases from Onshape to Duro should only be done when components or assemblies are in the Design status. When components or assemblies are in the Prototype or Production statuses, use the Duro tab in the Onshape plugin to update statuses. Then, use Duro's worfklow to create a change order and submit it for approval.

When submitting revisioned releases, ensure that the revision follows all rules of the revision scheme you've established in Duro.

Onshape Overview

When releasing from a drawing file, the drawing file must be assigned to the same part number as the top-level assembly in order to associate them.

Nested assemblies must be synced one-by-one. Select them in the dropdown and click "sync" to properly link everything within Duro.

If documents do not immediately appear in Duro after they are synced, do no re-release them. There may be a delay of up to 1 day (depending on the size and complexity of the document). If an error icon appears next to a document once it is synced, click "regenerate".