search results

(...) Hi, Current Situation: data sources are typically static and context-independent. Each Data Source is bound to a fixed query or API call, with no native mechanism to pass parameters dynamically. As a result, any variation in use (such as retrieving different columns, filtering by different criteria, or adapting to different workflow contexts) requires creating multiple data sources or embedding logic else (...)

(...) ce instead of only "report data tables" with information of processes. The data source should have the same sort and filter possibilities in the dashboard as in processes. There is so much data in data sources we'd like to visualize, search, filter, ... on a dashboard. As a dev imagine a WEBCON monitoring dashboard that has lots of widgets with SQL data sources that show e.g. a mail log, login log, proc (...)

(...) data source and invoke action using the connection. My suggestion is to add default custom headers in the connection as Postman does it in the configuration of its collections. By having this all data sources and invoke actions can inherit those default custom headers. Optional further custom headers can then be configured too as it is now. This would also enable a centralized management of header entr (...)