JMP Wish List

What inspired this wish list request? We currently use Statistica to send out emails when there is an out of control data point and we are able to embed the image of the control chart into the body of the email.  I also have daily reports I make in JMP that I save out a PDF and then have to manually grab each morning and email out to user groups.  If I am out unexpectedly this causes issues for user groups that rely on my reports.    What is the improvement you would like to see?  I would like to see the ability to have JMP Live allow embedding of Images and attaching of files.  This would be a feature to use for control chart alarming but also as a stand alone feature to send out a file to a user group from any analysis.   Why is this idea important?  Many users either only have access to their email (such as being on their phone way from a computer) or need to be able to print an output from JMP to post in their manufacturing areas.  By allowing automatic file generation AND Distibution this will greatly enhance the ability of Engineers to automate routine tasks as well as expand the use of JMP for enterprise systems and eliminate the need to use something like PowerBI for Manufactuing reports and SPC. ... View more

☐ 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:   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    TS-00143027   ... View more

What inspired this wish list request? A change was noticed in upgrade from JMP 17 to JMP 18 where all table column names are automatically alphabetized rather than following programmed order.     What is the improvement you would like to see? Return to previous setting where the table column order is how the table was built.     Why is this idea important? Increased burden on large tables to reorder.      ... View more

☑ cool new feature ☐ could help many users! ☐ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  In JSL there are functions like  is control key() to get the current status of modifier keys,   unfortunately,  This function does not return the current state of the control key but rather the state of the control key at the start of another event like mouse click or key press.  Checking for modifier keys (ctrl, alt, shift) in script without mouse trapping      What is the improvement you would like to see?  As  JMP does have an internal function to get the modified key state at any time but this is not exposed via JSL. Checking for modifier keys (ctrl, alt, shift) in script without mouse trapping  ... could you please provide a JSL function to expose the current status of a modifier key :)     Why is this idea important?  This will allow JSL programmers to generate Toolbars and commands in the menu on a completely new level: depending on the status of a modifier key, different actions could be triggered (!!!)   similar add-on functionality could also boost standard platforms: - A user could specify a DEFAULT action in the preferences. If a user clicks on Subset, Summary, Tabulate, Graph Builder - holding SHIFT - the DEFAULT action is executed ... without any need to manually enter the settings. - with a control key, the action could be triggered with the RECALL settings.   other wishes from  ... View more

What inspired this wish list request?Managing a large number of jmp installations can be complicated when it comes to updating and /or harmonizing versions within a company.   What is the improvement you would like to see? On major release installation, it will be fine if InstallShield could ask this question: An older jmp version was detected, would you like to install the new version (and keep the old one) or update jmp?   and something that will be good too, keep the users preferences on major update from old to new release.     Why is this idea important? Facilitating the deployment of jmp in companies where the software is managed ... View more

What inspired this wish list request? I was running a bunch of different Proportions in the Tolerance Interval analysis that is located in the Distribution Platform and found going over a lot of different proportions to be too time consuming.  I got help with how to script out of it from the community but it seems like this should be a built in functionality   Solved: Re: Inputting a data range and "increment by" into a user input box - JMP User Community   What is the improvement you would like to see? I'd like the ability to put in a min value, a max value, and an increment value and have all the outputs ran automatically in the platform.  For an example, if my min is 70 and my max is 90 and I want to have an analysis for every 10 units I could put in something like this:    and get out an analysis for 70, 80, and 90      Why is this idea important? This will save users a lot of time when they want to see a range out outputs.  I think this style of input could be used across a range of Analysis Platforms.     ... View more

What inspired this wish list request? We need to center only the data but not center and reduce (dividing by standard deviation).   What is the improvement you would like to see? Add a new function optionnal argument to define if we don't want to divide by the standard deviation and just make a center calculation.   Why is this idea important? Could be usefull and we don't have to code this function. Better performances.     ... View more

What inspired this wish list request?  Accessing the Text to Columns utility from the main Cols menu is cumbersome and inefficient.   What is the improvement you would like to see?  Enable Text to Columns Utility to be accessed by riht-clicking the column and from the Column manager. Potentially also allow the utility to be simultaneously operated on multiple columns.     Why is this idea important?  Increased efficiency and ease of use.   ... View more

