Release notes 3.24Release Content Summary The following table provides a list of the customer facing/relevant changes in this release. Not all platform backend changes are included in this list. Domain Type Notes Backend Enhancement Implemented the concept of pagination on the CDS subset list page Backend Enhancement “Top level” includes can also be enforced through types. A new field is added to types to indicate if the node should only accept type level includes. Backend Enhancement When running custom validations on pending data (forIncoming=true), the validation will run on pending data only for the main config data set (mds). If additional config data sets are defined in the mdsArgs parameter, the validation rule will take the latest snapshot of these additional config data sets Backend Bug Implemented a fix to export a config data set with a tag. UI Enhancement “Zoom Out” button is added below “Zoom In” button in the menu to make the option easily accessible. UI Enhancement When including nodes through an API call using the “processChildren” flag, the included node is displayed with its full path. The same has been implemented when including nodes through the UI. UI Enhancement A new filter called “User” is added to the Data Changesets page. This filter helps to see all changes made by a specific person. Details – Pagination on the CDS subset list page In this release, we are adding server-side capability to display a paginated subset of the full list of CDS in the Sweagle UI. Why? Tenants with a large number of CDS experience a delay in the loading of the page which currently uses client-side pagination. The reason for the delay is that all available CDS with all their metadata are loaded client-side upon accessing the CDS page in the Sweagle UI. Once loaded, client-side processing is applied. The current page offers filtering, sorting, and searching across the full list of CDS which provides a convenient user experience. Collecting the full list of CDS with all its metadata (pending, stored, validation status, etc.) does become time consuming and requires sufficient client-side resources once the list grows to hundreds or more. With this enhancement request the list of CDS to be handled by the browser will be limited to speed up the initial loading of the page. Tenant setting This capability (server-side filtering and pagination) will be controlled through a tenant preference setting. Only users with admin permissions can change this setting. The setting is tenant wide for all users in the system. The admin user needs to add the tenant preference below and set it true to enable the pagination on the CDS subset list page. cds_list.core_pagination.enabled NOTE: The server-side filtering and pagination will be disabled by default. It is expected that most customers will prefer the current “full list” loading. Page behavior The new page will be as follows: A default subset of the list of CDS will be loaded when a user accesses the CDS list page. The default returned subset will be a limited number of CDS.The user will be able to initiate a new search to retrieve another subset list. The user can enter a partial CDS name, and upon clicking the search button the service-side search function will return the list of corresponding CDS as a subset to the client.Using this new page, the stored status and pending status information will not be directly visible on the main list page. Status information will be visible when the user selects a CDS and access the details.The subset list will be paginated using the default pagination control with a configurable number of items to display on a single page. Details – “Top level” includes can also be enforced through types A new field is added to types to indicate if the node should only accept type level includes. Details – “Zoom Out” button in the menu The “Zoom Out” is added below “Zoom In” option to make the button easily accessible. Details – “User” filter in Data Changesets page Sweagle 3.24 version allows to filter the changesets list on filter “Name”.