IFS Cloud No of lower environment on remote installation

You mean any limitation to build as many test environments on-prem as necessary?

I don’t think there’s a technical limitation. I haven’t run into any doing fresh remote deployments anyhow.

Whether the license or an agreement with IFS limits this on the other hand is a customer-specific thing.

Thanks for your reply 

my question is related to license limit

regards

Pankaj 

That should be in the contract for each customer.

We are remote / on-premises install. I’m not aware of any limit on the number of non-PROD environments but it would be worth checking your license agreement as Sami mentioned.

FYI, we currently have 4: DEV, TEST, TRAIN, and MIGR. Our DBAs at Re-Quest enabled an automated nightly refresh from PROD to TRAIN. This is super helpful for testing and troubleshooting. If I were doing it again, I would probably add one more called “CLONE”, “QA”, or whatever IFS suggests, and use that for the nightly refresh instead of TRAIN, since training can require data staging which can’t be done in PROD.

​@CRUNDELL , is there any documentation on database automated refresh please?

Yes, here is one of the scripts that we use when refreshing DBs.

Please see the “IFS Cloud Clone” article for a list of “Refresh Exclusion Tables”.

FYI, we also designate users to receive privileged access in non-prods. We have one user group for each environment. The script then gives them full access to that environment via a permission set designed for that purpose.