10,853
edits
Salesforce admins: Urgent action required!
App projects: Difference between revisions
Jump to navigation
Jump to search
→Project hierarchy
(→Project menu: add Process) |
|||
| Line 83: | Line 83: | ||
You can establish a parent/child relation between your projects. Child projects inherit all changes from the parent project except for the parts changed directly in the child project. | You can establish a parent/child relation between your projects. Child projects inherit all changes from the parent project except for the parts changed directly in the child project. | ||
Here are the basic principles of how this functions: | |||
* Creating a child project creates essentially an empty project (because it uses the project files of the parent project). | |||
* When you modify a setting or component in the parent project, and the child project does not have its own definition of the component, parent change is used. | |||
* When you modify a setting or component in the child project, the link to the parent is permanently broken for that component. Any further changes for the component in the parent no longer apply to the child. | |||
* Behind the scenes, project components are saved as files. For example, [[Sync Filter]] is stored as a single file. If you modify the sync filter in the child project, further changes in the parent will no longer be inherited. | |||
* In Woodford, many project components include the '''State''' column, indicating whether a component is inherited from the parent or overridden by the child.<br>[[File:Inherited or overridden.png|600px]] | |||
See also: | See also: | ||