Welcome to the 25.2 release!
At Agillic, we are happy to present new product improvements that will aid your use of the platform, and enable you to be more efficient with the Agillic platform.
This is what we're bringing to the platform in 25.2.
Exports
Print steps: Multiple export files generated from export sted can now be zipped
Starting from version 25.2, you can configure to zip print files generated during the export step, the files will be split into multiple ZIP archives and it will affect only export profiles to folder. This configuration ensures that even with millions of recipients, you can easily open and manage the exported files. The behaviour can be controlled in Settings, Print section.
Activity export: Change the logic when to stop activity export in case of a bad configuration
We are changing how we handle badly configured activity exports. Starting now, exports will be stopped after 7 consecutive failures, rather than after 7 consecutive days of failure.
Report export: filter bot clicks during export
Bot clicks: report export now also support filtering bot clicks out
Integrations
Recipient API: add combined API request
A new API request allows you to update person data, one-to-many data, and achieve an event — all in a single request for improved efficiency.
Public API: RSQL filter for empty values
The API for retrieving recipients by filter now supports empty values in RSQL filters, allowing for more flexible and precise queries.
Target group service: Get target group population through API call
You are able to get the latest Target Group population count via a new API endpoint.
Reports
Add Report Dashboard Date Range
You can now set a date range for the entire dashboard, overriding the date settings of individual reports.
Extensions
Make extension editor available in UI
You can now create and update your extensions directly through the user interface, making management faster and easier.
Data
Stop Evaluation of unreferenced TG
Starting from version 25.2, the platform will automatically detect target groups that haven't been used for a while. To improve stability, we will stop counting the size of these inactive target groups.
Security
Spring boot 3.4 upgrade
We've implemented several improvements to our platform to make it safer and more stable.