cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
JMP Wish List

We want to hear your ideas for improving JMP software.

  1. Search: Please search for an existing idea first before submitting a new idea.
  2. Submit: Post your new idea using the Suggest an Idea button. Please submit one actionable idea per post rather than a single post with multiple ideas.
  3. Kudo & Comment Kudo ideas you like, and comment to add to an idea.
  4. Subscribe: Follow the status of ideas you like. Refer to status definitions to understand where an idea is in its lifecycle. (You are automatically subscribed to ideas you've submitted or commented on.)

We consider several factors when looking for what ideas to add to JMP. This includes what will have the greatest benefit to our customers based on scope, needs and current resources. Product ideas help us decide what features to work on next. Additionally, we often look to ideas for inspiration on how to add value to developments already in our pipeline or enhancements to new or existing features.

Choose Language Hide Translation Bar

Workflow Builder + Python

☑ 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:

hogi_0-1711608901080.png

 

Just add an option to choose between JSL and Python (or any other code which is allowed ...)

hogi_1-1711609710967.png

 

 

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  hogi_2-1702196401638.png