This week's release contains more bugfixes and small improvements
We are working on the next big feature, coming soon !
App
- layout improvements
- better (formatted) display of timestamps in rule executions
- no longer possible to create a field called "id" in the data model which was causing errors (the name is reserved)
API
- It is now possible to configure a separate database for ingested data (separate from the main db containing organizations, scenarios, decisions, cases...). This is mostly useful for our managed service, but may be helpful for some self-hosted deployments at scale.
- Fix a bug where a scheduled execution that found no objects on which to create decisions, remained stuck in "processing" status
- You can now pass the "allowssl" parameter for the DB connection (through the
PG_SSL_MODEenv variable). The default value if not passed is now set toprefered(though we recommendrequirein production). - Finally, you can also configure the DB connection by using the
PG_CONNECTION_STRINGenv variable (instead of passingPG_USER,PG_PASSWORDetc separately). This can be useful as it gives you more granular control on the options passed.