Enhancements for Journey Orchestrator Query Builder

Related products: None

We are starting to use Query Builder extensively and there are a few concerns with what is available currently:





1) The report coming out (and spreadsheet) is called after the original name of the Query rather than the current name. As a result, even when we modify the name in JO for the variation, the reports emailed uses the original name and this creates confusion. The alternative is to recreate the QB from scratch for every variation. =(





2) Speaking of the report - the spreadsheet only contains one worksheet to show the parameters. Can it be improved to also include the results of the query? 





3) Knowing that in the backend, this is a rule, we have no means to be able to go to the rule to amend the name issue.





4) Troubleshooting is way better in the rules editor. Can this be made available for Query Builder work in JO?





5) Can JO be enhanced to allow the selection of a rule for input?



I would love #5 especially. Lists/Queries should be allowed to be constructed independent of the program -t hat way changes to the query do not require the pause/stop/clone/relaunch of a program, and could be referenced multiple times across many programs while only needing to be modified in one place.





I would love to see the ability to send to more than one QB as well, if they were stored outside of the program.




Amen to them all. 100% agreement.




Hello Everyone!

Happy to announce that your request has been considered and included as part of the v6.12 release. Gainsight now provides detailed logs for the activities that admins perform while building and fetching data in Query Builder. Apart from logs, Gainsight also provides other details such as execution history of query builder source in programs, status, data flow diagram, and the downloading option for the result set.

You can find the relevant information in our v6.12 Release Notes

This feature is implemented in both SFDC & NXT versions.

Thanks for posting!