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; } } }

Make the "Manage Limits" utility more scriptable

Jordan_Hiller

A key step for many Quality-related workflows is attaching spec limits (or other limits) to process data. The Manage Limits utility makes this easy to accomplish via point-and-click; and if you're proficient in JSL, you can generate the code to do it repeatably.

It would be wonderful if the key button presses in this utility -- "Load from Limits Table" and "Save to Column Properties" -- could be captured in the enhanced log / workflow builder. The current state in JMP 17 is that the launch of the utility is logged, but not these critical steps.

Status: In Review

Comments

Byron_JMP

Jordan, I completely agree with this suggestion. Adding specification limits, control limits, or even custom metadata without coding really decreases the complexity of JMP. Having workflow builder capture step and generate code for it would be a very nice add to workflow builder.

Sarah-Sylvestre

mia_stephens

ChristianStopp

We have a JMP Live opp for which they maintain their specs in one database and their process data in another. They've inquired twice about the ability to easily update their Live reports should specs change . Of course it can be scripted, but having the capability to additionally capture this part of the workflow via the WFB would further remove hurdles to positioning/discussing Live in these manufacturing environments.

Jasean

What would be really nice here is to have a process data table open then make a call to Manage Limits supplying a limits table only (not specifying process variables). JMP would then scan the limits table and process table for matching column names and populate those columns into the process variables role as part of the Manage Limits launch. This way, a user could create one table of limits for many process variables, and JMP would automatically launch the Manage Limits utility with the appropriate process variables.

dt << Manage Limits(Load From Limits Table(LimitsDT));

It appears that none of the messages for the Manage Limits object are captured by Action Recorder. Some of these are captured in JIRA already. For example, JMP-8811 and JMP-8860. It would definitely help customers to have the actions captured - especially when trying to use Workflow Builder.

mia_stephens

See https://jmpdiscovery.atlassian.net/browse/JMP-8860