Pre-Prod Tenant experiences

I'm interested in hearing from anyone who has a pre-Prod tenant that (by my calculations at least) should have already gotten the October CU release for FSM & HCM.

The pre-Prod tenant seems like it would be especially useful (in October & April) given Infor's new semi-annual / two big releases per year model.

I'm trying to build a case internally that we should at least budget for this in 2024.

For those who have it, have you found it useful? How much regression testing do you find yourself actually doing? Would you recommend it to others?

Find more posts tagged with

Comments

Amy Coats

I'm interested to learn more about other users experiences also

Noe Ramos

following

Heidi Anderson

St. Luke's Health System has a pre-Prod tenant, and we use it quite a bit especially for the major releases in April and October. This allows our teams across HR, Finance, Payroll, and Supply Chain to test critical changes before they hit our live system. Probably every release we have found a few major issues to work through - some have required Infor support to resolve. Yes, I would recommend anyone w/MT have pre-Prod.

Heidi Anderson

@joseph-vandenburg - replying here as others may have a similar question. I'm not sure what exact applications are available or not in a pre-Prod tenant, but I believe ERM and UAP are not available.

cleverly

Thanks for the response! A few additional questions, if you don't mind...

With the few major issues that have required Infor support's assistance, has two weeks usually been enough to get to resolution (or at least a plan/workaround) ahead of the actual CU release? Is it safe to assume support has been extra responsive in these cases?

How often do you have Cloud Ops refresh data from PRD to whatever your pre-prod tenant is called? (I want to call it TST, but all MT customers get a TST tenant already, so there must be some other name for it.). I'm guessing that once the CU has been applied to pre-prod the database schemas wouldn't be compatible for a refresh until after the actual CU release, so if testing with relatively current data were a requirement, that'd be something we'd need to plan on requesting/managing to stay on top of...

I appreciate your feedback--it'll help me build my case to get this included in next year's budget. :-)

maureen-shea

We use Pre-Prod at Yale New Haven Health. I request a data refresh every month (usually the Sunday following the Pre-Prod (PP1) install. Like Heidi, we rely on it quite a bit. Most issues are resolved (or there is a workaround) before we go live. Hope that helps.

Hans Mueller

Most PreProd tenants are PP1 vs TST or TRN.

PreProd updates are initially delivered almost 5 weeks early. A second update window is available if needed rougly 2 1/2 weeks later.

Heidi Anderson

Our tenants are: DEV --> TST --> PRD (promotion path), TRN (training), and PP2 (pre-Prod)

Heidi Anderson

Passing add'l info back from my team:

- In terms of our experience with our Pre-Prod environment, we would be lost without it. We regularly find serious issues with the CUs in pre-prod that we would otherwise find in production. Many of these issues are major and a few have been critical. As noted, the window to address issues we find in Pre-prod is relatively small (approx. 2-weeks), we’ve found that Infor is pretty responsive to tickets we submit during that time – especially anything serious.

- As far as the refresh from Production to Pre-production – we always try to refresh Pre-production a couple of days after the CU has been applied to production. Additionally, Pre-Production is probably our most refreshed tenant which is usually tied to triaging fixes and workarounds coming in the next CU since Pre-Production would contain the next month’s CU after Infor has applied the monthly CU to production. We have found Pre-Production to be invaluable in testing and validation for the next coming CU.

Noe Ramos

I'm curious with the refresh monthly - i do like that idea but in terms of backup - how do you back up your items that you're still testing etc? i'm thinking about IPAs or settings that are only able to be backed up via ISD manually. Do you have a list of things your organization backs up before the refresh so testing data still in test is not lost?

Prakash Shrestha

We use Pre Prod (PP1) for all our updates testing and whenever we need to test issue resolutions as suggested by Infor before trying them in Production. It has been super useful.

cleverly

I just started a separate discussion about how the October CU gave supervisors broad access to all Employee and WorkAssignment related ActionRequests.

Those of you who had Pre-Prod, did this come up in your testing? What (if anything) did you decide to do about it? For our organization, we're trying to evaluate whether we take on the burden of forking a copy of the _ST security classes, reverting this change (or figuring out how to tighten it up), so I'd love to hear from people who are a couple weeks further down the path than we are!

Mychele Lee

Prior to moving custom LPL to PRD, we test it in PP1 to ensure it works on the future CU as well

Copyright © 2025 Infor. All rights reserved.