Since new IAL objects can no longer be created from 2020 R1 onward, what happens to existing IAL objects already in use (e.g. for lobbies, quick reports) when upgrading from IFS 10 to IFS Cloud, and how do you handle one that breaks?

Answer

Existing IAL objects and their underlying views keep working unchanged after upgrading — lobbies, quick reports, and other consumers that already reference them continue to function, and this holds for most reports/integrations built on those IAL views too. The one thing that no longer works the old way is maintenance: if an existing IAL view gets invalidated by a change to the underlying database schema, it can no longer be fixed through the IAL Object Developer window the way it could pre-Cloud. Instead, you have to extract the IAL's definition into a new, equivalent view (created via a Developer Studio customization project) and then update whatever consumes the old IAL object (reports, quick reports, lobby elements, etc.) to point at the new view instead. IFS has said future Cloud releases will address IAL-style use cases with a different, more native mechanism, but that's a separate forward-looking change from this existing-IAL-object migration path.