How to programmatically enable "Show as Graph Reference Lines" in Spec Limits property of a column?

[#1]

I am the recipient of a data table where each column has spec limits defined under its Column Property. I would like show these limits as reference lines in my charts when I plot the column data. How do I enable  "Show as Graph Reference Lines" in Spec Limits property for each and every (or some selected) columns in a data table?

[#2]

I think using Manage Limits is easiest option even without any scripting

and it is also fairly simple to script

Names Default To Here(1);
dt = Open("$SAMPLE_DATA/Semiconductor Capability.jmp");
obj = dt << Manage Limits(Process Variables(dt << Get Column Group("Processes")));
Wait(1);
obj << Show Limits All;
obj << Save to Column Properties;
//obj << Close Window;

[#3]

@jthi 

On JMP 16.2.0 doing it manually works (i.e. all grouped columns get the "Show as Graph Reference Lines" checked) but the script is not working i.e. "Show as Graph Reference Lines" remain unchecked. 

[#4 · Accepted solution]

Try Manage Spec Limits for JMP16

Names Default To Here(1);
dt = Open("$SAMPLE_DATA/Semiconductor Capability.jmp");
obj = dt << Manage Spec Limits(Process Variables(dt << Get Column Group("Processes")));
Wait(1);
obj << Show Limits All;
obj << Save to Column Properties;//obj << Close Window;

[#5]

@jthi 

Thanks JMP16 version of the script works but the end result of having the LSL/USL on the chart as reference lines is not satisfactory. JMP appears to automatically place the text LSL and USL at the extremities of the Y axis and the reference lines are hidden outside the visible y-axis range. Any way to fix this?

[#6]

How would you adjust the scale with the data and the limits manually? I am not asking about the steps taken. I am asking about your criterion.

[#7]

@Mark_Bailey  I have explained the issue here https://community.jmp.com/t5/Discussions/How-to-show-USL-LSL-lines-enabled-via-the-property-quot-Sho... . Apparently on a more recent JMP version, a satisfactory result could be expected. I am (we are) on 16.2.0 and do not want to upgrade yet.