Additional Productlines

I need to provide supporting documentation for requesting an additional productline. We currently have one on a development server and one on a second development server. I want to add a second productline to one of the development servers. Here are my reasons:
Allows data to be frozen at a point in time in one productline without affecting developers and users trying to test with current or more recent data. For example: W2’s, Benefits enrollment, New facility implementation, Development, Running a payroll to parallel a production run.

Can anyone think of additional pros for adding a second productline to a server?

IDF Level 1 Overview Companion Video to XA Roadmap 04232020.mp4

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

jreese

We currently have 2 Development product lines on a development server, which we use to test out new products, and functionality without affecting end user testing. This could include upgrading versions. Most end users do not have access to this environment. We also have 3 test product lines in a test environment which usually mirrors production. During ESP/MSP testing we usually reserve one just for PR to do parallel testing which cannot have other updates entered and allow the other areas to do their testing in another product line that has all the plugins that are product line specific attached to it. The third productline stays at the same release as production in case of a critical issue that needs testing.

unknown

We have 5 prodlines on LSF and 4 on Landmark. On LSF-DEV we have prodlines DEV, TEST, TRAIN, and PRIST; On LSF-PROD we have prodline PROD:
- DEV is used for development and Unit/System testing
- TEST is used for User Acceptance testing and business testing
- TRAIN is used for user training (and we have some "fake" users/employees set up for EMSS training)
- PRIST is used for configuration testing and/or for testing objects that should mirror PROD. We also use this at year-end to store a 12/31 dataset for a period of time for payroll testing.

Our LSF promotion path is DEV >> TEST/TRAIN/PRIST >> PROD

On LMRK, we have a similar structure, though with fewer prodlines. LMRK-DEV has prodlines DEV (prodhcm) and TRAIN (trnhcm), and LMRK-PROD has prodline PROD (prodhcm).

Our LMRK promotion path (IPA Flows) is DEV>>TRAIN>>PROD.

As we implement LSF-10 and LMRK-10, we plan to move to three LSF and three Landmark environments and move around the prodlines, but we won't have any fewer of them.

I hope this helps!

Kelly

sarb-nahal

Thank you both for your input! It helps a great deal.

unknown

We have users in 4 main functional areas, so we have a product line for each one of them. That way, if finance needs a data refresh and HR is in the middle of testing new benefit stuff, they don't step on each other. These 4 product lines are in the same (DEV) environment, and we have another non-prod envrionment with one product line, where upgrades are tested for instance. When we are not in upgrade mode, this product line is used for testing CTPs before they go into production.

Copyright © 2025 Infor. All rights reserved.