FLEXI PAGES OVERRIDES
Flexi Pages overrides are the possible options of the actions in Lightning experience. Flexi Pages can be overridden on the Object level, Application level, and on the Profile level. All types of the overrides can be controlled by the Subscriber. When the ISV makes the changes in the overrides settings, these changes will not be delivered to the subscribers by the package upgrade.
Option 1 is the override of the standard actions on Custom Object (Accept, Clone, Delete, Edit, Tab, List, New, View) at Object level or at the Application level. In this case:
What’s updated by Zuppio:
- All ActionOverrides from Custom Objects 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 Flexipage in source org in case source Content is managed.
- ActionOverride is overwritten if its type is Flexipage in target org and is Default/Standard in source org in case target Content is managed.
- ActionOverride is overwritten if its type is Flexipage 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 Flexipage 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 Flexipage on source org.
- ActionOverride with FormFactor different to Large 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 Flexipages which don’t exist in target org.
Option 2 is the override of the standard actions on Custom Object (Accept, Clone, Delete, Edit, Tab, List, New, View) at Profile level. In this case:
What’s updated by Zuppio:
- All ProfileActionOverrides are copied as-is from source to target org.
- ProfileActionOverride is added to target org from source if it doesn’t exist in target.
- ProfileActionOverride is overwritten if its type is Default/Standard in target org and is Flexipage in source org in case source Content, PageOrSobject and (if exists) RecordType is managed.
- ProfileActionOverride is overwritten if its type is Flexipage in target org and is Default/Standard in source org in case target Content, PageOrSobject and (if exists) RecordType is managed.
- ProfileActionOverride is overwritten if its type is Flexipage both in target and source orgs in case: Content is managed both in target and source orgs and Content is different, PageOrSobjectType field is managed both in target and source orgs and is the same, RecordType if exists managed both in target and source orgs and the same.
- ProfileActionOverride is overwritten if its type is any in target org and is Flexipage in source org in case Content, PageOrSobject and (if exists) RecordType is managed both in target and source orgs.
What’s ignored by Zuppio:
- ProfileActionOverride with Type different to Default, Standard or Flexipage on source org.
- ProfileActionOverride with FormFactor different to Large on both source and target org.
- ProfileActionOverride with unmanaged Content, PageOrSobject and (if exists) RecordType on source org.
- ProfileActionOverride from Custom Objects which don’t exist in target org.
- ProfileActionOverride from managed Custom Applications which don’t exist in target org.
- ProfileActionOverride with Content equal to managed Flexipages which don’t exist in target org.
