Last Updated: December 11, 2024

Bug Fixes

1. Manage Salary Budget
   • When adding worksheet items the “Hours / FTE” column would always default to 1950 until it was saved.  This has been corrected to default to the most common group role detail hours per FTE for the given salary budget version.
2. Process Scheduler
   1. Build Budget – Command Dialog has been fixed as it wasn’t properly showing saved parameters when re-opened.
3. Process Worksheet (Procedure)
   • Fixed a strange bug that was happening on one client running full process worksheets which would prevent the procedure from completing.  It involved how dates were being calculated
4. GL Budget
   • Fixed an issue on the Account Summary grid where it was grouping by the account ID.  This was incorrect as the account ID includes more lookup columns than are shown causing more records to be visible then it should be.  Once it was removed, it groups properly and shows a proper summary.
   • Fixed an issue with saving data when a user opens the notes and attachments dialog (GL Budget documents) on the Manage GL Budget page, adds a new row but doesn’t fully save it and then closes the dialog, in some cases the pending change is retained, and any subsequent database change (even on unrelated grids) were showing an errors such as “bdoc_description cannot be null”.
5. User Cross Tab
   • Fixed an issue on the layout tab when filtering on fields by typing in keywords above them.  Depending on how fast users were typing in a keyword to search for it would sometimes cause issues as the event was firing on every key pressed and not when the user paused or was finished.  I added a delay to the event so that it wouldn’t fire too often and cause pauses or glitches in the user crosstab screen.
6. Cube Drill Down
   • Fixed an issue where the staging table that was calculating the drill down records were never getting cleaned up.  This wasn’t causing a visible problem but in some cases can slow things down if the staging table gets very large.  Now the cleanup is done by the nightly job that happens on the server.

Enhancements

1. Reporting Groups
   • There is now a new system parameter that can enable alternative group codes.  Once enabled, the “import code” column on the reporting group tree details can now be used to specify the parts of this group code.  Ex: Instead of 0002.0003.0004.0071, a custom group code may say Assets.ShortTerm.12345 where the Assets was a root node, ShortTerm was the middle node, and 12345 is the cost center code.
   • Added the ability to see which cubes are referencing the trees.  To see this new feature, simply use the checkbox at the top of the tree master grid and it will enable the “calculated fields” which includes the new Cube Ref. Count field.  Double clicking on this field will show a popup which lists the cubes that reference the selected tree.
2. User Cross Tab
   • Added the ability to see column filters assigned to the grid itself (not related to the database filter control under the pivot grid).  You can now also right click on a pivot grid field and select “clear all column filters”.
3. Landing Page
   • Changed the two Variance pages so that you can now specify the first tree by Employee Class.  Originally you could only specify Cost Centre first or Earning Benefit first…now you can also do Employee Class first.
4. Manage Data Retention
   • Added features to this screen to be able to better filter on things like attachments by related table versions.  Ex: If you wanted to purge the attachments for an entire version related to the line items table, then you can now do that.
5. Performance Improvements
   • The process for creating the materialized tables for the GL Actual and Budget summary as well as the Payroll Actual and Budget summary have been changed to include all of the previous year amounts, YTD, etc.  As a result, the refresh will take a bit longer but the views that rely on these materialized tables (user cross tab, reports, etc.) will be faster especially on older SQL Server versions (such as 2017 where I saw 2X performance improvements in some cases for long running queries).
6. Capital Forms Activity
   • This is a new page which functions very similar to the Budget Activity page (from a high level).  This page will allow for approving and rejecting capital forms and will handle locking down forms after they have gone through the approval process…for example: a manger that approves a form cannot edit that form unless it is rejected (and sent back to the manager).
7. Code Tables
   • Positions
     • Created a new lookup table called positions.  It has been added to the payroll actual and payroll budget tables.
   • Salary Grid Types
     • Added a new tab that shows the salary grid step range.  Shows things like: lowest and highest step for a given grid type and effective date.
8. Cube Management
   • The tree lookup detail have been converted to views so that additional columns would be available to be filtered on.  For example, it’s now possible to filter on the cost center alias on the cost center detail tree table.
9. Salary Functions
   • udf_get_db_earning_hrs – New user function for use in the salary earning/benefits
10. Report Writer
    • New User Functions
      • GetValueTranslation
        • GetValueTranslation(translation_type_code, source_value) returns target_value
        • Ex: GetValueTranslation(‘PRODTYPES’, ‘38010’) Returns ‘P’
        • Note: This uses types, source values, and target values from the Manage Translations page within ESM.net
      • GetFiscalYearGLPeriodAdd
        • GetFiscalYearGLPeriodAdd(fiscal_year_gl_period, num_periods)
        • Adds (or subtracts) from a fiscal year GL period.
        • Ex: GetFiscalYearGLPeriodAdd(‘2024GL12’, 2) returns ‘2025GL02’ as string
        • Ex: GetFiscalYearGLPeriodAdd(‘2024GL02’, -3) returns ‘2023GL11’ as string
      • GetPOAAdd
        • GetPOAAdd(poa, num_add_poa)
        • Takes a starting POA and a number to add to the POA to get the next POA.
        • Ex: GetPOAAdd(‘201505’, 6) returns ‘201511’ as string
        • Ex: GetPOAAdd(‘201512’, 3) returns ‘201603’ as string
      • GetPOAToFiscalYearPeriod
        • GetPOAToFiscalYearPeriod(poa, fiscal_year_start_month)
        • Note: Fiscal Year Start Month can be a 4 (april) or 1 (january)
        • Ex: GetPOAToFiscalYearPeriod(‘202403’, 4) returns ‘2023GL12’ as string
        • Ex: GetPOAToFiscalYearPeriod(‘202403’, 1) returns ‘2024GL03’ as string