Skip to content

After IFS performs an environment clone (for an IFS-hosted Cloud environment), do Appearance Configuration settings (like environment-specific logos used to visually distinguish CFG/UAT/TST from PROD) get overwritten by the clone source's settings?

Answer

Yes — Appearance Configurations are copied as part of a clone (the underlying data lives in fnd_model_data_tab, cloned alongside page configurations generally), so any environment-specific appearance differences (like a distinct logo per environment) get overwritten with the source environment's settings every time a clone runs. A documented post-clone step — reapplying the target environment's own appearance configuration and swapping the Document Logotype back to that environment's distinguishing logo in every company — is the practical way to keep this environment-identifying setup intact across repeated clones, since there's no way to make it clone-immune on its own.

← Browse Developer Studio, deployment, and upgrades questions