Document Template Source Engine?
Looking to see if anyone has knowledge of the engine Quickbase is using in the Document Template (Doc Gen) feature? Reason: We are hand editing the source to gain control over the layout. Each time we paste our edited and functional HTML into the Source window and save, the Document Template engine modifies the HTML. When we print the Template the layout does not meet end User requirements. If we know what Quickbase is using, we can read the documentation and learn what HTML is allowed. It is obvious the HTML engine is not compliant with HTML5 and we are struggling. We are chasing our tails. Any ideas ... aside from using a third party solution.
Document Generation - Filename
I started playing with the Document Generation in Quickbase this week which is amazing! I am curious to know if there is a way to set the filename of a Document that is generated in a custom email notification from a Quickbase application? I know that when you use the Generate Document code to create the document for a record in the application, it does allow you to set the title/name of the document specifically. However, using the same option as a part of the custom email notification sends the notification with the PDF attached and named Document 1, rather than any name you specify in the code that is attached the Formula URL field.
Add barcodes to PDF templates
We have an app for tracking form internal processes. There is a paper printout that will travel with a part throughout the plant. I want to add a barcode to that printout so when someone needs to update the record, they can just scan the barcode (we already have USB barcode scanners at all the computers). Is there a way to take the value of a field and create a barcode?
