Certain features have a "Derivation Variable" configuration which is used to get around Onshape limitations when deriving the same part multiple times, as Onshape does not allow deriving the same part with the same configuration multiple times into the same part studio (as ids are deterministic, so that would result in an id collision).
We should identify parameters with this value and automatically populate it with a UUID in the UI.
To make it easier for library admins, I suggest adding a new slice to the admin UI state to display whether a feature has a derivation variable parameter.
In the UI, we should identify derivation variables, disable the parameter (since there shouldn't be any reason for users to edit it), and add a tooltip (I suggest a question mark info icon you can hover) explaining what a derivation variable is and that it's been auto populated by the app.
Certain features have a "Derivation Variable" configuration which is used to get around Onshape limitations when deriving the same part multiple times, as Onshape does not allow deriving the same part with the same configuration multiple times into the same part studio (as ids are deterministic, so that would result in an id collision).
We should identify parameters with this value and automatically populate it with a UUID in the UI.
To make it easier for library admins, I suggest adding a new slice to the admin UI state to display whether a feature has a derivation variable parameter.
In the UI, we should identify derivation variables, disable the parameter (since there shouldn't be any reason for users to edit it), and add a tooltip (I suggest a question mark info icon you can hover) explaining what a derivation variable is and that it's been auto populated by the app.