JMP Wish List

What inspired this wish list request?  you should link the serial number to the user when we download the CSV file   What is the improvement you would like to see?  you linking the serial number to email address instead of us having to track it all down   Why is this idea important?  end user ease of use   ... View more

What inspired this wish list request?  When we have a listbox into a UI in jsl we cannot search elements easily into it (it's only possible with filter col selector whch is adapted to data table columns only) . A code has been proposed to do that in the community but it's difficult to make a generic solution. For a window containing several listboxes, it doesn't work properly.       What is the improvement you would like to see?  An argument << Show Filter into the listbox() object should be great.     Why is this idea important?  Many users have the same problem, hard to select the good element when there are lots of elements.     ... View more

Would like to be able to generate random values from a Weibull distribution where the threshold parameter is not 0. ... View more

☐ cool new feature ☐ could help many users! ☑ feels like a bug ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  code that is generated via << save script will generate JSL code to reproduce the same behavior - in combination with the settings in the preferences. So far so good.   But the same code - in combination with (other) settings on another system can generate a completely different behavior. One could say: so far so good - the user on the other system might have some idea why he adjusted the settings.   But things get funny when the code was generated on a system with adjusted settings in the preferences. Then - (most *) setting which fit to the current (non-standard) settings in the preferences will NOT be saved in the JSL script - and now when such code will be executed on a standard system such non-standard standard settings will be missing in the code → leading to a different behavior on a standard system. - (other **) settings which fit to the standard settings will NOT be saved in the JSL script - and therefore when being executed again on the same system (with non-standard settings) will be missing.   *) like color gradients: it's not possible to specify a gradient for a plot in JSL  (via << save script) which equals the gradient in the preferences    **) like Conditional settings of the Data filter: on a system with Conditional enabled in the preferences, it's not possible to generate a JSL code (via << save script()) for a non-conditional data filter   collateral effects: With there are CHANGED settings in the preferences, a user loses the chance to use Dashboard Builder to generate Dashboards which opens platforms on his system with STANDARD settings :( Do you use the preferences?    The only workaround: Open the source script of the Dashboard and add the respective code manually.   What is the improvement you would like to see?  Although current behavior is as designed - it is not always as expected by the users. Please optimize the behavior in a future version of Jmp.   Why is this idea important?  If a user changes settings in the preferences he should still have the chance to generate Dashboards which use the standard settings.   more wishes submitted by   ... View more

☐ cool new feature ☐ could help many users! ☑ feels like a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  The Regex search in Jmp is restricted because the user is not allowed to set all flags which are officially available for regex searches.   vs. what is possible in Jmp for Regex():   What is the improvement you would like to see?  Please add options to enable/disable all flags.   Please start with standard behavior which matches other tools.   Why is this idea important?  At the moment, with singleline option enabled, the result of a Regex search in Jmp differs from what the user expects after debugging the Regex search outside of Jmp (unfortunately, there is no Test system in Jmp which can be used to debug Regex searches): Regex: disable singleline option  So, it will be highly beneficial once  - Jmp behaves the same as the other tools. - Jmp allows all options which the user finds in other tools.         more wishes submitted by   ... View more

What inspired this wish list request?  Currently not every interactive action is capture by the Action Recorder and written to the log View.  When a JMP script is written for repeated execution of a process, it is helpful to have every action required for the JMP process to have a JSL code.  When a JMP action is not scriptable since the actions were not recorded in the Action Recorder, instructions must be written within the JSL script process for the operator to perform a specific action manually.     What is the improvement you would like to see?  Capture manual JMP actions in the Action Recorder and write to the Log View.   Why is this idea important?  Save time for the operator since the operator does not need to perform manual actions.   ... View more

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  Xpath provides a very powerful way to address individual elements in a display tree. Unfortunately, it feels like black magic and I assume that it's just used by a few Jmp power users.   Column Formulas are also very powerful. One can generate very complicated code. The difference: There is this amazing Formula Editor which allows even beginners to generate meaningful Column formulas.   such an editor is missin for Xpath queries.   What is the improvement you would like to see?  Please implement in Jmp a Xpath Query GUI. It should provide all possibilites to generate a fancy Xpath query. Examples from JMP-Discovery-2015-Mining-JMP-Reports-v10 :     There should be a live view of the query results. The entry point should be selectable from the Display Tree. Additional entry points should be available as well: - current report() - all scriptable objects within the current report     Why is this idea important?  Users experience a huge efficiency boost when they start to learn to talk to the Report elements. Xpath is a great help to do so - but it's quite complicated.   A Xpath Query GUI will provide all the necessary flexibility and guidance when working with Report entries and Xpath queries - even for Jmp Newbies :)         more wishes submitted by   ... View more

