ILAP Analytics – Release Notes v2.11.1.0

Modified on Thu, 28 May at 4:12 PM

Overview

This release introduces improvements across the ILAP Analytics API, Web UI, and Background Jobs. The updates focus on improved data handling, export capabilities, authentication support, and fixes to scheduling and user interface behavior.


Component Summary

  • Analytics API: Version 2.11.1.0
  • Analytics Background Jobs: Version 2.11.1.0
  • Analytics Web UI: Version 2.9.0.0

No infrastructure or Bicep template changes are required for this release.


Completed Work Items

7136 – Background Job Processing Indicator

Fixed an issue where the background job processing indicator did not disappear after reverting a live revision, improving UI accuracy and user feedback.

7290 – Correct Source Display for Archived Schedules

Resolved an issue where the proper source was not shown for report schedules marked as active after being restored from archive.

7458 – Optimize Timephasing Request Payloads

Improved performance by pruning unused data from timephasing request payloads.

7582 – Export of Planning Schedules

Added support for exporting planning schedules, improving data accessibility and reporting capabilities.

7583 – Revert for Non-Live Revisions

Introduced the ability to revert non-live revisions, providing greater flexibility in managing schedule versions.

7584 – Formatting of Dates and Numbers

Improved formatting of dates and numbers for better consistency and readability across the application.

7585 – Authentication: Support Service Tokens for GraphQL

Added support for service tokens in GraphQL authentication, enabling more secure and flexible integrations.

7617 – Fetch Planning Schedule for Previous Cutoff

Fixed an issue where fetching planning schedules for a previous cutoff could fail.

7716 – HotFix - Fix timephasing error for missing C field


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article