☑ cool new feature ☑ could help a lot of Jmp users! ☐ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2024   What inspired this wish list request?  With the new seamless Python Integration in Jmp18 , it's now much easier to transfer small tasks to Python.   e.g.  - JSL: read a file - Python: compute new columns - JSL: make Principal Component Analysis - JSL: Plot Data in Graph builder - use Make into Data Table -> dt2 - process dt2 in Python ... - JSL: plot the result in Jmp   Such a ping pong between Jmp and Python was already possible before, option 1) Use inline Python code within the JSL code -> very hard to debug option 2) write the actual code in Python , 'import' is as a whole via JSL   new: write the main code in Python - with some JSL calls within the Python code. -> same issue as with option 1: hard to debug the inline code (slightly reduced issue as JSL is not as strict with the indentation as Python)   What is the improvement you would like to see?  Please allow Workflow Builder to accept JSL and Python code.   At the moment, the Workflow GUI asks for JSL code:   Just add an option to choose between JSL and Python (or any other code which is allowed ...)     Why is this idea important?  It will help in both directions::  - facilitates Python integration (Python can be included as an intermediate step without additional effort) - significant improvement for Workflow Builder (no limits)     more wishes from     ... View more

Our company is now using automated scripts in JMP connecting to our Laboratory management system, LIMS, to pull data for SQC reports.  These need to be reviewed for 'bad data' prior to sending to customers.  Samples undergo multiple tests which need to be arranged in columns - 1 row per sample.  Most of the 'bad data' relates to a single test (maybe a typo or a measurement special cause) so we don't want to exclude the whole suite of testing just to remove that single point. JMP's row structure to data currently means the only way this is possible is to exclude values in column properties or delete the value from the cell.   ... View more

☐cool new feature ☐ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  How does one perform Bitwise operations in JMP formulas?  How do I perform bitwise xor operations between columns with 44-bit binary data?    What is the improvement you would like to see?  Native function for bit operations like XOR, shift bits, split bits, get bit, set bit.   Why is this idea important?  could help users who want to do bit operations in Jmp.   more wishes submitted by       ... View more

☑ cool new feature ☑ could help many users! ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2024    Short:  Let JSL Editor show which function evaluates it's arguments and which function doesn't!   Long:   What inspired this wish list request?  There is a very powerful behavior in JSL which, on the other hand, makes it difficult for new users to get started without hiccups: Some Functions evaluate their arguments and others don't.   This is very important for functions which are used for expression handling. There is a wonderful lecture by @joseph_morgan : Using JSL to Develop Efficient, Robust Applications (EU 2018 415) on the differences, how to live with them and how to use them to develop efficient and robust applications.   ...  describing the status at that time: Jmp 14 [2018]: This doesn't exist in the documentation. This is something I figured out [ ] by reverse engineering the behavior of expression handling functions. Trust me, [ ] if you do not think of these functions in this you will never get them right.   Besides the expression handling functions listed here, the same holds for all function: if you do not think of these functions in this you will never get them right: It's highly important to know if an argument gets evaluated before the function call of not.   Does this code work or doesn't it?!? dt = Expr(current data table()); myscript = Expr(get script()); dt << myscript   Unfortunately, for the JSL scripter there is no hint how the function behaves - does it evaluate its arguments or not? Maybe it just evaluates one of the arguments? Who knows? The user has to know! ... or: reverse engineering the behavior of the respective functions.   What is the improvement you would like to see?  Please implement some syntax highlighting to indicate the different ways a function evaluates - or doesn't evaluate its arguments. Add-On: Please also indicate the difference in the Scripting index.      In JSL editor, the highlighting can be activated/deactivated via a keyboard shortcut.   The Expr(_x_^2) show kind of dilemma: the argument of Expr () doesn't get evaluated. But the two arguments of ^ would get evaluated. Maybe the highlighting reacts on the position of the mouse or cursor -  just the arguments below the branch are highlighted where the mouse/cursor is currently located.   Why is this idea important?  With the new syntax highlighting, JMP will guide the user automatically to generate the right code. The user doesn't have to run the code to get an error message - or to see the wrong result ... or to reverse engineer the function - like @JosephMorgan had to do to prepare his paper.   other wishes from  ... View more

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  The Group By concept in Jmp is sooo useful! You can find it everywhere. e.g. in Graph builder one can use X/Y groups to generate split graphs - and summary statistics will automatically give the correct results for every single graph. In Platform menus, there is a By option - which splits the data into groups and every group is analyzed separately. Under the porcellain layer, there are more group by options, like the Col aggregation functions (e.g. Col Median(:height, :sex)) which automatically return separate aggregated values for groups of rows.   What is the improvement you would like to see?  Please use such Group By options wherever it is possible. let's see if other users find more places where Group By could be useful ...   here I want to focus on a Col Grouped Interpolate function which can be used in a Column Formula like New Column("interpolated", Formula(Col Interpolate(:newX, :height, :weight, by(:sex)))) It should generate an interpolation for :weight by :height - split by subgroups M/F in :sex - and use the interpolation to calculate values @ x values :newX.   In a similar way, the existing Interpolate function could be lifted to a new level by providing an argument  BY() which can be used to interpolate subgroups [for this case, I think an additional argument for()is needed to specify the groups of interest and their order] Grouped Interpolate    Interpolate(myheight, :height, :weight, by(:sex), for({"F","M"}))   Definitely worth to have it - which can be seen by the fact that users invested the time to program their own grouped Interpolate to get the results: https://community.jmp.com/t5/Discussions/Grouped-Interpolate/m-p/692358/highlight/true#M87807    Why is this idea important?  Group By is one of the concepts which makes Jmp a million times more useful for exploratory data analysis  than Excel . use this concept at as many locations in the program as possible.         more wishes submitted by   ... View more

