Yes… we definitely want to provide this as some point.
In the meantime, one thing I find useful for my FLOs is that you can create a companion Table for your FLO then add steps in the FLO to add a row to the table for each transaction you care about and include columns for all values you might want to search/filter for later. We don’t have built-in search in our table UI, but you can export any table to CSV and then open up in a spreadsheet to do searching, filtering, sorting and analysis.
One advanced tip is you can also have a column where you write the unique ID of the FLO execution that created that record. Or even build the URL that will take you right to viewing that particular execution in FLO History in the following format:
https://designer.ui.azuqua.com/designer/<your-org-id here>/<the FLO ID here>/exec/<unique execution ID>.
You can get the unique execution ID from the “context” section of the FLO’s event card.
Hope that helps. Appreciate the suggestion!
Azuqua Prod Mgr