using the Print Steps action is very useful when one needs to print steps in an app (or save them as PDF). this action has a useful feature that eliminates the need to select multiple steps at once, by placing all the steps that need to be printed in a group.
hello @Akito, great to hear you found this useful!! you can change the order of the steps you’d like to print either by changing 1) the order of the actions or 2) the order of the Steps in the App.
can you attempt this and let me know if you’re experiencing the same issue??
hello @nitingoel82, you could add a Variable > App Info > Step Name that will display the Step Name (which you can name sequentially) when you print the Steps:
Testing this in the browser using Dev mode doesn’t seem to work but it works well in the player.
I’ve been messing around with feature this and found when adding the Variable “App Info”, “Step Name” it will only print the “Step Name” of the page that initiated the print trigger.
Hello @koncvaker ,
Are you using the same variables in both of your steps? If yes, this is the reason.
To explain further : A variable is defined for your whole app, not for a single step. If you use the same variable “Step name” in both steps, the printed value of “Step name” will be the latest value. It means that each of your step must have separated (unique) variables in order to print multiple pages.
KR,
Kevin
I created a document of measurements for a specific production item that the users could print out at the end of the quality process. The pages have same variables on the header (product name, product number etc.), but completely different variables are in the pages (two page document is created, first two stages of quality check on one page the last stage on the second page.) If I print this step group out, containing the two pages the second page is duplicated, so it wants to print three pages in the end.
This is because the same variables are used in the header of the page? Because I don’t understand how is this the intended behaviour, can you explain it a bit further please!
Hello,
Your case is indeed different from what I mentioned.
I tried to duplicate your issue but it worked fine on my end.
We will need more details/printscreens to help you on this matter.
KR,
Kevin