Skip to main content

Naverisk 2025 R4.1

Release notes

Updated this week

Welcome to the Naverisk 2025 R4.1!

With this latest update, we've enhanced the functionality of scheduled jobs, allowing for more precise control over post-action triggers.

You can now specify an exact delay for post-actions to begin, ensuring they are executed at a predictable time, even if other tasks in the job are still in progress. In addition, this release includes several performance, stability, and quality improvements.

Device Grid, disk space, memory and processor version

The device grid now provides richer, more immediate hardware insight. We've added columns to show total disk space, total memory, and the processor version for each device, making device management and diagnostics faster.

Scheduled jobs, post actions

We've updated how post-actions of scheduled jobs are triggered, giving you more control over your workflows. The “Wait for” field now determines when these post-actions begin after a job is initiated.

  • Wait for = 0 (Default): Post-actions will start immediately after the action is completed. This ensures a seamless, direct transition.

  • Wait for > 0 (Time Value): Post-actions will be delayed by the specified time, even if other actions in the job are still in progress. This allows you to set a precise delay for post-actions to begin, providing greater flexibility in managing complex jobs. It also guarantees post actions are executed at the same predictable time.

This update provides more precise control over the timing of your scheduled tasks.

Other performance, stability & quality improvements

  • Fixed: issue where changes to Naverisk project’s attributes changes were not saved correctly in the database.

  • Fixed: issue where the survey field in ticket search modal was not displayed correctly.

  • Fixed: issue where email integration tickets appeared in the wrong queue. They will now be logged in the Naverisk Tickets queue in the Settings page.

  • Fixed: issue where scheduled jobs configured to use device filters failed to execute. These jobs now run correctly at their scheduled times.

Did this answer your question?