Developer Studio, deployment, and upgrades FAQ
Browse questions about Developer Studio, build and deployment work, and release changes. Identify the product generation and environment first: an older IFS Applications technique may not apply to a current IFS Cloud installation.
Related learning:
- Follow the development and modifications guides
- Plan and validate upgrade scripts
- Read the authored and generated file map
- Prepare a release handover
Release note: These answers include IFS Cloud and older IFS Applications topics. Confirm the product and release mentioned in each answer. They are written explanations, not procedures verified in an IFS environment.
Explore other FAQ topics (23)
916 questions · page 1 of 23
Should we remove obsolete customization files after an upgrade, or leave them?
Do user roles and permissions carry over unchanged when moving from an older UI to Aurena?
What tooling exists for developing against IFS Cloud outside the browser (an IDE extension, for example)?
How should we plan an upgrade that spans several releases at once (skipping versions)?
A security advisory (CVE) was published for a component IFS uses — how do we know if we're affected?
How do we make a PL/SQL package we wrote available as a projection custom action?
A custom override in our Cust layer collides with a Core method signature after an upgrade.
How do we install or enable an additional language for the application?
Where should environment-specific configuration (connection details, environment definitions) live in source control?
A page throws an "invalid identifier" error only when opened from a specific lobby or shortcut, not when opened directly — why would the path matter?
Is there supported tooling to connect Developer Studio to an external issue tracker, like Jira?
Before an OS-level server upgrade (like a Windows Server version bump), how do we confirm the rest of our stack is still supported?
A Kubernetes-based installation or upgrade fails with a "resource mapping not found" or similar missing-custom-resource-definition error.
After an upgrade, the build place (DEV) shows a different framework version than the application version, and that looks inconsistent.
An installer fails partway through with an obscure error related to a temporary directory or file copy step.
Is there a built-in way to identify all the projection action permissions that will be affected before an upgrade, instead of finding them one by one during user testing?
Can the default wildcard filter in a bulk "add parts" style dialog be removed so it doesn't include everything by default?
How do we find out exactly when standard support for our current release ends?
Shop orders that were in a "Parked" state before a migration from an older application generation behave differently in Cloud than expected.
A toggle or button on an assistant/dialogue page can't be found or hidden in Page Designer, even though the same kind of control is configurable on other pages.
Existing page configurations show a Baseline Status of "Behind" after applying a release update — how is that resolved?
Where do we find the installation instructions for an air-gapped (fully offline) Cloud deployment?
How do we confirm the latest available update for an older application generation (like Apps 10) before a maintenance window?
Is a full administrative permission set the only way to grant access to Page Designer, or is there a narrower option?
If we install a release at a specific Service Update (SU) level, does it include the fixes from all the SUs before it, or could an intermediate one be skipped?
For an on-prem-to-on-prem upgrade, can the database upgrade step run in a customer-hosted interim environment instead of one hosted by IFS?
Can we upgrade directly from a much older application generation (like Apps 9) straight to a current Cloud release?
A Kubernetes pod (like the OData service) stays in "Pending" state and never starts.
A manually joined High Availability cluster node behaves unexpectedly, or nodes crash during setup.
The "Enable log window" option is missing from the debug menu on a newer release.
Can "Recreate Build Home" be used to condense an existing deployment's accumulated Service Updates into a single upgrade, the way a fresh build home works?
What actually happens if the replica-count setting is left unspecified during a Kubernetes-based installation?
How should we read a release/update version number, and how do Early Availability (EA) and General Availability (GA) relate to each other?
Is there a documented approach for installing IFS Cloud when the server sits behind a corporate proxy?
Can a newer Service Update be applied partway through an already-in-progress release update, if a critical fix becomes available mid-process?
Do previously-uploaded LTU (limited-use) permission sets need to be re-uploaded when applying a Service Update?
Is there an official limit on how many release versions behind a customer can be and still receive standard support?
Is there an official recommended cadence for how often to apply release updates after go-live?
A self-hosted BI/reporting connection (like an SSIS or Power BI data source) fails to connect with a generic database timeout error.
No questions match. Try a broader term or reset the filters.