Migrating classic rule projects to decision services

Make sure that your classic rule projects meet the prerequisites and use the migration wizard to migrate them to decision services in Rule Designer.

Before you begin

A decision service is the recommended unit of rule management, since it allows for complex decisions that involve several rule projects to be grouped as one entity. Synchronization, branching, and change management are applied to all rule projects in the decision service hierarchy, allowing the decision service behavior to be governed and deployed consistently.

You do not have to migrate your classic rule projects to decision services. If you do, take note of the following points:
  • Any rule project that you migrate can no longer be used in a classic rule project structure.
  • You cannot migrate a rule project contained in a decision service back to a classic rule project.
  • You cannot use RuleApp projects to deploy a decision service. You must create and use deployment configurations.
Before you migrate classic rule projects to decision services, make sure that your classic rule projects meet the following requirements:
  • In each rule project, the variables of the ruleset parameters have a verbalization value.
  • There is no cyclic project reference between rule projects. For example, if project A refers to project B and project B refers to project C, check that project C does not refer to project A.
  • If your rule projects refer to other rule projects, the referenced projects are open.
  • If your rule projects refer to other rule projects, the referenced projects are already migrated, or you migrate all projects at the same time. For example, if project A refers to project B, you either migrate project B before project A, or you migrate both projects at the same time.
  • If you want to migrate projects from Decision Center, you must ensure that the projects are synchronized with Rule Designer.
Note: If you have decision service projects from Operational Decision Manager V8.5.x, you must convert them back to classic rule projects, and them migrate them to decision services. To do so, right-click the project and choose Properties. Then, click Decision Service on the navigation panel, and deselect Handle this project and its dependencies as a Decision Service in Decision Center.

Procedure

  1. Open the Rule Designer workspace that contains the classic rule projects that you want to migrate.
  2. From the Rules perspective, click the Rule Projects Migration icon in the toolbar.
  3. Follow the steps in the migration wizard.

Results

The wizard creates a report that lists the changes and resulting elements.

What to do next

If you synchronized projects from Decision Center to Rule Designer before migrating, synchronize the projects again with Decision Center.