Question 1

What is IFS release management?

Accepted Answer

IFS release management is the controlled process used to assess, prepare, test, approve, deploy and close application changes. It can cover a one-off IFS Applications patch, a scheduled maintenance release, an IFS Cloud Service Update or a Feature Release. The process accounts for customer-specific configurations, customisations, integrations, reports, permissions, databases and supporting technology so production change is based on evidence rather than installation steps alone.

Question 2

What is the difference between an IFS patch, Service Update and Feature Release?

Accepted Answer

IFS Applications patches apply fixes to the relevant legacy application release and are managed through the tools and prerequisites for that estate. In IFS Cloud, a Service Update is a monthly cumulative set of high-severity or high-priority fixes for a Release Update. IFS describes Release Updates, also referred to as Feature Releases in customer material, as twice-yearly updates that include new functionality and cumulative fixes. Current terminology and policy should be checked for the customer's release.

Question 3

How often is IFS Cloud updated?

Accepted Answer

IFS currently states that IFS Cloud receives monthly Service Updates and new Feature or Release Updates every six months. That does not mean every customer should deploy a package to production without assessment. The timing available to a customer depends on its release, lifecycle policy, residency model, contract and readiness. Customisations, integrations, reports and business acceptance still need a controlled review and test process.

Question 4

Is IFS release management the same as upgrading to IFS Cloud?

Accepted Answer

No. Release management controls patches and updates within an existing IFS estate. A move from an older IFS Applications release to IFS Cloud is a wider upgrade or reimplementation programme that may involve data migration, process design, CRIM uplift, integrations, reporting, security, training and organisational change. Release management can support the technical governance around that programme, but routine patching is not a substitute for a full Cloud upgrade.

Question 5

Can Pro DBA deploy a single urgent IFS patch?

Accepted Answer

Yes, subject to access, supportability and a defined change scope. Even an urgent fix should be checked for prerequisites, dependencies, required backups, environment sequence, downtime, validation and rollback limits. If the patch package itself appears defective or incomplete, Pro DBA can help gather evidence and liaise with IFS technical resources rather than forcing an unsafe production deployment.

Question 6

How are CRIMs, customisations and integrations handled during an IFS update?

Accepted Answer

They are inventoried and assessed against the release information and technical change. Relevant code, configurations, interfaces, reports and permission sets are included in the test scope. Some items may need uplift or remediation before production. Pro DBA keeps those decisions visible, but responsibility for changing a specific customisation depends on source ownership, skills, access and the agreed service scope.

Question 7

What testing should be completed before an IFS release?

Accepted Answer

Testing normally combines installation checks, technical smoke tests, interface validation, queue and scheduled-task checks, report output, user access and regression of critical business processes. The customer should retain control of business acceptance unless another arrangement is explicitly agreed. The depth of testing should reflect the release content, customer-specific changes and operational risk rather than a fixed generic checklist.

Question 8

Can every IFS update be rolled back?

Accepted Answer

No. Rollback depends on how the package changes application code, configuration, database structures and live data. Backups or snapshots may support recovery, but restoring them can discard transactions created after the recovery point and may not be the safest response. Pro DBA assesses the actual release and defines recovery decision points, prerequisites and limits before change. A rollback label is not used as a guarantee that all consequences are reversible.

Question 9

How does Pro DBA liaise with IFS Support during a release?

Accepted Answer

Pro DBA can maintain the release record, collect versions, logs, installation results and reproducible evidence, and progress technical questions or package defects with IFS. This gives the customer a coherent view of the issue and reduces lost context between teams. IFS remains responsible for its product decisions and case handling; Pro DBA's role is to improve technical coordination and keep the customer's release plan controlled.

IFS Release Management for Safer Patches and Cloud Updates

When IFS Updates Are Becoming Harder to Deliver Safely

Turn IFS Updates Into a Repeatable, Evidence-Led Process

Certified standards. Built into how we work.

Use IFS Release Management at the Right Point in the Lifecycle

One-Off Patch or Urgent Fix

Ongoing IFS Applications Release Management

IFS Cloud Update Readiness

30 years of keeping critical systems running

Make Every IFS Release a Controlled Business Decision

Clear Go or No-Go Decisions

Controlled Production Deployment

Better Protection for Customer-Specific Changes

A Reusable Release Record

How Pro DBA Manages an IFS Release

Assess the Release and Estate

Build, Test and Resolve

Approve Deployment and Recovery Controls

Deploy, Validate and Close

IFS Patch, Cloud Update and Release Governance Coverage

IFS Applications Patch Management

IFS Cloud Lifecycle Activities

Testing and Validation

Governance and Coordination

Trusted by Organisations Running Critical Database and IFS Environments

IFS Release Management FAQs

Bring in the Right IFS Specialists

How can we help?

London office

Head office