Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.First time visiting? Here are some places to start:
- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
Addendum - Improvements to Onshape - August 16th, 2017 - Versioned Drawing Metadata
UPDATE VERSIONED DRAWINGS TO REFLECT CHANGES TO METADATA
Also new in this latest update is an architectural change designed to improve your ability to implement a release management workflow using Onshape. This work lays the foundation for new capabilities that you will see in future releases. We are making this feature available now so that you can take advantage of this new workflow and you can read a more detailed explanation below to explain our thinking and direction.
TL;DR - Versioned Drawings can update to reflect changes to metadata.
Throughout your training and experience with Onshape, you learnt the meaning of the word “immutable”! We searched long and hard for a different one, but this word best embodied the concept that versioned data could never change. It's been that way since the start of time - or at least the public launch of Onshape in December 2015.
Since then, we have been bowled over by the adoption of Onshape across broad spectrums of industry and sobered by the reliance companies have placed upon us. We try very hard to listen to feedback and make improvements to Onshape that better our customers’ Engineering processes. One of the pressing needs that became apparent was the desire to use Onshape as the master record for release management. We are working hard on this and even though our work is far from done, we are turning on a capability that allows, for the first time, versioned drawings to update with changes to metadata. Immutable no more! But as we learnt from Uncle Ben in Spiderman - “With great power comes great responsibility” (more on this later).
These Properties (as before) can be inserted into drawing fields in the current Workspace.
Having created our Drawing, we are now ready to submit it for review. One way to do this is by creating a version - in this case , we have named the version ‘Release Candidate’.
We can also go ahead and set the Drawing ‘State’ to ‘Pending’ (here in the Version, as ‘State’ can never be anything other than ‘In Progress’ in a Workspace).
Following a review, an authorized user can (as before) go into the version properties and update these fields (as well as in this example, change the name of the version).
The change as of this latest update, is that Drawings will now automatically update to reflect changes to metadata.
(Note - no other changes to Drawings can be made)
This significant architectural change opens up new workflows for our users. It is the foundation of upcoming capabilities and our work is far from done. That said, we wanted to release this first milestone rather than wait for additional supporting capabilities.
NOTE: There are important considerations to be aware of. This does mean, for instance, that Drawings set to ‘Released’ can still be changed (“With great power ….”). Consensus said that Engineering process would prevent accidental changes. Please try out this new capability and let us know what you think.