Best practice when updating and versioning a FeatureScript
Community,
I searched the forum, but did not find any messages that address my question.
I have successfully created a FeatureScript, versioned, and shared it with my FIRST Robotics teams. Now I want to make enhancements.
Are these the best steps for a new FeatureScript version?
- Create a new Feature Studio in the original document.
- Copy old code to new FS and add enhancements.
- Rename original FS (tab) and change the Feature Type Name in the original from "Example" to "Example v1".
- Use original Feature Type Name in the new FS.
- Commit, test, verify functionality.
- Version and share.
Do I need to make a new Feature Studio (copy) or is that the whole point of the version?
Do I have to share the FeatureScript again or would the share status remain from the first version?
If there is a best practice guide for FS version management, I would welcome a link to the document.
Thank you for your time and attention. I look forward to your replies.
Regards,
Jerry
Best Answer
-
You don’t need to copy the FeatureScript tab. Just update it and test in your document. When you’re done, create a new version and then all your team can use it. They will need to update to the latest version on their end but that is much much better than having several different FeatureScripts with similar names floating around.
Simon Gatrall | Product Development, Engineering, Design, Onshape | Ex- IDEO, PCH, Unagi, Carbon | LinkedIn
1
Answers
-
You don’t need to copy the FeatureScript tab. Just update it and test in your document. When you’re done, create a new version and then all your team can use it. They will need to update to the latest version on their end but that is much much better than having several different FeatureScripts with similar names floating around.
Simon Gatrall | Product Development, Engineering, Design, Onshape | Ex- IDEO, PCH, Unagi, Carbon | LinkedIn
1 -
Ackn. Thanks, @S1mon !
0