nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

54589_en-US

liliconcom

Questions to ask customers about deployment of new JMP versions

We would prefer that customers always have the latest version of JMP and deploy it in a timely fashion. However, we know for various reasons, there are delays in deployment. The more we know about what causes them issues, the better we can make the installer to help remove roadblocks in the future. If you have a conversation about a customer about JMP deployment, here are some questions you can ask and report back answers to devops and production management:

What is their deployment tool of choice? What software are they using to repackage and deploy their version of the JMP installer?
Are there technical reasons why the current JMP installer, built with InstallShield, doesn’t work easily with the software they are using to repackage the installer? i.e. is a delay in deployment a scheduling issue or a technical burden? This would be helpful for us to understand as we consider future iterations of the JMP install.
Do they only deploy the .1 release, or do they also repackage and deploy the .2 release? If they don't use our installer at the start, they won't be able to have their users download web updaters.
1. If they only deploy the .1 version, is this because of the IT burden of repackaging the installer, or because of other software or script validation requirements?
2. If they do deploy .2, do all JMP users get the update automatically, or is it on-demand?
Do any of their users test the production .0 version, or only the JMP EA?
Do they have a need to add custom files to the payload they install?
When they repackage the JMP installer, how do they ensure all of the minimal operating system requirements are met?