What inspired this wish list request? I quite commonly have to use XPath to access JMP report layer and usually it requires using << Get XML   What is the improvement you would like to see?  I would like to have a feature which would allow me to easily view the XML of report. In best case it would be interactive, if I select display box from report, it would go to starting tag of XML, and in "worst case" it could be new script window/open to similar place as Show Properties.    Why is this idea important?  Makes it easier to see what is under JMP reports as XML. ... View more

☐ cool new feature ☐ could help many users! ☑ feels like a bug ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  In Jmp, there are 2 approaches to generate Transform Columns. 1) by talking to a data table: - the transform column is generated with Table Scope - so, the Transform Column "lives" outside the context of the platform it is generated for. - there is a Replace option: either a pre-existing Transform Column is replaced (setting: 1) or the name of the new Transform Column is adjusted (setting: 0) - The Transform Column is easily accessible, e.g. by using the return value of the command = handle for the generated transform column 2) by talking to a report 2b)  via platform << Transform Column() - this Transform column is generated in the scope of the platform - and will we deleted once the platform is closed -> very useful :) This is why this is the default approach how Transform Columns are used in Graph Builder, Summary and all the other platforms. - unfortunately, there is no replace option. If there is a Transform Column with the same name, the command is ignored (!) and the exiting Transform Column is used instead. -  unfortunately, Transform Columns which are generated by a platform are very hard to access: how to reference a Transform Column?  e.g. how to remove a Transform Column? What is the improvement you would like to see?  Although it works like designed, it definitely feels like a bug. It's hard for a user to understand that there are several tasks doable via the GUI which are not accessible via JSL.   Please improve the functionality of Transform Columns which are generated in the context of a Platform: return a handle for the column - - analogous to the one of the first kind of Transform columns add a replace option - analogous to the one of the first kind of Transform columns   Why is this idea important?  GraphBuilder has cool features to aggregate data via Summary Statistics - but important functions are missing, like CDF . Transform Columns provide a possibility to close such gaps - but the limited functionality of Transform Columns in the context of a platform make it difficult.   Example: If a user changes the selection in a Local Data Filter - how to update a Transform Column to account for the changes?         more wishes submitted by   ... View more

Hi.  I've been writing scripts to automate visualization of distributions, fitting distributions, and reporting cpk.  I just finished a long one, and really found a lot of disparities in how the names of some distributions must be used.  This required a significant amount of debugging.  My ask is not a small one, but I would love if JSL could make usage of distribution names more consistent in order to make writing scripts more efficient and less confusing.  I will provide examples below.   My script takes a list of distribution names {"Exponential", "Normal 2 Mixture", "Johnson SU", ...} and first generates a table of random data with one column for each distribution.  It then creates distribution plots, fits the data, extracts the fit parameters for each distribution.  It also uses the Process Capability platform to compute cpk.  I rely a lot on creating JSL Quotes then substitution of the desired distribution name to get the exact code I need.   Issues: When I want to generate matrices of random data initially, I need to use "Exp" instead of "Exponential" and "Normal Mixture" instead of "Normal 2 Mixture".  J(100, 1, RandomExp(...)); J(100, 1, RandomNormalMixture(...)); J(100, 1, RandomJohnsonSB(...)); On the other hand, to fit a distribution to my data, I need to use "Exponential" instead of "Exp", "Normal 2 Mixture" instead of "Normal Mixture" and "Johnson" instead of "Johnson  SB": dt << Distribution( Continuous Distribution( Column(:colname1), Fit Exponential, Fit Normal 2 Mixture, Fit Johnson ) )  And again another naming scheme for the Normal 2 Mixture in the Process Capability platform: pc = dt << Process Capability( Process Variables( :colname1 & Dist(Exponential), :colname2 & Dist(Mixture of 2 Normals), :colname3 & Dist(Johnson), ) ) I had initially hoped I could just provide my script a list of distribution names to try, then have a for loop cycle through the list, adding the specific name to a JSL Quote, and then executing.  Instead I found out the hard way that I needed to create several if clauses to fix the distribution names for each different operation prior to substitution.   It would be great if all of this could be simplified by just using one set of distribution names for all functions and platforms.  Thanks.   [Using JMP Pro 17.2.0] ... View more

