Move application definitions. Preserve operational history.

01 / APPLICATION LIFECYCLE

Package definitions with their dependencies

An application release describes a configuration that can be exported as a portable package. Package validation examines supported definitions and their dependencies so an installation is more than a collection of unrelated files. Forms, processes and other assets must refer to compatible configuration.

Packages carry application definitions, not a backup of the operating organization. They do not export the organization’s live business records, purchase state or integration credentials as a recovery image. Keep backup and restore planning separate from application distribution.

02 / APPLICATION LIFECYCLE

Resolve identities and configuration at the destination

Installation and cloning create destination-local identities. References must be resolved in the receiving context rather than reusing the source organization’s private identifiers as authority. Integration and other configuration requirements need deliberate attention before the installed application can operate.

This is especially important when a definition depends on a role, connection or asset. Review dependency validation and configuration requirements rather than assuming that a successful upload makes all execution paths ready. Portable structure and operational readiness are related but different checks.

03 / APPLICATION LIFECYCLE

Preview change before applying an upgrade

An upgrade preview helps an operator inspect the proposed configuration change. Published versions and historical runtime definitions are preserved so applying a newer application release does not rewrite the meaning of work that already ran. Running instances remain associated with their pinned definitions.

Retirement and archive behavior provide ways to manage definitions over their lifecycle. Evaluate an upgrade with a running instance and inspect the preview, current configuration and history afterward. This tests continuity through change, not just whether a new package can be imported.

• Build and publish the intended definitions.
• Create a release and export its portable package.
• Validate dependencies and destination configuration.
• Preview upgrades and inspect version preservation.

How do application assets fit into an operating lifecycle?

Use the educational guide to frame the design decision before comparing product capabilities.

• Building Operational Applications Around Business Processes