The tech behind the Amplify schedule has received a huge upgrade this month. The upgrade resolves many of the quirks and bugs that have appeared over time.
While not immediately apparent, the upgrade also brings a lot of performance boosting features behind the scenes. The new calculation engine in particular pledges to considerably boost the performance of the schedule as well as support much larger datasets without compromising.
We, at Amplify, have also been working on making sweeping performance updates to the Amplify software. We've put considerable resources into optimising database performance which means we can offer much quicker resolutions for complex queries and large datasets.
Some of our performance updates have also given a boost to the rendering performance of certain pages. Some reported instance have been reduced from minutes to seconds!
|Service Request #/ Internal Ticket ID||Description|
|SR # - 1035||Cyclic dependencies would cause the schedule to become unusable|
|SR # - 1272||Critical paths would not display correctly if linked to certain dependencies|
|SR # - 1305||The schedule would not render correctly at some zoom levels|
|SR # - 1315||Obscured some license information|
|SR # - 1322||Adding a new team would require a refresh to access them|
|SR # - 1324||Some schedule tools would be obscured at certain resolutions|
|SR # - 1326||Quickly created RAID items would not default to the current project|
|SR # - 1348||Some task dependencies would display incorrectly on the schedule|
|SR # - 1359||License override comments would not send correctly|
|SR # - 1386||Reporting year would not save in some Goals|
|SR # - 1391||Measures would not display on the dashboard under specific conditions|
|SR # - 1415||Certain schedules would become unresponsive|
Please sign in to leave a comment.