Release multiple levels of versioned assemblies in one release candidate.

FChien

This suggestion is to enable versioned release of parent assembly with all child assemblies using one release candidate.

Currently:
An assembly with multiple layers of subassemblies must be released sequentially from the lowest level child part all the way up to the top level parent assembly. This is required to ensure each parent assembly is referencing the correct/ latest released version of a child part.

This process forces the release workflow of a complete assembly to take a very long time because each assembly has to be drafted, initiated, and reviewed before moving to the next level up. In any other CAD program you are able to release an entire assembly tree of parts in one release candidate.

Ask/Proposal
Is it currently possible to reference a "PENDING VERSION RELEASE" in a parent assembly so that once the overall release candidate is approved, all references are pointing at thelatest released version?

The closest thing to this at the moment is referencing MAIN which could be dangerous as that tab could contain unapproved changes, and thus undesirable. Additionally, the way it currently works requires each time a child assembly is revised, the parent assembly needs to be revised as well to ensure the correct configuration is referenced (opposed to auto demanding the latest released revision)

This capability would easily eliminate weeks of design release time per year.

adrian_vlzkz

Agree, this is one of the pitfalls I've found with Onshape. The assumption is, that collaboration trumps everything; when in reality, once a design enters a controlled stage, you need that "Control", not agility.

The current approach works great early in development, when iteration and flexibility have a lot of value, but in later phases that "Always WIP" approach causes a lot of extra work and confusion; especially once designs starts integrating into other systems (PLM, MRP, ERP).

My feedback is just that the MAIN workspace should accessed/referenced intentionally, not by default, and that could be an Enterprise setting, Ideally set by team/project/scheme