APEX PAGES OVERRIDES
Apex Pages overrides are the possible options of certain standard actions (Accept, Clone, Delete, Edit, Tab, List, New, View) of Custom Object in Classic experience. The overrides can be controlled by the Subscriber. When the ISV makes the changes in the overrides settings of managed custom objects, these changes will not be delivered to the subscribers by the package upgrade.
What’s updated by Zuppio:
- All managed ActionOverrides are copied as-is from source to target org.
- ActionOverride is added to target org from source if it doesn’t exist in target.
- ActionOverride is overwritten if its type is Default/Standard in target org and is Visualforce in source org in case source Content is managed.
- ActionOverride is overwritten if its type is Visualforce in target org and is Default/Standard in source org in case target Content is managed.
- ActionOverride is overwritten if its type is Visualforce both in target and source orgs in case Content is managed both in target and source orgs and Content is different.
- ActionOverride is overwritten if its type is any in target org and is Visualforce in source org in case Content is managed both in target and source orgs.
What’s ignored by Zuppio:
- ActionOverride with Type different to Default, Standard or Visualforce on source org.
- ActionOverride with FormFactor different to null (or not specified) on both source and target org.
- ActionOverride with unmanaged Content on source org.
- ActionOverride from Custom Objects which don’t exist in target org.
- ActionOverride from managed Custom Applications which don’t exist in target org.
- ActionOverride with Content equal to managed ApexPages which don’t exist in target org.
