Confluence has been updated to version 6.15.9

This page shows how to start a synchronization.

Navigate to the Connections tab in the Exalate admin menu

1. Initiate Connection 

1.1 Choose a Connection type

   Connection type defines how to communicate with the Destination Instance.
   You can synchronize between Instances, even if one Instance is not accessible from the outside network. 
   You can also use Local Connection to synchronize between projects within one Instance. 
   The configuration depends on the connection type.

   Another instance which is accessible from your side - synchronization with the Instance you can access from your Instance.
   Another instance which is not accessible from your side - synchronization with the private Instance, which you cannot access from your Instance.    
   Local Connection - synchronization between two projects within your Instance;

1.2 Specify Connection details

This step is available only if the Destination Instance is accessible from your side.

If the Destination side is Servicenow you need to use the Exalate app for Servicenow URL.

1.3 Choose Sync Rules template

 The connection between instances requires sync behavior configuration on both sides. 
 You need to specify which issue data you want to send, and the project for incoming sync requests.
 It's required because Exalate creates issues whenever synchronization is received. 

 Single project synchronization

 Single project synchronization does not require scripting. Please, select the project for incoming sync requests to generate default sync rules. 
 By default the following issue data will be synchronized: summary, description, type, comments, attachments and labels.
You can adjust generated scripts later by editing the connection.


Single project synchronization template is available only on the Create Connection step.

Connection editing is performed in the advanced template mode.
 Advanced synchronization

Advanced synchronization requires setting local project key and issue typeName for incoming sync requests directly in scripts.

You can set a default project key and issue type here.

Shortcut to validate scripts

CTRL+1 helps to validate scripts and move to the next step.

1.4 Add Connection name and click Initiate сonnection button to proceed

2. Send an invitation

Congratulations! The connection has been successfully created. Your side is set up. Now invite your partner to communicate with you.
Copy the Invitation and send it to the Destination Instance administrator. This is last step of the Connection set-up from your side. 
Once your partner Accepts the invitation, you can start syncing issues.

Connection Invitation helps to send a pre-configured invitation to your partner. It ensures that communication with the Destination Instance is correct and you can start syncing issues. 

If your Connection is local, you don't need to send the invitation.

  1. Make sure the Invitation has been accepted and synchronize issues!

    Once the other side accepts your invitation your connection will be activated. Refresh Connections page to see Connection status change.

    Connection statuses

    Pending - Connection is set-up on your side. Once your partner accepts the invitation the status will be changed to Active.

    Active - Connection is active; you can start issue synchronization.

    Deactivated - Connection is not active, issue synchronization will not be performed if the Connection is inthis status.

    Navigate to the issue view, click More and use Exalate button to start issue synchronization.

    Check other ways to synchronize issues.

Congratulations! You've just configured a Connection. 

Proceed to the configuration, to specify your particular synchronization behavior.

Also, you may check some typical Use Cases.