PlanGuru App Update 1.9.6.3

This release includes server-side performance improvements, UI enhancements, and several bug fixes designed to improve reliability and speed — especially for larger, more complex scenarios.

Annual Roll Forward: Scenario Loading Optimization

We've streamlined how PlanGuru loads scenarios following an Annual Roll Forward. Previously, post-roll-forward scenarios used a separate code path to handle their additional data requirements. That logic has now been merged into the standard scenario loading process.

Miscellaneous UI updates have been applied to support the Annual Roll Forward server-side improvements described above. These changes are behind the scenes and require no action from users.

Impact: Users should notice faster, more consistent scenario loading after performing an Annual Roll Forward.

Overall Performance Improvements (Large Scenarios)

We've made targeted improvements to browser-side performance, particularly for large scenarios with high memory usage.

What changed:

• Certain heavy click events were triggering unnecessary processing. This has been corrected.
• Net Income recalculations are now limited to the specific scenarios where they are required, rather than firing broadly on user interactions.

Impact: Users working in larger, more complex scenarios should experience noticeably smoother performance.

Fix: Non-Financial / Assumption Account Saves

Resolved a bug where changes to non-financial or assumption accounts were not saving correctly. In some cases, the system lost context — specifically the company, project, or scenario — causing saves to fail silently.

Impact: Account updates will now save consistently and reliably.

Excel Import: Subclass Validation Update

Fixed an issue where Excel imports could fail if an account subclass was null or blank. The import process now requires users to select a subclass for all account mappings before the import can proceed.

What to expect:

• If any account mapping has a null or blank subclass, you will be prompted to select one before the import completes.
• This validation step ensures successful imports and prevents data errors downstream.

Impact: Excel imports will be more reliable, with clearer feedback when data is incomplete.