Create a plugin/process so that after document generation a custom script can be executed on the document before that document is status is set to done and returned as a finished document.19 votes
planned for 21.3.0 release. Internal issue number ATE-5399
Disconnect DataSets from Datasources. If we could create a dataset seperately (Like we do with Query Tags) we could have datasets defined in the template itself and not in the datasources. This allows us to change the datasource when generating the template on the Staging or Prod machines and still have the same subset of data selected.
It would make templates much more reusable as we could define a handful of more general datasources and limit the data requested by using DataSets in the templates.3 votes
We have reviewed this idea and accepted it for future development. We will come up with a solution where you specify in the Engine to use the Dataset defined in the template instead of specifying the same query in the Engine. This way, changes made to the Dataset in the template can be used in the Engine at runtime without you needing to update the query somewhere in the Engine, but rather just by updating the template.
If this solution does not solve your problem, please let me know. Thank you for your idea and please submit any other ideas you have to improve our software.
- Don't see your idea?