In this article, you will learn:
How to print all your data when an app is completed
How to design a step that is properly formatted for printing
As your company begins automating paper processes and digitizing forms on your shop floor, you still may need to print the results of different operations in order to share data properly.
If you want to print data from a Tulip app in real-time (or save to a local PDF), there are four things that you need to do:
Configure a step (or multiple steps) to match the desired print size
Design a step that will look good when it is printed
Add a button with a "Print" trigger
Customize print settings so that the size of the step fills up as much of the page as possible.
With the "Print Steps" trigger action, you can print either a single step or an entire step group at once. Each step will be printed on a separate page.
Configuring Step Resolution
To start, many users prefer to create a step group called "Reports" and add all the steps that they would like to print at once to that step group.
It looks like this:
Then, it is important to appropriately configure the steps in this group to be printed in the desired resolution. In the app, navigate to the Step tab in the Context Pane and choose "Step Resolution".
Within the Context Pane, select the desired resolution to match the paper size desired.
In PDF cases, letter portrait is often best to use. Matching the size of the paper will ensure the app view is printed out as a full page.
Designing a Step
You may be using a "Master Layout" in your app with many solid colors. Although this works well for communicating information to an operator, you probably don't want to waste printer ink on colorful steps.
Instead, you will want to remove all "Master Layout" elements from the "Report" steps, and focus on text instead.
Here's an example of a step that is optimized for printing:
This step includes 7 pieces of data from the app, as well as 5 test results. The "Print" and "Menu" buttons in the top left and bottom right have a white background so that they do not require colored ink.
It utilizes the following features within Tulip:
Grid widget to create a simple visual layout
Variable text to embed the values of different variables on the step
Button with custom coloring
Adding A Print Button
A print button requires one trigger action. It is often combined with an app completion, but this cannot happen in the same trigger. You must create a separate button to trigger the app completion.
So, here is an example of a trigger that allows an operator to print a step and go to the step after the "Reports" step group, where they can complete the app:
"Print Steps" "Reports"
"Go To Step" "Next"
You can also place the "Print" button on a normal step, and use it to print an entire group of steps without even showing them to the operator.
This will open the computer's default print options.
Customizing Print Settings
Operators use the Tulip Player on screens of all sizes. So, you will need to do the following on each computer that is running the Tulip Player and requires a step to be printed or saved:
Change the page layout to match the resolution of the steps to be printed. Ex. Letter Portrait.
Save these settings locally as a "preset" so that operators can easily select it in the future:
In order to check that the app will print correctly, you should use the "Preview" option in the print dialog to see what the app will look like before you print.
Filling In Fields On A PDF
You can also print out a "filled in" PDF by embedding the PDF on a step, and then placing "Variable" text widgets on top of the PDF in the appropriate places. The step will print as displayed in the Tulip Player.
Here's how to do that:
Embed a PDF on a step that is sized to the appropriate resolution.
Add "Variable" text widgets on top of the appropriate fields from the PDF. These will be dynamically filled in when the app is used in the Player.
If the PDF has multiple pages, add a new step in Tulip for each page in the PDF and repeat the pattern above.
Saving the App Data Locally in A PDF
The print dialog is also the best way to save app data on a local computer in a PDF. Rather than pressing "Print" in the system dialog, select "Save as PDF" to save the step and live data in a local file.
Here are some rules around which app content will not work well when printed.
Any references to “Current Step” in a "Variable" text widget will only work on the step that is open when the "Print" button is pressed.
"On Step Enter triggers" will not fire on any printed steps, so you should ensure that the correct data is already added before pressing "Print".
Machine Attribute Widget: These will rarely work properly. A better pattern for a report that wishes to capture the last known output would be to have a trigger on machine output that stores that output into a local variable, which is then displayed via some custom widget.
Videos: For Youtube videos, the banner image will not load.
Did you find what you were looking for?
You can also head to community.tulip.co to post your question or see if others have faced a similar question!