☑ cool new feature ☐ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  edit: first part shifted to Expression Indexing: How to climb the Expression Tree?  Thanks @jthi for providing a solution: Via  Extract expr a user has the possibility to search and extract parts of Expressions. The function provides a pattern search and returns the first match.   Even Wildcards are possible :)   What is the improvement you would like to see?    A mixture of Display Tree Indexing and Data Table Indexing - just for expressions:   A more precise read access via: dt = Open( "$SAMPLE_DATA/Big Class.jmp" ); myExpr=Expr(gb = dt << Graph Builder( Size( 437, 413 ), Graph Spacing( 4 ), Variables( X( :height ), Y( :weight ), Y(:height), Overlay( :sex ) ), Elements( Points( X, Y, Legend( 1 ) ), Smoother( X, Y, Legend( 2 ) ) ) )); //instead of: Arg(Arg(Arg(Arg(Arg(myExpr,2),2),3),3),1) // I want to use: myExpr[2][2]["Variables"]["Y"(2)][1] //assign // send // Graph Builder // Variables // or like it's possible for Display Trees: myExpr["Variables"]["Y"(2)][1]   Where it gets really cool: write access similar to what's is possible via Data Table Indexing: myExpr["Variables"]["Y"(2)][1] = Expr(:height); Like Substitute - but in a different dimension! [edit] And maybe the best application of Expression Indexing:  Insert Into , e.g.: Insert Into ( myExpr["Variables"], Expr(Y(:age))) Why is this idea important?  With the Power of Expression Indexing, Expression Handling in Jmp will get easier :)         more wishes submitted by   ... View more

  ☑ cool new feature ☑ could help many users! ☑ users can remove bugs on their on ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  Via  a user can edit the main menu and [on windows systems] the toolbars.   Other menus cannot be edited. Unfortunately, some of the implemented functions have bugs - and some functions are missing.   What is the improvement you would like to see?  Please add the possibility to remove items from any right click /  red triangle / ...  menu and the possibility to add user defined items. This will allow us to fix tiny issues which won't make it into a future version of JMP - or just in many years. e.g. - Allow us to perform more actions when right clicking on column name on columns panel  - Paste Column has a bug and should be replaced with a version without bug: JMP jumps   Is it possible to customize the Add Formula Column menu to include customize functions?    yes and no: -  a user can not add  user-Defined mini GUIs , e.g. to add Modulo to the portfolio. - Existing functions cannot be added to the menu by name.   (TS-00152405)     Why is this idea important?  Less pressure on JMP developers to bugfix and fine-tune the GUI. Users don't have to wait for version N+2. -> Users will be able to bugfix and tweak the GUI on their own.   other wishes from  ... View more

