Pain Point? Please describe.
Revision numbers are required in the API and shown in the UI. These introduce needless confusion and we have no use for them.
Desired Solution
If I never have to specify or see a revision number in the API and UI, I'm satisfied. Revision numbers serve a valid purpose internal to the system, but should never have to be interacted with by the user. The recipe types should always contain the newest revision of any job type. The behavior for "auto update" should be default and applied throughout the system.
Alternative / Workaround
Continue to rage whenever I have to update any recipe type or job type.
Additional Context
How do I know this is completed satisfactorily?
I do not see any "rev #" in the Recipe Type editor associated with recipe nodes.
job_type_revision is not required when posting a Recipe Type payload for node_type of job
recipe_type_revision is not required when posting a Recipe Type payload for node_type of recipe
revision_num is not required when posting a Strike payload for recipe of configuration
There is no Auto Update flag anywhere in the UI for Job Types or Recipe Types. This should not be in the API either. Whatever logic was applied when this was set to true in the API should always be applied.
Pain Point? Please describe. Revision numbers are required in the API and shown in the UI. These introduce needless confusion and we have no use for them.
Desired Solution If I never have to specify or see a revision number in the API and UI, I'm satisfied. Revision numbers serve a valid purpose internal to the system, but should never have to be interacted with by the user. The recipe types should always contain the newest revision of any job type. The behavior for "auto update" should be default and applied throughout the system.
Alternative / Workaround Continue to rage whenever I have to update any recipe type or job type.
Additional Context How do I know this is completed satisfactorily?
job_type_revisionis not required when posting a Recipe Type payload fornode_typeofjobrecipe_type_revisionis not required when posting a Recipe Type payload fornode_typeofreciperevision_numis not required when posting a Strike payload forrecipeofconfigurationtruein the API should always be applied.