Using the Repository in a Multi Tenant environment

Overview

This article covers how to pair and utilize a Decisions Designer Repository with a Multi-Tenant setup of Decisions. While there isn’t much difference in setting up and using a Repository in a multi-tenant environment, there are a few nuances users need to be aware of. 

• First, the Repository would need to be connected to each tenant. 
• Second, any project checked in or out from the Repository will pull from the same project. A project must be checked in/out from separate branches if individual variations of the project are needed for each tenant.

Setting up a Designer Repository Connection

When setting up a Repository connection for a tenant, the steps taken will be similar to how it is configured for a standard Decisions server. The only caveat would be that we would need to setup the connection for each individual tenant, and that setting up the connection to the Primary tenant should be avoided. 

1. In the tenant, navigate to System -> Settings
2. From the settings folder, select Designer Repository Settings
3. Under Repository Server, place the url to the repo server
4. Under the Advanced category, check Show Repository Actions

Checking projects in and out from the Repository

Projects can be checked in and out from the Repository individually for each tenant. However, changes checked into the Repository will update the source project. This can lead to issues if tenants require their own version of a particular project. For tenants to have their own versions of a project, they must be created in separate branches in the Repository