☐ cool new feature ☑ could help many users! ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  A task that puzzles many new Jmp user at some point: how to create a formula column with a column reference (or a constant) that is pre-defined and stored in a variable. Use for loop variable in a formula  Use expr() to replace variable column names in a formula  JSL: How to pass a variable to a column formula  New Column Formula with JSL  How to use a variable value in a formula  Need help with expressions, column references, formulas and column renaming  Creating Formula Columns in a For Loop  Apply a formula from a list  Adding Formula Columns based on Column Name List    The good news is that an experience user can choose from a range of solutions: Insert one expression into another using Eval Insert, Eval Expr, Parse, and Substitute   On the other hand, before a user gets aware of the issue, reads the manual, finds a community post or asking for help in the community, ...  he will just start with the most simple approach: use the bare column reference (or constant) within the formula.   Then Jmp will display an error, the column formula will not work - or the formula will not work anymore after a restart of JMP.   What is the improvement you would like to see?  For an experienced user, it's very easy to identify the issue and to correct it.   So, maybe, a Jmp "Copilot" could detect the issue as well and guide the user to a solution, e.g. by providing a link to Insert one expression into another using Eval Insert, Eval Expr, Parse, and Substitute   Is it possible to automatically correct the code? via right click, maybe Jmp could automatically add an  Eval(Substitute(...)) which replaces a placeholder with the variable that was defined outside of the column formula.   Why is this idea important?  New users will lose less time identifying the error + searching for a solution.   The application case of a column reference in a column formula is the most common use case, but in principle, the same Copilot could also detect and fix similar issues where variables are not evaluated before handing them over or where variables are evaluated too early before they are handed over to the next function.   more wishes by   ... View more

☐ cool new feature ☑ could help many users! ☑removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  In general, Jmp doesn't distinguish between upper and lower case - and Jmp ignores white spaces in Symbol names. So, :age can refer to the same column as :A G E  But :age and  :A G E can be also different columns. check if column exists?    JSL ignores white-spacing for names, most people don't take advantage of this!    Let's take the Concatenate platform as an example. This platform is very picky with column names. If Table A has a column :age and table B has a column :A G E,the combined table will contain 2 columns! In general this is a nice feature: better split the columns, the user can merge them later.   But for user who lived the carefree life of "difference don't matter" - the first collision with Concatenate can be traumatic.   What is the improvement you would like to see?  In Concatenate (and other platforms?) please provide an option "Column Names: Exact match". If the option is on, Concatenate is as picky as now, if it's off, Concatenate follows the usual rules of JMP/JSL when comparing column names.   Why is this idea important?  - The option will give the user more possibilities.   - The presence of the option will generate awareness!   - The idea is related to the option Exact Match (1 |0) of   dt << has column(), which will be introduced with Jmp18: data table : message column exists(colname)?    more wishes by   ... View more

What inspired this wish list request?  Trying to move my preferences between few PCs and running into issues when ALL preferences were exported instead of just changed. For example I'm not really sure if I would really like to set incorrect CPUID as it seems to be included in Get Preferences()   What is the improvement you would like to see?  Add << Changed option to Get Preferences(). It can already be found from Get Platform Preferences() Utility Functions (jmp.com) . With this we could get the list of the preferences user has changed. You could also provide function such as "Get Default Preferences" so we could always check the default preferences JMP uses.   Why is this idea important?  Makes it easier to take backups or move JMP preferences between different laptops when not ALL preferences are copied over. ... View more

What inspired this wish list request?  Resetting preferences when changing JMP versions is problematic because pre-existing preferences often get removed. The JSL Set Platform Preferences() command does not run if missing preferences are listed. Additionally, the alert only gives a few messages at a time, so multiple iterations have to be run to work through the list.   What is the improvement you would like to see?  Is there a way to only generate the list of preferences set/modified by the user? The command currently seems to publish all preferences (unchanged/default and user set/modified). I primarily only care about the former. Is there a way to have the JSL commands ignore missing preferences? Is there a way to get a full list of missing preferences in one alert? Can JMP provide detailed documentation on which preferences ihave been removed for a major version change?   Why is this idea important?  This will enable aster changeover to and adoption of new versions of JMP.     ... View more