create-solution-installer

To create a DirectumLauncher installer plugin, you generate a scaffolding structure with a valid manifest.json, package files, and a plugin module implementing get_install_package_path(). This ensures the RX base package deploys first, followed by solution .dat packages.

A DirectumLauncher installer plugin scaffolding is a standardized folder structure with manifest.json and deployment logic for publishing .dat packages. You need it when deploying a BaseRnDComponent-based solution to ensure correct multi-package deploy ordering and UI-install steps.

Multi-package deploy ordering in a Directum RX installer plugin is configured via the get_install_package_path() method using semicolons to separate paths. This ensures the RX base package is included first, followed by your solution packages in the correct sequence.

Yes, generating a valid Directum RX plugin manifest.json requires mandatory SKILL variables including solution_name, plugin_name, alias, package_file, version, and dependencies. Optional flags like has_templates and has_public_api control whether template imports and PublicAPI raises are included.

Yes, a DirectumLauncher installer plugin can optionally import templates and raise PublicAPI during UI installation steps. The scaffolding guides adding required localization keys and flags to enable these features within the BaseRnDComponent deployment workflow.

When using BaseRnDComponent for Directum RX deployment, you must copy the identical base_component.py from the team reference to ensure consistent behavior. The installer requires strict adherence to the BaseRnDComponent contract and correct manifest dependencies to avoid breaking the deployment chain.