Application components (core system), databases, reports, user interfaces, and external files can all be deployed separately.
Use top-level folder configuration properties to specify which elements should be grouped together in a deployment package.
If a report class, or folder is selected for building, ensure the configuration properties set for the folder matches the top-level deployable Element properties. For example, ensure the deployment paths and database host matches the correct system.
Including External Installer files
Using Configuration Properties, you can bundle and execute external files within selected deployment packages. Builder typically binds external files as nested files.
Note: External files must be capable of running without user input, otherwise deployment might appear to hang when it is actually waiting for input for an external package.