Aside from the CN Summary that @JeffZemsky mentioned, @d_graham has done something similar that I did in our implementation. Been working since 9.1 and now on 11.1. Creating a custom action on the CN Actions drop down:
This launches a custom JSP page in which you have it do what you want. The issue with PTC tables has always been that when printed, you only see what is in the window. Yes, you can expand it but with dynamic content, this is not practical for the end user to adjust each time. A printable rendering needs to display all rows and wrap text nicely to fit on a printed page, either landscape or portrait. Here is what ours looks like (apologize for redactions). Includes CR/CR summary data, header, status, comparison between affected and resulting items (custom table), attachments, signatures, and my favorite, BOM comparison showing BOM diff between parts in affected and its match in resulting items table. CSS was the key to getting this to render right. Heavy customization here (only UI stuff) but willing to share.
I've used two very different ways to do this.
Both technique could certainly be applied to a CN or whatever.
One way is:
Create a custom action menu option named "*Print" that the user can select from the CN info page action menu.
When user selects the Print option a JSP page opens that has passed the id of the CN to a method that gets all the info and returns it to the JSP where is is displayed to the user in any form you want.
User RMC and prints the page.
Advantage of this approach is more control over the look of the page to be printed and two clicks for the user.
Another way (I like this one) is:
1. Create a custom action menu option named "*Print" that the user can select from the CN info page action menu.
2.Create a Query Report that has all the info you need and a criteria that keys off the CN object id (You could uses number instead)
When the Print option is select by the user it opens a JSP that gets the CN object and passes it to a method that edits the report by replacing the id in the criteria with the id from the current CN.
The JSP then redirects to the edited report page.
3. The user then selects "Generate" (or maybe checks the info they want or unchecks the info they don't want).
4. From the report output the user can then select one of the OOTB option to export as PDF, HTML, etc.
Both way work well.
If you don't care about the look I like the second way as it allows an Admin to edit the report template any time and everything still works. Plus the user can check what they want displayed. You don't need to be a coder to edit the output.
Also, once you have this working it can be applied to any report template with very little work.
Here's an example where the goal was to show a WTDocument's content in the file vault.
This technique could certainly be applied to a CN or whatever.
