Hi @Gunnar -
This is a great question. A couple things to consider here:
-
Would it be possible to have the print app as a step inside the assembly instructions app rather than as a separate app? It is important to consider overall approach to building apps here. Tulip usually recommends building smaller, composable apps (so one app for each specific process) rather than parameterized apps where you have to pass information between them and they may be harder to scale.
-
I know there are some cases where you might want to keep you app design as is (parameterized) due to process complexity (high mix, etc), and in this case, there is a way to connect apps in the manner you are asking about. In fact, @danielpomeranz just posted a nifty tutorial example of how to do this here: [Video Tutorial] - Don't Repeat Yourself: Abstracting Repetitive Tulip Steps into Separate Apps - #4 by sebme
Let me know if this makes sense or you have any additional questions!