Loading
시스템 관리자에 대한 피싱 방지 MFA 및 전 직원사용자 MFA 적용 안내 더 많이 읽기
Business Rules Engine
Decision Matrix Migration Considerations

You are here:

  1. Salesforce Help
  2. Docs
  3. Business Rules Engine

Decision Matrix Migration Considerations

Here are a few typical migration scenarios and recommendations on how to maintain decision matrices in your target org for a successful migration.

Required Editions

Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions for clouds that have Business Rules Engine enabled

The result of decision matrix migration depends on whether the decision matrix and its versions exist in the target org and on the status of such versions.

Note
Note

When you migrate a decision matrix version, only the column headers of the version migrate to the target org. Row data isn’t migrated.

Before you migrate a decision matrix version, specify a rank and activate the version in the source org. Then, migrate the version or the entire decision matrix to the target org. The migrated decision matrix version is invoked in the target org based on the specified rank. Migration fails if the target org already contains a decision matrix version of the specified rank.

Decision Matrix Configuration Migration Behavior Migration Recommendations
The target org doesn’t have the decision matrix. The decision matrix and its versions migrate successfully.
  • Deploy the decision matrix in the target org.
  • Migrate the decision matrix versions independently.
The target org has the decision matrix with one or more versions, where some or all the versions are active. The migration fails. Deactivate active decision matrix versions in the target org and then try again.
The target org has the decision matrix but all matrix versions are inactive. The decision matrix migrates successfully and all the versions from the source org replace the versions in the target org.

Migrate individual decision matrix versions separately, rather than migrating an entire decision matrix with its versions together.

This approach gives you more flexibility to evaluate what a decision matrix version contains and change your migration approach accordingly.
The target org has the decision matrix with only a subset of the versions from the source org, and all the versions are inactive.
  • The decision matrix migrates successfully and all the versions from the source org replace the inactive versions in the target org.
  • The versions that didn’t exist in the target org are added to the target org under the parent decision matrix.

Scenario 2: Migrate a Decision Matrix Version

Here, you’re migrating a decision matrix version independently, and not the entire decision matrix to which the version belongs.

Note
Note

When you migrate a decision matrix version, only the column headers of the version migrate to the target org. Row data isn’t migrated.

Decision Matrix Configuration Migration Behavior Migration Recommendations
The target org has the same decision matrix version in active state. The migration fails.

Deactivate the decision matrix version in the target org and then try again.

The migrated decision matrix version from the source org overwrites the inactive decision matrix version in the target org.
The target org the same decision matrix version, but in inactive state. The version from the source org migrates successfully and overwrites the inactive version in the target org. We recommend this migration approach.
The target org doesn’t have the decision matrix to which the version from the source org belongs. The migration fails. Deploy the decision matrix in the target org and then migrate the version again.
 
로드 중
Salesforce Help | Article