Setting up project dependencies
New in 8.10.2 Administrators and configuration managers can set up project dependencies in the Business console to make a project available in different decision services or branches.
A project in a decision service can be referenced by other decision services, or in other branches of the same decision service. All items in the referenced project are then available to you for use in your current decision service or branch. For example, you might want to place your BOM and vocabulary in a separate project and reference it, so that you need to maintain only one BOM and one vocabulary, and changes made to the BOM and vocabulary are automatically propagated to all the projects that use them.
Before you create project dependencies, make sure that you have a clear idea of how your decision services and branches will be organized to share one or several projects. Take some time to assess how any modification to a rule artifact in a shared project can impact the different branches and decision services that share this project.
Creating a project dependency
To create a project dependency:
- Open the main branch of your decision service.
- In the Branch pane, expand the Linked Projects section, and click Edit dependencies. The Dependencies editor opens.
- Select your project in the Project list to see the list of its dependencies (if any). Click the + icon to add a new dependency.
- Double-click the blank fields of the new dependency to select the decision service, project, and branch you want to reference in your current project.
- Click Save.
- Go back to your branch with the breadcrumbs. Your shared project is indicated by the
shared icon in the Decision Artifacts tab, and a tooltip when you hover over the project name. The tooltip is limited to five dependencies at most, but you can review the full list in the Linked Projects section.
Migrating classic rule projects that use project dependencies
- Follow the procedure at Migrating classic rule projects to decision services.
- After the migration is complete, you must publish your decision services to Decision Center. To publish, see Publishing decision services to Decision Center. You must keep the dependencies when publishing.
- In the Business console, open the Library tab to see the decision
services that you published. By default, because you kept the dependencies in Rule Designer, you can see in the main branch of
each decision service that your common project is still shared, as indicated by the
shared icon, and the tooltip that is displayed when you hover over your project name in the Decision Artifacts tab.
- When you create subbranches from your main branch, you must re-establish the project dependencies. See Working with branches.
Setting project security for shared projects
Administrators can set permissions for groups of users to access a project from the Setting project security).
(seeWhen you enforce security on a decision service, the security settings do not apply to shared projects in this decision service. You must set the permissions for these shared projects manually.
The security settings that you apply for a shared project are available to all decision services that references this project.