What happens when an application is installed?
Installing an application from the Application Directory is the equivalent of using the Setup area to create an Application instance along with a number of Tabs, Portals, Objects, and their components such as Fields, Relationships, Pages, Views, Charts, etc. Once an application is installed you will see all of its Objects and other components in the same Setup locations you use to manage components from other applications.
Can applications share objects and other components?
Yes. Many applications share object definitions. When you install an application that uses an object you already have installed, that object will not be overwritten. Instead, Progress Rollbase will only add any object components that are missing from that object to bring it up to date with the application being installed. This may include the creation of fields, relationships, views, charts, and other object components.
How does object sharing work across multiple applications?
Although you don't see this as a Rollbase Administrator, all objects have a unique global ID that allows Rollbase to track which objects have been installed in any given account. In this way, Rollbase automatically takes care of any object conflicts for you. When publishing an application that should share an object from another application, you must first install an application containing that object and use it in the application you intend to publish.
How does application publishing and installation work behind the scenes?
Progress Rollbase is a purely model-driven, multi-tenant, on-demand application development and delivery platform that is based on a proprietary application serialization, publishing and execution engine. Whenever an application is published, the entire application including all of its components and component configurations, including images and document templates, get serialized into the Rollbase XML format which is then stored in the Application Directory. The only thing not included in the published version of an application is the actual data in the publisher's account. When another user installs this published application, the XML representation is parsed and recreated in the user's environment as if it was copied directly from the publisher.