Lines image

Easy Collaboration and Change Control with 1Integrate

Seamless team collaboration is more important than ever, as remote working becomes increasingly common and transforms how many businesses work. But even teams in the same office space may find themselves working on the same projects and sharing code.

In such cases, the use of a Version Control System (VCS) is a vital addition to your workflow and is a well-established practice among development and delivery teams. With the latest release of 1Integrate, it is now even easier to apply these best practice approaches within your teams of rule writers.

1Integrate Synchronisation Tool workflow

For example, a team within your organisation could be collaborating on writing rules for one project, each with their own local 1Integrate repository. By using the 1Integrate Repository Synchronisation Tool and a VCS such as Git, team members can push changes they have made, and pull any changes that other team members have made.

Within 1Spatial, our consultants use this to allow multiple users to author rules on different environments, and then pull the deliverable together via a version control system.

The 1Integrate Repository Synchronisation Tool is now provided as part of official product release packages, meaning 1Integrate customers can take advantage of this methodology and the variety of benefits that come with it.

1Integrate Repository Synchronisation Tool interface

Track Changes and Resolve Conflicts

A simple workflow for tracking changes to your 1Integrate Repository would be the following:

  1. Determine a local file system to use and connect to VCS (e.g. Git/Bitbucket).
  2. Configure the tool to point to 1Integrate and your file system
  3. Work as usual
  4. Click Run Sync within Synchronisation Tool (make sure your repository and file system match)
  5. Commit changes to your VCS, using a tool such as Git Bash, Tortoise, Source Tree (make sure your file system and VCS match)

1Integrate Repository Synchronisation Tool configurationNow the changes you have made are submitted to your VCS and can be pulled by other users. Similarly, you can pull any changes made by teammates. The VCS can be used to detect and resolve any conflicts or differences between user submissions.​

Because you can configure which parts of your 1Integrate repository are synchronised, you could select only certain project folders. In practice, this allows you to keep any custom configured data stores and sessions, and only update the rules and actions applied within those sessions.

Increase Automation

At 1Spatial, we’re committed to automation and efficiency. Our Synchronisation Tool allows for increased automation, making deployments and test more efficient.

An example of this enhanced workflow in practice can be found in deployment of our US NENA Validation project.

Our previous workflow for updates was:

  1. Install the software
  2. Deploy our “Standard Package” of validation rules for NENA
  3. Configure data stores
  4. Configure sessions
  5. Configure 1DataGateway

Upon updating any rules/actions we had to repeat the steps 2-4 which is an inefficient use of time that could have been spent on other activities such as testing.

With the Repository Synchronisation Tool we have the power to deploy just the rules/actions, but the customer-specific data store and session configuration remains consistent and doesn't need to be updated.

Share Rules Between Teams

Working with the Synchronisation Tool removes barriers for sharing rules, whether that’s between departments or more widely between businesses.

Sharing expertise benefits everyone, and this opens up the possibility of creating a rule repository marketplace where rules can be exchanged.

If you would like to find out more about 1Integrate or any of the other 1Spatial products and solutions, or how we can help you unlock the power of your data, please get in touch.