x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 89 subscribers
  • Views 541 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
btmlinesoft

PR 2.24 Release

SOLVED
Posted By

Trying to get my head wrapped around the release.  You publish 2.24 last week and then just a day or two later you release a hot fix?  Did you know about the hot fix pending when you released the update or did you scramble at an unheard of lightning speed when the issue was reported??  Since you are NOT known for hot footing hot fixes, I have to believe you knew the hot fix was coming down the pike and didn't bother to warn us when releasing the update!  SHAME on you for wasting our time trying to get ahead of the YE installs! How GRINCHY of you.

  • 0
    SUGGESTED

    Hi  ,

    Thank you for your feedback. I understand your concerns about the recent update and the quick release of the hot fix. We strive for transparency and efficiency, and I want to ensure you have the full context. The initial payroll release was announced on December 15th. Following this, we identified an issue that required immediate attention, leading to the hot fix released shortly after. This was not anticipated at the time of the initial release. Our team worked diligently to resolve the issue as swiftly as possible. I apologize for any inconvenience this may have caused, and we appreciate your patience as we continue to improve our processes. I will keep you informed with any further updates.

    Warm Regards,
    Erzsi

  • 0 in reply to Erzsi_I

    Thanks for the response.   Perhaps the next time this happens (there will be a next time), how about pulling the release immediately and posting a reason why it was pulled?  A lot of people were caught unaware and proceeded to update their clients.   A LITTLE communication means a LOT to us!

  • 0

    As of today, December 27, 2023, I noticed that the PR2240T hotfix isn't linked from the main PR 2.24.0 download page. It might be helpful for users to have a clear indication on the main download page that a patch is available and should be applied. This could prevent confusion and ensure everyone uses the most updated and stable version. Just a suggestion to consider for improving the user experience!

  • 0

    Wayne is correct and I am confused because the download page for 2.24.0 shows: Created on 12-14-2023 / Last modified on 12-19-2023

    There is no link to a hotfix located there, that leads one to believe the download was modified to include the fix. 

  • 0 in reply to Wayne Schulz

    Thank you  for bringing this to my attention. This was 100% a miss on my part to not update the download of PR 2.24.0. I am working on getting it updated right now.

  • +1
    verified answer

    Jeff, Sage engineering did not know about the issue when PR2024 was released. Had we known about the issue, the release of PR 2024 would have been delayed. The issue was reported by a partner. The issue is specific to terminated employees and the number of years of check history to be retained. 

    John Nichols

    Sage

*Community Hub is the new name for Sage City