Revisioning public Featurescript - Public/Private Versions in one document?

owen_sparks

Hi folks.

I'm sure this has been covered before but I can't find the post I was after.  Sorry if it's old ground.

(Question 1)
Lets say I have a document containing a FS that I've made public that I now want to develop further. 

The workflow I envisioned was to have the latest stable revision made public, and with further development revisions set to "private".  As soon as I'm happy a new version is good then it'll be set it to public.

Can I get this behavior in a single document, or should I have a separate private document for development?

(Question 2)
The latest OS update has an indicator to a user that a new version of a fs feature is available.  If the user finds the updated version has a fault can they roll back to the last version?

Cheers,
Owen S.

kevin_o_toole_1

Question 1 Not yet. Onshape currently doesn't have version/branch-specific permissions. There's also currently no way to distinguish "working" and released" versions you make (other than names). Stay tuned as Onshape's version control system becomes more refined. You're right that this is useful for way more than FeatureScript.

Question 2 Absolutely. As long as they have link permission, a user has full control over what version any feature points too.

For a specific feature in the feature tree, right-click the feature and click update to change the version of any and all specific features in that tab (more on updating linked documents). For a feature in your toolbar, right-click the toolbar icon and select update.

The most common case for both is to update to the latest version, so (as you've pointed out), the blue link icon indicates that a new version is available, and the default option in the dialog is to "update all" to latest.

owen_sparks

Thinking further this isn't limited to FS but is appropriate to all documents.

If I have a drawing I may want our in house production team to be working on Release 1, our component supplier to have sight of Release 2 and the design team to be working on Version 3.

Cheers,
O.S. 
(Also please rename Onshape; every time I go to sign my initials it looks like I'm trying to pretend I work for you...)

kevin_o_toole_1

Question 1 Not yet. Onshape currently doesn't have version/branch-specific permissions. There's also currently no way to distinguish "working" and released" versions you make (other than names). Stay tuned as Onshape's version control system becomes more refined. You're right that this is useful for way more than FeatureScript.

Question 2 Absolutely. As long as they have link permission, a user has full control over what version any feature points too.

For a specific feature in the feature tree, right-click the feature and click update to change the version of any and all specific features in that tab (more on updating linked documents). For a feature in your toolbar, right-click the toolbar icon and select update.

The most common case for both is to update to the latest version, so (as you've pointed out), the blue link icon indicates that a new version is available, and the default option in the dialog is to "update all" to latest.

owen_sparks

Thanks Kevin.

Thanks for the speedy reply.  I wasn't looking hard enough.  

As you say the Reference Manager >> Selective Update >> Version Graph option allows the user to roll to any version of a FS feature they wish. 
I think I over-thought the term "update" and came to the conclusion that it could only "update", and not "roll-back" revisions.

Looking at this the user only has the option to use a saved revision.  So a developer could have a released version and a working main "section" in a single doc.  just as long as they didn't apply a revision to it. Risky though.

Cheers,

Owen S.