Hi @Michael Derr, 

It sounds like our source control solution, Deltanji, would be a great fit for your setup.

Deltanji is tightly integrated with the IRIS environment, providing source control for Productions and Health-specific artifacts directly at the workface.

It is also well-suited to concurrent development. It has high-granularity branching and merging, so multiple developers can easily work concurrently on separate branches. 

We can set Deltanji up to suit your workflow as it’s fully configurable. Developers can work locally, in their own sandbox, before pushing to the development server, or by using a shared Dev instance, with Deltanji controlling concurrent edits. We can then achieve the master source control state that you mentioned very easily, with code being moved through the Dev, Test and Prod environments.

Regarding your comment about differences between dev and prod Interop Productions, our Deltanji Production Component Driver, which allows granular management of Productions, will allow you to safely transfer interfaces from dev to test to prod without ending up having your live production talking to your dev endpoints. 

If working in Git is an organizational requirement, we have a Git Integration, so you can manage your IRIS artifacts with Deltanji, and then push to a Git repository as an upstream record of the changes.

Our website has more information: georgejames.com/deltanji. We’d be happy to give you a demo as well, just DM me, or my email address is laurelj@georgejames.com.

Laurel

Another solution is to use Deltanji source control to manage and transfer these items, as this has the added benefit of providing full source control and accountability of changes to these items. I know you’re getting set up with Deltanji at the moment with John, so this is something he can help you with.

It was great to see you and the team in Birmingham!