What inspired this Wish List Request?
During a recent discussion with Corning and previous discussions with Wolfspeed, Qorvo, Regeneron, and others that have legacy JSL scripts. One of the biggest hurdles of getting enterprise scale accounts to migrate to a new version of JMP is the fear that a new version of the software will break existing JSL scripts and add-ins. Very few people are aware of the Compatibility Notes chapter in the Scripting Guide that covers potential compatibility issues with the previous version of JMP.
Please describe the new or improved feature or solution you would like to see.
Split out the Compatibility Notes section of the Scripting Guide into its own document. This new Compatibility Notes document should include the Compatibility Notes chapter from each of the previous Scripting Guides as far back as we have it.
Provide links to the new Compatibility Notes Document in the Scripting Index (Help > Scripting Index) and in the Help menu in the area that has the New Features document link.
What would the value be to you and/or other users if this new feature is provided?
This is an extremely common complaint from customers about moving between versions ( particularly from larger install bases). It prevents customers like Wolfspeed (using v7 through v16), Qorvo (using v10 through v17), Corning (using v14 through v17), Regeneron (v10 last time I talked to them through v16) from updating in a timely manner. This makes nurturing the account challenging from an SE standpoint and prevents the users from accessing the new features and improvements they may have asked for.
Is this an external customer request?
Current request was spurred by Corning (Casey Volino and other champions there), but the request has also come from Wolfspeed (Lance Lambert), Qorvo, and Regeneron.
Is there a competitive software package that has this feature or solution that we should be aware of?
N/A
Will this impact a renewal, expansion, or adoption at a customer, and does this put an account at risk if we do not address this?
This issue is stunting expansion and adoption efforts in strategic accounts. It also is preventing us from dealing with compliance issues related to use on servers that are blocking adoption of JMP for the Cloud (proper licensing of server use) or JMP Live (generally the better solution for the server based legacy deployments).
I have had this same discussion with Regeneron. They have many scripts that need to be validated which takes time to implement which impacts deploying the new version of JMP. One thing we have discussed wtih them is testing scripts during the EA cycle. It would be nice if the Compatability Notes appeard on the EA page so scripters would get an early warning of what may be affected.
I also have a customer, CreeLED, who could benefit from this as they are running older versions of JMP and are using legacy scripts that need to be updated and making this more visible and accessible would be helpful in getting them to upgrade to newer versions.
