Post-deployment tasks

There are tasks that must be completed after the global package has been deployed. This section describes these tasks.

After deploying the package, log in to ION on the target tenant to confirm successful resource deployment.

Next, check the table below for potential post-deployment actions:

Task Description
Activate the models
  • Activate data flows.
  • Activate workflow definitions.
  • Activate monitors.
  • Activate alarm templates.
  • Activate activation policies.
Connect > Enterprise Locations
  • Create credentials for the location.
  • Download and install an Enterprise Connector on the target tenant-specific local (on-premises) system.
Connect > Enterprise Connector connection points
  • If applicable, configure the connection parameters.
  • Create and link PGP keys.
Monitors & Workflows > Workflows
  • Users are tenant-specific and are not exported or imported. If you need users in your workflow definition distribution lists, add them.
  • If API calls are configured, API calls require a Service Account for authentication. Service Accounts are tenant-specific, so create a new Service Account in the target tenant or use an existing account and apply it to the API call.
Monitors & Workflows > Monitors

Users are tenant-specific and are not exported or imported. If you need users in your monitor definition distribution lists, add them.
Monitors & Workflows > Business Rules

Users are tenant-specific and are not exported or imported. If you need users in your business rule distribution lists, add them.
Configuration > Error Reporting

Configure email addresses. See the Receiving emails for exceptions topic in the ION documentation.
Configuration > ION Service > Configuration Files > Certificate Store

Import trusted certificates.
Configuration > ION Service > Configuration Files > E-mail Templates

Adjust any templates that include tenant-specific email references. See the Customizing the layout for email notifications topic in the ION documentation.

Working with the live version after first deployment

After the initial deployment, your main working area is the version shown in the UI as the live version. Your organization uses this version in daily operations and can adjust the delivered package items to fit its business needs.

You can:

  • Adjust configurations.
  • Extend or refine business logic.
  • Align delivered items with your specific processes.

These changes remain under your control and are preserved when new package versions are deployed later.

Adopting changes from a new package version

When a new package version is delivered, ION makes the updated content available in the version shown in the UI as the reference version. Your live version continues to run unchanged.

To benefit from the new version, review the updates and decide which changes to apply to your live environment. This is a manual, user-controlled process.

This process typically includes these actions:

  • Identify which delivered items are relevant. Not every item requires attention, so focus on items that are important for your business processes or are known to include updates.
  • For each relevant item, compare the current live version with the updated reference version.
  • Decide how to proceed for each item:
    • Keep the current live version unchanged if it already meets your needs.
    • Fully adopt the updated version if it includes important improvements.
    • Selectively apply specific updates while keeping your existing customizations.

After making this decision, update the live version manually to include only the changes you want to adopt. Because ION does not automatically merge updates into the live version, apply these changes carefully and intentionally.

Also review whether existing live items must be connected to newly added items in the updated package version. These connections are not created automatically because the upgrade does not change existing live configurations. Identify and add any missing connections manually.

Finally, validate the updated live configuration to confirm that:

  • Existing business processes continue to work correctly.
  • Newly adopted changes behave as expected.
  • Related items and configurations are properly aligned.
Note: Copying, exporting, or deleting delivered items from a global package is not permitted.