App installation process
If you need to manually install an app, the app (.ppk file) is configured at run time.
Some apps may require additional configuration, make sure you have completed the required configuration steps first.
For all apps installed, the following information is displayed:
• Its name
• Its partner identifier
• Its version
• The Platform API versions on which it is built (multiple API versions are possible)
• The Planon version on which it is built.
• A description of its functionality
Here, you can also set the app's status to Active/Inactive.
Some business objects may be set Under construction and a cache refresh may be required when activating/deactivating apps (see Field definer).
 | • For some apps, it is possible that the App account field needs to be filled in to activate the app. Only when you configure the Module settings in Details selection level, you will be able to select the App account field and activate the app. For more information, see Configuring module settings. • Note that it is not possible to downgrade an app to an older version. If an app is already installed, then only the same or newer versions of that app can be installed. |
Modules level displays the relevant information of a module.
Details level displays the technical details of the app:
• Module configuration: displays the app's JSON configuration.
• Module settings: displays the app's settings than can be further configured.
For more information, see Configuring module settings.
• App component settings: displays the app's component settings.
• Artifacts: displays the app's artifacts (jars) that are deployed.
The configuration is applied at run time, which implies that it also available for on-premise installations.
 | Note, however, that clustering is not supported. |
Important
When an app has various artifacts and one of these artifacts cannot be properly deployed, the app status will be Failed.