Deployment

You must prepare the application before deploying the global package.
  • Verify that ION is enabled by confirming that the ION menu is displayed in Infor OS Portal.
  • On the Deployed global packages page in CSSP, verify that no other package deployments are running in the same environment.

For deployment steps, see the CloudSuite Self-Service Portal User and Administration Library and select Administrator > Configuration Management.

First deployment

When you deploy a global package in ION for the first time, the system creates two versions of each delivered resource in your environment. This approach enables your organization to use and modify the package content while retaining a record of the original Infor-delivered content.

The version used in daily operations is displayed in the UI as the live version. You can edit this version so that your organization can adapt it to its business processes from the time the package is deployed.

The second version is displayed in the UI as the reference version. This version contains the original Infor-delivered content. It is read-only and cannot be changed. The reference version provides a stable baseline that you can use to compare your current configuration with the standard package content.

Enterprise Locations

Enterprise Locations follow a different versioning model.

  • During the initial deployment, a live version is created, but no reference version is created.
  • Subsequent package deployments do not create reference versions for Enterprise Locations.

Subsequent deployments and version upgrades

When you deploy a new version of the same editable global package, ION preserves your current operational configuration.

Your live version remains unchanged, so business operations can continue without interruption and your customizations are not overwritten. At the same time, ION updates the reference version with the latest content from the global package.

The updated content is available next to your current configuration instead of being applied automatically. You can review the changes and decide whether and when to adopt them from the new package version.

Benefits of the deployment model

This deployment and upgrade model provides several benefits.

Your customizations are protected because the live version is not overwritten during package upgrades.

You can review changes between package releases because the original Infor-delivered content is updated with each package version. This comparison helps you understand how your current configuration differs from the standard package content.

You remain in control of the upgrade process. Updates are available for review, but they are introduced into the live environment only when you decide that they are relevant and ready to be applied.