Any news on reporting capabilities and limit setting? We really need more information client-side as to what each recipe is costing and doing. What's my most costly recipe? How much transactions has it used by week/month? How can I limit recipes consumption? Where do I set limits? When I'm at the end of my monthly transactions I have to "guesstimate" which recipes I should keep and which ones I should deactivate, not ideal... How do I define max thresholds for live and above all, test recipes?
I'm a big fan of Workato but you need to work a bit harder on the information we (the clients) need to make decisions and to make the best of our transactions. Just sending emails and warnings about transactions running out and available add-on packs doesn't really cut it :-)
Come on Workato!
Send us a ticket, we will try our best to assist you with your problem
Carlos Santos
Suggestion: usage statistics
Hi.
I think Workato users would greatly benefit from more detailed and customisable usage statistics. Here are a few suggestions around this topic:
1) Burndown chart
Just having a count of how many transactions each recipe spent gives you an idea of the weight of each recipe but doesn’t tell you if your limit for the month will be enough for your rate of usage. And having the spent/remaining slider is nice but it also doesn’t provide much more information than that. So a simple burndown chart would help here.
Something like a green line for your ideal burn to last until end of month (a mere reference), a black line for your actual remaining transactions each day and a red line for the usage rate trend.
It would be easy to spot that the transactions wouldn’t last until the end of the month. So the user would either deactivate less critical recipes or increase the monthly limit.
This could be available in the website and/or sent daily by email to the admins.
2) Recipes transaction usage chart
It would be nice to see a chart showing each recipes transaction usage over time. It would make it easy to see which recipes are hogging the transactions and at what times.
3) Color coded slider
You could color code your spent/remaining slider to indicate if you’re above or below ideal burn average.
4) Customisable alerts
It would be very useful to have alerts like these:
- If this recipe spends more than X transactions per day notify me;
- If my remaining transactions drop below X1, X2 and X3, notify me.
Something like that.
5) Customisable thresholds
Customisable thresholds for each recipe would be nice to control run away test recipes. For instance: if recipe reaches 100 transactions, deactivate. Nice for testing periods.
Just my 2 cents. Keep up the good work!