I've got a main table that needs a PDF generated to show all rows. That is no problem for me. I've built another table with one row with a Y/N switch setting so I can set up an action that turns the switch from No to Yes. I want that action to start the process of generating the PDF on the main data table.
When I use that switch setting action in a bot on the small table (the Y/N field), it only lets me generate a PDF of the small table. How do I sequence the bot (or bots) to trigger generation of the main table's PDF file?
Thanks, Wick
Solved! Go to Solution.
There are 2 ways to utilize PDF templates:
1) Use the given row data to produce the PDF - e.g. an invoice. In this case, the automation is triggered by THAT row to be processed and THAT row is given to the template as the row of context.
2) A stand alone template that gathers all its own data to generate the PDF document - e.g. Inventory report. In this case, a row change is also used to trigger the automation but the template largely ignores the row sent as the row in context. In some cases, the context eow might be used for parameters such start and end for the data that is selected (e.g. a monthly report or quarterly report.
It sounds like you need to the second use case. You would have some row which sets a flag to generate the report. The automation is triggered by detecting the flag is set to "Yes". The row is sent to the PDF template BUT the template uses its OWN query to select the rows from the "Main" table, ignoring the context row.
If you have already built the PDF template to produce the report you wish then its just a matter of adding a Bot that triggered when the flag is set and generates your report with your template.
There are 2 ways to utilize PDF templates:
1) Use the given row data to produce the PDF - e.g. an invoice. In this case, the automation is triggered by THAT row to be processed and THAT row is given to the template as the row of context.
2) A stand alone template that gathers all its own data to generate the PDF document - e.g. Inventory report. In this case, a row change is also used to trigger the automation but the template largely ignores the row sent as the row in context. In some cases, the context eow might be used for parameters such start and end for the data that is selected (e.g. a monthly report or quarterly report.
It sounds like you need to the second use case. You would have some row which sets a flag to generate the report. The automation is triggered by detecting the flag is set to "Yes". The row is sent to the PDF template BUT the template uses its OWN query to select the rows from the "Main" table, ignoring the context row.
If you have already built the PDF template to produce the report you wish then its just a matter of adding a Bot that triggered when the flag is set and generates your report with your template.
User | Count |
---|---|
16 | |
6 | |
6 | |
3 | |
2 |