PiWeb & approving a part post-run

[[Gr...]]

I'm trying to make the "Approval" function in PiWeb useful. My ideal state would be after a part is run, the PDF is not saved/printed until the operator has a chance to review the data and click a checkbox tied to the "Approve" variable.

Currently, after Calypso generates a report, it gets saved (with a custom filepath within Calypso that includes customer, part name, serial number, etc) and printed. The PiWeb window pops up, where the data can then be reviewed. I've added a check box for "Approved part" to the header.

While PiWeb will remember the state of the box, the PDF and print out have already been generated. Telling PiWeb to save the data results in it taking me to a generic folder and not having the custom name scheme from Calypso. That's less than ideal. Is there a way I can have the data not printed/saved until it's been decided if it passes or fails? My motivation behind this is to tie the approval of a part with a operator time/date stamp.

I suppose I could not print/save the report at the time of generation, review ALL the data in a table format with a per-line approval checkbox, then generate the individual reports, but that seems like that complicates and slows down the process.

[[La...]]

Consider using the action Export all Pages as PDF --> Set Filename --> Use variables to decide the path and naming convention and have it as a stacked action where when they press the button to Write Changes and lock in the approval status, it also saves the PDF.