1 ACCEPTED SOLUTION
Accepted Solutions
Printing is a difficult issue to tackle. From a text wrapping issue to fit to a unknown page size, I've dealt with this for many years. We only solved this by creating our own JSP page which called out the objects, attributes and tables we wanted. From there it was a few custom data utilities and CSS modifications to get a "printable" page. The main hurdle was the default tables in Windchill want to cut off and give you internal scrollbars (printing only shows what's visible on the screen). CSS changes allowed them to display based on the number of rows and expand to fit entire window horizontally. This does not impact the OOTB Windchill pages so users will have to use a custom action to get a printable report page for what you are asking. Before you embark on this, ask yourself what are you printing this for? If its a PDF to sent to someone, that is ok but its for archival, I would recommend against. That creates multiple sources of truth.
Printing is a difficult issue to tackle. From a text wrapping issue to fit to a unknown page size, I've dealt with this for many years. We only solved this by creating our own JSP page which called out the objects, attributes and tables we wanted. From there it was a few custom data utilities and CSS modifications to get a "printable" page. The main hurdle was the default tables in Windchill want to cut off and give you internal scrollbars (printing only shows what's visible on the screen). CSS changes allowed them to display based on the number of rows and expand to fit entire window horizontally. This does not impact the OOTB Windchill pages so users will have to use a custom action to get a printable report page for what you are asking. Before you embark on this, ask yourself what are you printing this for? If its a PDF to sent to someone, that is ok but its for archival, I would recommend against. That creates multiple sources of truth.
