v5.0.1656
NEW FEATURES
Connector Configuration Sets
A Configuration Scenario is an identifiable bundle of settings that can be used to pre-configure a NIM System. Multiple Configuration Scenarios can exist, each of which can be selected for pre-configuration of a system. After pre-configuration of a NIM System, the system's configuration can be tailored any further, after which the resulting configuration can be stored as a new Configuration Scenario, or as a replacement of an existing one. Configuration Scenarios are stored in the NIM Connector.
0
Compose Items
Ability compose items to be reused across apps. This provides the ability to standardize certain elements, rows, or forms so they can be same across multiple apps. Examples of this would be headers, footers, buttons.
0
Timeout Session Length control
Session timeout control for NIM login sessions. When people with various rights to perform admin rights we should be able to control the amount of time that session lives without requiring a re-authorization. How long is the current setting ? From a security perspective I want to be able to adjust custom rules based on access rights .. eg Admin sessions can only have xyz length , password reset rights etc .. Additionally in SAML authentication support for "notOnOrAfter" attribute
1
IMPROVEMENTS AND FIXES
- Service - When the server reconnects, socket.io communication is restored
- Service - Use secure session cookies when HTTP is disabled
- Service - Improved session security
- Service - Update dependent packages including node
- Service - Name Generation iterations limit configurable
- Service - Small possible memory leak fix while processing API
- Service - Improved authentication on socket.io communication.
- Service - When offloading audit is enabled, the service won't start
- UI - Dark mode for form construction tab displayed incorrectly
- UI - Log window scrolling not correct
- REST - Option to set extra headers on data retrieval per table
- REST - Add the excludedFields in the array selector configuration
- REST - Make it possible to override the selector configuration per endpoint
- REST - Support retrieving non JSON results without text/plain content-type
- REST - Respect maxCount on exponential retry configurations
- REST - Allow the Google connector to override the build-in retry configuration
- REST - Remove double query parameters on paged calls with link paging
- REST - Body will preserve the type with fields where a variable resolves as non-string
- REST - Filter out NULL values in data collection responses
- Systems - Dataset statistics show errors in overview
- Systems - No checking on duplicate (primary) key and reference values
- Role Model - Support for multiple member tables with Role Model scoping
- Configuration - When restoring a repo, only load the last successful data if the hash matches
- Logs - Loading large logs in the log overview failed with Maximum call stack size exceeded
- Templates - Cannot send test e-mail when configuring notification template e-mail
- Apps - sort and search in grid custom column
- Apps - incorrect processing of variable state
- Apps - Validation error 500 between forms
- LDAP - Connection reset errors are not logged anymore
Known Issues
- SAML - After being released, it was discovered users are able to login with SAML but can be immediately returned to the login screen
- Events - Email fails to send when tables are used in the template
Notes
- This version checks uniqueness on system table keys. If a key is not unique it will fail validation.