Peter Grlica

Integration gateway response postfilter [PlanID: 2023.3/45/1.7]

1

Currently there is only support for incoming requests to integration gateway, there needs to be support for response as well, especially coming from workflows. There's an existing JSON postfilter that...

# The following changes are implemented Ability to return a meaningful response via integration gateway's `Response` postfilter. This is the backend implementation that might change a bit, depending on the...

Triggering of global/filter profiler should be in settings, not only as env variable Checklist: - [ ] update service to read from settings - [ ] add a new batch...

## Route details **Frontend** - [ ] add description field **Backend** - [ ] add description field ## Route list **Frontend** - [ ] [route list consistency](https://github.com/cortezaproject/corteza/issues/518) - [ ]...

Currently the profiler requests coming into gateway are not purged in any way, so it can be a memory hog. There should be a call to action on frontend (profiler...

The profile prefilter comes in handy when taking a closer look on the input of the requests into Corteza. Sometimes you want to profile the routes after authentication, so it...

Currently the filter list is inconsistent with the other Corteza entity lists, this should be fixed to match the global UX. 

Option to display Fields horizontally in a Record block not just vertically

2

you could have a horizontal block or a vertical block

Upgrade go, node, build pipeline

1

Upgrade: - [ ] node to `21` - [ ] golang to `1.22` - [ ] build pipeline ubuntu to latest, but fix it to a version (probably 23) -...