Managing Component States
Manage activation, versioning, and dependencies for components and objects as part of your deployment plan. A successful deployment makes sure that the system executes the intended, final, and active logic, preventing failures caused by stale or inactive component dependencies.
A component’s state is its operational status, which includes the:
- Active, inactive, or draft state
- Component version
- Dependencies on other components and objects
- Component-specific attributes like rank on expression sets
Components like decision tables, expression sets, and context definitions must be deployed taking their state into account. Also, some objects use an Active checkbox to determine if their records must be used during run time operations or not.
You must also make sure that all related dependencies are moved correctly and in the proper sequence from the source org to the target org.
Component deployments usually fall into one of these categories:
Deploy a New Component: If the target org doesn’t contain the component that you want to migrate, deploy it along with its versions from the source org to the target org.
Deploy Component Updates: When the target org already contains the component you want to migrate, then state and version management take effect. For example, with expression sets, you must deactivate the version in the target org where you want to deploy changes. If you try to deploy to an active version, the deployment fails.
Deploy Components with Dependencies: All related dependencies must be moved correctly and in the proper sequence from the source org to the target org. For example, expression sets reference elements such as decision matrices, decision tables, subexpressions, context definitions, field and object aliases, and explainability message templates. Migrate the dependent elements independently before you migrate the expression set version.
Refer to these links for examples and component-specific information:
- Considerations for Migrating Decision Tables
- Considerations for Migrating Expression Sets
- Migration of Expression Sets with Dependencies
- Migrate Context Definitions
Some Revenue Management components have unique activation requirements. For complete information about state management for these components, see Additional Deployment Information.