For one of our reports we prefill temp tables for performance. Without pre-generated temp data the report is unusable. As part of a larger process flow this is no issue. However because the Thinkwise platform doesn’t run stored procedures inside a REPX file this report cannot be implemented standalone.
The solution for now is a new process flow for this one report. Drawback is that in the GUI the report button then becomes a task button. This is because a new table task to fill the temp tables needs to set the process flow in motion that then generates the report.
Preceding process actions could be a more elegant solution here. I would like to be able to perform a GUI action (e.g. start a table report or table task) and have the process flow postpone the starting process action and perform another process action (e.g. a stored procedure) first. In this case the table report would be the starting process action inside the flow and the stored procedure to fill the temp tables would be the preceding process action. Then the table report button could stay in place in our end-product, right there among other existing table reports.
