26.1.0

Sync Tool 26.1.0 is the first release of the Sync Tool. It moves selected entities from one inorigo® instance to another, for example to promote model changes from development to test to production.

Purpose of this release

This first version covers the core flow from start to finish:

• find the entities that have changed in the source instance,
• collect them in a pull request, together with the dependencies they need in the target,
• review what merging the pull request will change in the target, and
• merge it, with a comment that stays with the pull request.

It focuses on that flow, so some things you may expect are not there yet. They are listed below.

For a full walkthrough, see the Sync Tool documentation.

Not yet included

• No approval step. A pull request is a draft, merged, or failed. There is no state for a pull request that is waiting for someone else to approve it.
• Some entities cannot be synchronized. Users, security groups and their relations, authentication records, UI components, data objects with a variant that cannot be synchronized, and pull requests themselves stay in the instance where they were created. A pull request that would change one of them cannot be merged. Make such changes in the target by other means.
• No transaction comments in the search results. The Source panel does not show the comments from the source's transaction history, and you cannot filter on them.
• No adjustment for the target environment. Take care when you synchronize entities that are tied to the source environment, such as data sources that point to local data files on the source server, or HTML files with hard-coded links to the source domain. They may not work as intended in the target.

Compatibility and system requirements

• Minimum inorigo® platform version 22.6.2, on both the source and the target instance.
• Both instances need the same version of the Sync Tool plugin.
• An administrator sets up which source instances a target accepts, in System Management. Enter each instance URL in full, ending with a slash, for example https://<server>/inorigo/.
• You need to be able to sign in to both instances.