option to disable the expiry warning☐ cool new feature
☑ could help all Jmp users!
☑ removes something that feels like a „bug“
☐ nice to have
☐ nobody needs it
What inspired this wish list request?
In Jmp18, a warning message appears for EVERY user - EVERY day - EVERY time Jmp is started
... unfortunately: already months before Jmp expires.
Unlike a splash window, the pop-up window remains in place until the user closes it manually.
This is how it looks like:
hogi_0-1717240535439.png
What is the improvement you would like to see?
Please
- remove the warning message [either: completely, or: after 3 seconds]
- just show the warning message 1 - 2 x before it gets disabled [automatically]
or:
- add an option to disable the warning message (like for the startup splash window).
Why is this idea important?
- less confusion for JMP users
- no annoyed license site managers
other wishes from 
hogi_2-1702196401638.png
TS-00143027
Advanced Statistical ModelingAutomation and ScriptingBasic Data Analysis and ModelingConsumer and Market ResearchContent OrganizationData AccessData Blending and CleanupData Exploration and VisualizationDesign of ExperimentsMass CustomizationPredictive Modeling and Machine LearningQuality and Process EngineeringReliability AnalysisSharing and Communicating ResultsRe: option to disable the expiry warningYou can remove the annoying window by using JMP startup script jmpStartAdmin.jsl (Scripting Guide > Common Tasks > Run a Script at Start Up)
Window("Expiration Warning") << Close Window;
though you might want to go a bit further and add some information about the expiration, in the most simple case you could print the message to log
Try(
Write(Window("Expiration Warning")[TextBox(1)] << Get Text);
Window("Expiration Warning") << Close Window;
);
or maybe show it once every ten days or something
Edit:
Even better idea might be to create an add-in which just runs that script on start up.
Re: option to disable the expiry warning" and add some information about the expiration"
argh, I missed the chance this year ; )
Re: option to disable the expiry warning - Status changed to: AcknowledgedRe: option to disable the expiry warningBecause of this issue, JSL scripts cannot be used reliably for automation.
Re: option to disable the expiry warningWhat type of issues are you facing due to JMP18's expiry warning (I don't think JMP18's expiry warning should block anything as it is just extra window which opens)?
Re: option to disable the expiry warningActually, I had mistaken the license expired warning (which I am seeing) for a license will expire warning. Nonetheless, it would be nice to have a workaround to prevent this.
The issue I face is that JMP effectively hangs when my automation workflow tries to run JSL code, making it unusable.
Clearly, the resolution is to acquire a new license. But that's outside of my control.
I think it would be much, much better if JMP/JSL did not run at all, rather than allow a grace period.
Re: option to disable the expiry warningExpiry warning starts 60 days before the license expires. And due to the switch from SAS license to JMP license it's not possible to do anything against the warning.
Even if the new JMP license is ordered and maybe paid - it will start on day XY, not one day earlier - many days to enjoy the expiry warning.
Re: option to disable the expiry warningHi @hogi, to be clear, my license has already expired, and this is the popup that makes this notification, (which I understand is different than the issue raised by OP, but is still effectively the same issue).
In this case, I would expect that purchasing a new license would fix the issue.
Re: option to disable the expiry warningyes. purchasing a new license will fix this issue.
Re: option to disable the expiry warning - Status changed to: AcknowledgedRe: option to disable the expiry warning
We see the same issue at our company. Many users receive the expiry warning and assume their JMP license is no longer valid, which generates unnecessary support requests.
A simple solution would be to add a preference:
☑ Disable license expiration warnings
This does not need to be a complex administrator feature. In centrally managed deployments, organizations already control default JMP preferences, so this setting could simply be configured as part of the standard setup. Users who want to see the warnings could still leave the option enabled.
The current warnings provide little value to end users because they typically cannot renew licenses themselves, while the warnings create considerable confusion and support overhead. This feature would be especially beneficial for companies with centrally managed licenses and large JMP user populations.
