Page History

...

Model configuration based on existing configuration

This makes it easy to create The Problem: An easy way to start configuring a business object ( such as a content app is to model it off of an existing content app. However, a template, or a dialog) by comparing it against an existing business object
One can easily tell what nodes/properties are still missing and quickly create them
One can easily tell what modifications one has made on top of the baseline object
when there is a lot of configuration, it is difficult to tell what configuration one one has that the other doesn't and whether these differences are on purpose or by accident. One must also either scroll a lot to do the comparison or go through the annoyance of placing two windows next to each other.
The Solution:
- Select the root node for the baseline business object on the left of the split view and the root for the new business object on the right
- Easily tell what nodes and properties the baseline business object has that the new business object does not
- Quickly migrate these differences from the baseline business object to the new business object using actions supplied by the app
- Easily review the differences between the baseline and new business objects in the end to make sure all differences are on purpose
- Use sample business objects supplied by Magnolia to get started quickly
Sample business objects can be specifically supplied to serve as templates for creating new ones

...