☐ cool new feature ☐ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it What inspired this wish list request?  from @ https://community.jmp.com/t5/Discussions/How-to-know-if-a-table-is-a-linked-subset/m-p/655280/highlight/true#M84437  If I try to concatenate tables with the option Append to first table, the script stops with the message:   Cannot append to table: Big Class. Possible reasons for this include: the table is locked, the table is in a platform with a by group, or there is a linked subset of the table. in access or evaluation of 'Concatenate' , Concatenate(/*###*/Data Table( "Subset of Big Class" ), Append to first table)     The error message was very helpful to identify the issue. But how to make the script robust against linked subsets?   What is the improvement you would like to see?  An addition function: dt << get list of linked subsets() will help. Then I can close the subsets via JSL.     Why is this idea important?  code won't crash if there are linked subsets. Alternatives: Jmp updates the linked data tables Jmp cuts the link automatically concatenate get a new option: Jmp_is_allowed_to_close_linked_data_tables_if_this_is_needed_to_run_this_concatenate(1)        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?  The command  New SQL Query() is very useful because it allows the user to run the Query in the background. While the query runs the user can continue to work in Jmp. Very efficient :)   The command  Execute SQL() is very useful for debugging because it sends the SQL error message to the log.   It seems that the command  New SQL Query doesn't have the possibility to log the error message ( catch Sql Query error ) and that the command  execute SQL doesn't have the possibility to run the query in the background    What is the improvement you would like to see?  If so, please make it possible to run at least one of the following codes: myquery = New SQL Query(); myquery << run; myquery << get error message; or Execute SQL (... , run background )   Why is this idea important?  With the new functionality the user has the chance to do something else while the SQL query is running to find typos in the SQL code       more wishes submitted by   ... View more

What inspired this wish list request?  I make several reports that run hourly on a server farm -- they output static reports via HTML files, and one way that I'd like to visually display if the report is stale is to have a short little JavaScript header that checks the creation time vs. the current UTC time (our company has users around the globe), and if older than 2 hours it'll turn the background red.     What is the improvement you would like to see?  I'd like JMP to natively give the UTC offset of the local time-zone.  Currently I spin up a short little Python script in the AddinLoad file to determine it, but It'd be nice to have it be native       Why is this idea important?  Having UTC offset can be handy when dealing with users across multiple time-zones.   ... View more

What inspired this wish list request?  I've experienced migrating scripts & add-in from JMP 15 to JMP 16 to JMP 17 which consume a lot of my engineering time to debug. We never know how many more versions JMP plan to release in the future. I foresee we will keep repeating this process, which really holding us back to fully automate the decision-making flow in operation. Imagine, if I have 10 scripts saved at 5 computers for machine learning which may contain >100 lines of code. Every time JMP release new version that is not compatible with old versions, I need to re-edit my scripts & test at all computers to ensure no disruption to the operation.   What is the improvement you would like to see?  -Create "add-in script converter" between versions. Maybe start with JMP 17 --> if user want to upgrade to JMP 18 license, this feature propose a new script or verify the old version code to see if it compatible.  -Maybe add this feature in "add-in manager" feature highlighted by other users. https://community.jmp.com/t5/JMP-Add-Ins/Add-In-Manager/ta-p/43736#U43736 https://community.jmp.com/t5/JMP-Wish-List/Integrate-Add-In-Manager-in-Jmp/idi-p/575114     Why is this idea important?  1. We can save a lot of time & do something else in JMP rather than keep re-edit our released scripts. 2. Easy for me to justify investment to buy more JMP license.   ... View more

