Update a Decision Model

You can update a decision model for various purposes, according to the semantic versioning rules.

To understand semantic versionining, see Semantic Versioning Rules.

To ensure seamless integration, updating the minor or patch versions of a decision model does not disrupt the integration flow that references the model. The integration automatically incorporates these updates when you activate the updated model.

However, for a major version revision of a decision model, you must manually update the integration to use the new version.

Note:

After versioning a decision model, you must activate the new version for the integration to pick up the changes. There are limitations regarding the concurrent activation of versions. See Activate a Decision Model.

Versioning decision models serves the following purposes:

  • Change tracking: Allows maintaining a history of changes to your decision model to review previous versions or revert when necessary.
  • Support for multiple scenarios: Enables using different versions to address varying business automation scenarios.
  • Incremental development: Facilitates updating your decision model incrementally as your business requirements evolve over time.
To version a decision model:
  1. In your project, click Decision Decision icon in the left toolbar to view the list of decision models.
  2. In the Decisions box, point to the decision model you want to version, click Options icon, and click Create new version.
  3. In the Create new version panel:
    1. Update the Version field with an appropriate number, and add a description if necessary.
    2. Click Version.

    A new version of the decision model is created and listed in the Decisions box.

Semantic Versioning Rules

Oracle enforces semantic versioning rules, also known as SemVer, for all decision models.

With semantic versioning, you increment the version numbers in a meaningful and controlled way. A version number provides a quick explanation of the types of changes that are in the version.

Oracle Integration supports the following types of updates to decision models.

Type of update Example Guidance

Major version revision

1.2.3 to 2.0.0

The change adds a major new feature and has the potential to break backward compatibility.

Minor version revision

1.2.3 to 1.3.0

The change adds minor new features while maintaining backward compatibility.

Patch version revision

1.2.3 to 1.2.4

The change improves quality while maintaining backward compatibility.