Yes, each Exalate connection has its own sync rules and triggers, allowing you to fully customize synchronization behavior per connection. Different projects, teams, or partners can use separate logic, field mappings, and automation settings under the same subscription.
Independent Sync Rules for Each Connection
Sync rules are Groovy-based scripts that define what data to send out and how to apply incoming data. One connection can sync all work items with full field mapping, while another only syncs high-priority items or specific projects with tailored transformations. You have full script and operational control over your sync, implementing filtering, mapping, and value transformations unique to each connection.
This includes conditional logic based on status, priority, labels, or custom fields. For example, a connection to an external partner might exclude sensitive fields and mask certain data, while an internal connection between teams shares complete information with no restrictions.
Connection-Specific Triggers
Triggers determine which entities start syncing for each connection separately. A connection can automatically sync only items matching a query, such as a specific project, label, or status. This while another connection uses a different trigger filter or manual sync only. This flexibility ensures each integration behaves according to its specific requirements without affecting other connections.
Isolated Behavior When Connections Are Paused
If a connection is deactivated, synchronization events are queued and resume from where they stopped once the connection is re-enabled. This keeps behavior isolated per connection, ensuring that pausing one integration doesn't impact others. You maintain independent control over each connection's lifecycle and operational status.
Use Cases for Per-Connection Customization
- Cross-Organization Collaboration: Share limited fields with external partners while maintaining full synchronization internally.
- Multi-Team Environments: Configure different sync logic for development, support, and operations teams based on their unique workflows.
- Tiered Access: Provide different levels of data visibility and sync depth depending on the relationship or trust level with each connected party.
- Regional Requirements: Adapt field mappings and transformations to meet different compliance or business rules across regions.