No More Enhancements for ST/OP Customers

We just found out Infor will no longer be releasing enhancements to their single-tenant and on-premise customers.

Are other ST/OP customers aware of this? Was this communicated officially or just done without any notice?

We find this to be a completely unacceptable business practice and are interested in speaking to others with similar concerns. Looking forward to hearing from the community on this one.

Find more posts tagged with

Comments

unknown

Was not aware of this, thanks for bringing this to my attention, will verify and get back to this forum. We are a single tenant in the cloud. How did you find out about this?

unknown

We are as well. We asked our CSM about the lack of release notes for 2023.03 (7 items) thinking it was a mistake. They came back with this:

“Yes, there are only 7 tickets. 11.23.03.00 is the first release after splitting MT and ST/OP. Only regulatory items and P1/P2 issues that directly relate to ST/OP customers are being put into ST/OP.”

Hans Mueller

This is Hans Mueller from the Product Management Operations team, and this is posting is not correct. Can I ask in what context this was conveyed to you, so that we can please follow up and correct any confusion and misinformation that might be being spread in the ecosystem.

Since you posted in the FSM and HR Talent community, I assume you are referring to those products in a ST/OP deployment, but please clarify if you are also (or instead) referring to Lawson 10 products in ST/OP. In either case the title of this post is not correct, but the response is a bit different in either case so would like to understand before I add more clarity.

unknown

Hi Hans,

That is correct - we are an Infor HR Talent ST deployment and that is what I am referring too. The context is what I replied to Donnell with:

Us: We asked our CSM about the lack of release notes for GHR 2023.03 (7 items) thinking it was a mistake. :

CSM per Development: “Yes, there are only 7 tickets. 11.23.03.00 is the first release after splitting MT and ST/OP. Only regulatory items and P1/P2 issues that directly relate to ST/OP customers are being put into ST/OP"

Upon clarification that this meant no enhancements for ST/OP, they confirmed only "regulatory enhancements" would be included going forward.

Hans Mueller

Thanks for the background. I am conferring with the product management team to ensure we present a clear answer for you and the rest of the ecosystem. Hope to get you a more detailed response tomorrow.

jwienecke

Hi Hans, any feedback yet?

The product announcement (noted below) is a bit misleading as it states in the benefits that going from 4 ST releases to 2 releases will allow ST customers more time to adopt new features. However, at the end of the notification it says bug fixes, security and regulatory changes.

The 7 items in the release notes include 5 issues from Feb 11.23.02, 1 issue from Mar 11.23.03, and 1 enhancement from Mar 11.23.03 which is really not an enhancement but a dependency on a landmark version. Our users are upset as they saw the 2023.03 release notes and it includes reporting changes that they were expecting. I need to get back to the users with a clear answer, so your response is greatly appreciated!

Description

Beginning March 2023, Infor will transition to a semi-annual release cadence for all single tenant (ST) and on-premises (OP) deployed customers running the above products. The new release targets will be March and September each calendar year, allowing more time to coordinate environment installations.

Key benefits

Less frequent, consolidated changes to allow your organization more time to review and prepare for our releases
More flexibility and time to plan, test and adopt new features
Provide the highest possible quality across the entire solution

Additional important information

Please note the products on these platforms (ST & OP) will continue to evolve separately from the multi-tenant versions. This means ST and OP products will have different content and capabilities compared to what is deployed in the multi-tenant (MT) cloud. This is being done to provide the highest possible product quality and to meet the unique requirements for each specific product audience. Both versions are fully supported under Mainstream Maintenance.

Going forward, the ST and OP versions of these products will use the versioning notation below to differentiate them from MT product versions.

11.YY.MM.xx (YY = year, MM = month, xx = patchset)

Example: Infor Financials & Supply Management 11.23.03.00

Critical product bug fixes will continue to be provided as necessary including security updates, and date-sensitive localized statutory and regulatory compliance updates.

Please review Knowledge Base (KB) article 1973371 for exact versions and release availability and subscribe to the KB article to receive update notifications.

If you have any questions about this communication, please reach out to your Infor account team. Thank you for being an Infor customer.

Hans Mueller

Hi all -

Good morning, and I apologize again for the delay. Here is the official response on behalf of Infor on this discussion:

We appreciate your posts and questions and want to address any outstanding concerns. Single-tenant (ST) and on-premises (OP) customers are very, very important to us and customer success is our mission. As noted in previous support announcements, we are separating the code base for some Infor products on single tenant and on-premises environments from their multi-tenant versions. We feel that separate code bases are the best approach to address unique deployments and needs in respective environments.

We have investigated the current release and noticed that it is short on enhancements and regret if this caused any unnecessary concern about these environments. Our goal is to always provide meaningful enhancements to our ST/OP and MT users in each release. We have put new processes in place to address the circumstances giving rise to these concerns.

Please feel free to reach out to me at (hans.mueller@infor.com) with any other questions or concerns.

unknown

Hi Hans,

This response seems rather vague and open ended. Can you please elaborate on the "new processes in place to address the circumstances giving rise to these concerns"? Are ST/OP customers going to receive the same enhancements as MT, if applicable, in the separate code base going forward?

If not, ST/OP are effectively subsidizing the R&D for your MT customers. A large part of the money we as ST/OP customers pay for your software is based on the ever improving and enhanced system features.That is the product we were sold. If we aren't receiving these benefits, these products should be heavily discounted as they have effectively reached the point of sustaining maintenance.

I know Infor's goal is also to eventually get ST/OP customers all to move to MT. Isn't it counterintuitive to further diverge the products? In the end, that just makes a ST/OP to MT conversion significantly more difficult, risky, and costly.

unknown

Hi Hans,

I wanted to follow up on this topic. Please see me previous post which I've pasted below for convenience:

"This response seems rather vague and open ended. Can you please elaborate on the "new processes in place to address the circumstances giving rise to these concerns"? Are ST/OP customers going to receive the same enhancements as MT, if applicable, in the separate code base going forward?

Hans Mueller

Hi all -

Good afternoon! I understand your additional questions and concerns, but the details you are seeking will need to be discussed outside of this community setting. I would strongly encourage you, and any customer with similar concerns, to raise these issues directly with your Infor account team so that your specific footprint and deployment can be reviewed in context to that discussion.

I will say that no, ST/OP customers will not be receiving the exact same enhancements as what is provided in our MT releases. There are technical reasons as to why that cannot be done, as there are technologies that are available as part of the MT offering within Amazon's cloud services that are just not feasible to leverage in ST and OP deployments.

At the same time, your original concerns are valid - there should not have been "no enhancements" provided in the March HRT release - and that has been addressed internally through additional review processes (led by product leadership) throughout the roadmap and development cycles leading up to each release.

I know this isn't answering all your questions, so again, I strongly encourage you to continue this dialogue through your account team.

Thanks,
Hans

Copyright © 2025 Infor. All rights reserved.