What inspired this wish list request?    Set Cell Changed Function This command can only be used for tablebox, there is no similar command for data table, identify the value of a cell has been changed, and return the changed value.   What is the improvement you would like to see?  The value of a cell in a data table is modified, and the system immediately returns the modified value.   Why is this idea important?  There are now subscribe commands for modifying the rows and columns of the table, but there are no commands for the cell, which is equivalent to the missing part.         ... View more

  What inspired this wish list request? To help audiences understand what analysis they are looking at, it is important to have the metric definitions easily accessible to the analysis. If we can treat the data definitions as data (in data tables), we can easily report the definitions along with the analysis. The audience's ability to understand the analysis increases. See my presentation at the JMP Discovery Summit (Americas)   What is the improvement you would like to see? DTB=Data Table Box(Definition_Table)); //In the Data Table called Definition_Table, we can set the cell height and width within the table. Using the Data Table Box, these cells formatting are not carried over nor can be specified. (<<set height; set width; or set wrap is not enabled). It requires sophisticated jsl coding to have DTB outputted into a window or journal. //Desired coded, where the cell height, width, and wrap are pulled from the data table Ol1_Def=Outline Box("Definitions", DTB=Data Table Box(Meta_def)); //Or Ol1_Def=Outline Box("Definitions", DTB=Data Table Box(Meta_def) <<Set cell height(20), <<Set Cell width(150 ), <<Set Wrap (125));   Why is this idea important? This change makes it easy to report the meta data with the analysis vs for the analyst struggle coding this to make it work.     ... View more

What inspired this wish list request?  If I make several charts and I want them attached to my data table, I need to go to each chart and save it to the data table. (I know I can also mess around with the log file, or I could do a work flow, but sometimes things happen organically and there might be intermediate steps in the log or flow I don't want.)   What is the improvement you would like to see?  Add an option where when you select the chart icons, there is a 'Save to Data Table' option. Then you could do all of them at once.     Why is this idea important?  Clicks are time, and time is money.   ... View more

no code to insert What inspired this wish list request?    Win ratio analyses can be used for clinical trial composite outcomes, comparing treatment to standard of care.  While there is an R package (winratio) based on the Bebu and Lakin paper (see attachment below), there is no canned function that I can find in any of the JMP packages or scripts by users.  Medical device manufacturers, CRO's, and others would use this function.     What is the improvement you would like to see?    A canned JMP function based on the winratio R package.   Why is this idea important?      ... View more

What inspired this wish list request? After contacting JMP support regarding Bug when using combination of set each value, tables with same column name(s) and col statistical functions within a loop (00049239) I got to know that the way I have been using << Set Each Value and Col statistical functions (such as Col Rank() and Col Sum()) successfully for many years are unintended. The inspiration here is that the way they currently work make scripting in JMP much much faster and easier when creating new columns and if the behaviours were to change, I would have to rewrite all my scripts (most likely I will just start using something like Python at that point for all my data manipulation scripting needs).   What is the improvement you would like to see? Change the behaviour where user can use << Set Each Value with formula expression as  supported behaviour. Change the behaviour where expressions can be used as first argument (or any argument?) in Col statistical functions  as supported behaviour. Or at least provide confirmation that the behaviour won't be changing.   Why is this idea important? There are hundreds or thousands of examples in JMP community where these functions/messages are being used wrong. I use them wrong in almost all of my scripts as those behaviours are so powerful and much faster than any other options I know of in JMP. If these are to change without any notice (or even with notice) I will have to stay with some older version of JMP which still support these behaviours or start using other means for my data manipulation tasks.   Some examples from community: First Value for a Unique ID , How to calculate relativ values based on a position of a base value? , Special Formula Columns , Searching Maximum value of each row across several column and name of source column , Fill column with values based on another column with keys and associative array , JSL Companion 2nd Edition Applications of the JMP Scripting Language, Second Edition contains examples of using << Set Each value (for example 3_CreateDeleteColumns.jsl) ... View more