Service Catalog forms support customization on a form by form basis by allowing you to place to write your script and specific events to call those scripts. This works well.
There is also the option to write scripts that would be used on multiple forms and place them in this location. USM_Home\filestore\custom\explorer\scripts\custom_form_lib.js. This is useful for thing like checking date fields for past dates which can happen on multiple forms. I've run into issues of browsers caching this file on user machines. If the form definition updates without the .js definition updating any user that uses the updated form will receive errors. I know a common method for handling such things is adding a version number or some unique numbering so the new reference will force the user to pull a fresh file, however I'm fairly certain within the confines of Service Catalog you cannot do this.
Has anyone run into this and come up with a solution? Is there a standard method to handle this within Service Catalog?