Last Updated: June 3, 2024

Bug Fixes

1. Score Card Viewer
   • Fixed the saving issue where adding attachments was causing other attachments to stop working (after closing and then reopening the attachments dialog for a new item).
2. Process Scheduler
   • Fixed an issue when changing command parameters for the update budget prepare dialog wasn’t setting the user field or the reason code lookups
3. Worksheet Items Allocations – Views
   • These views that are used by the user cross tab, reports, and view source data were not very efficient and have been sped up significantly.
4. Time Offset Issues
   • On sites that are using Azure where the SQL Server is often set to UTC (universal time coordinates) time zone and the application server is set to something completely different like EST (Eastern Standard Time) then it was causing problems for the process scheduler as the user was interacting with EST and the application server which was getting it’s time from the database was often starting jobs hours before it was supposed to.  This has been corrected by adding a time offset as a system parameter for database queries that rely on the database time.

Enhancements

1. User Logins – Microsoft Entra Application Partial Support
   • The 1.9.0.2 ESM.net server can now be configured to point to an application connector created using Microsoft Entra.  If a user is added to the Entra application and that same user is added to the ESM.net system via the User Maintenance screen, they should be able to log in by typing in the user/password on the main login screen.  The automatic login button will not work with Microsoft Entra yet…that will be added in a future release.
2. Landing Page
   • Added the annual variance on the landing page
3. Report Parser – Data Imports
   • For the report parser, we introduced the ability to repeat column values when parsing lines where repeating values were shown in the report as partially blank links where only the amounts were posted and not the related descriptions.
4. Project Budget
   • When users were clicking on reload data there was a procedure that ran just before the getting of the data and putting it in the grid…this was the recalculate amounts procedure.  This procedure under certain circumstances was very slow as SQL Server wasn’t always choosing the best solution for getting this data.  The procedure has been simplified and it now runs very quickly.
   • Changed the job cost lookup to be editable.
   • When adding projects when you specify a project and there is only one in the project job cost cross-reference, then it will default to that job cost (a smarter default).
   • Publish Project has been modified to post directly to ESM General Ledger budget.  It will only publish projects with approved amounts.  You have the choice of publishing a single project or leave it blank to publish all approved projects.  Also have the choice of publishing future years only (if you don’t have to modify current year budget for projects)
5. User Cross Tab
   • • Asset Depreciation Schedule
       • Added columns: transaction type and model
     • Asset Funding Amortization
       • Added columns: transaction type and model
6. Budgeting – Start of fiscal year  
   1. Modified from being at the entity level to the Cost Centre level.  Specify start month (typically 4 April or 1 January)  Calculations will utilize the configuration based on Cost Centre when it is available, otherwise use the default as specified in the NOTCODED Cost Centre entry, or not coded Entity as no other value is available. 
7. Salary Earnings – Transfer hours to GL
   1. If an earning is flagged as Include FTE Hours, Transfer hours will continue to be true (Will transfer as per previous configuration)
      1. There is a trigger that will set Transfer hours if you forgot to check it.
   2. You also have the option of tagging other records by setting Transfer Hours to true. 
8. Reason code – Salary module
   1. Distribution assignment of reason code has been changed to a post salary calculation event, so that shift code (that are combined into one line entries) can be distributed according to their portion of FTE assignment correctly.  This impacts both Earnings and benefits. (Indirect assignment)
   2. Line entries that are directly assigned to a reason code continue to flow with that reason code.
   3. Sites have option to disable post event at budget startup even if want to use it as it does have some impact on calculation speed.  Post event can be delayed to just prior to reporting or transfer to ESM tables.  All post events such as reason code and allocations are performed AFTER all regular salary calculations.
9. GL Account Utilities 
   1. The cleanup for GL Budget master has been adjusted to ensure we retain the reporting accounts for re-grouping based on the site’s configuration.  That will prevent the utility from removing reporting accounts that are created by the materialization process to speed up reporting.
10. Framework Changes
    • Added the “combined description” fields that were  previously calculated on most views for user cross tab, reports, etc. to be stored in the actual lookup tables.  This affected many of the views in the system as these columns no longer have to be resolved on the fly.  It also makes filtering or grouping by these fields faster.
    • Removed the materialized tables for the tree versions of the GL Actual/Budget views and the Payroll Actual/Budget views as the same data can now be handled more efficiently without storing these tree combinations.  This means that the reports will still function the same and the refresh materialized procedures that dealt with trees will be much faster (specially for the sites that had many trees).  For sites with a lot of tree combinations, this will also save a lot of database space.
    • Created additional persisted columns in tables like the worksheet items to improve query response time in a few situations where complex where clauses were causing slow queries.