• Attribute Mapping Editor

    Tasktop Sync 2.3 includes an attribute mapping editor to improve the ease of setting up a new Sync installation. Together with Quick Start, the attribute mapping editor allows administrators to quickly create the repository connections and synchronization mappings between repositories visually. The attribute mapping editor builds upon Sync's repository schema introspection to present the administrator with a list of available attributes to be mapped as well as a list of available casters that can be used in the mapping.



  • Integration Visualizer

    Sync provides a comphrensive and live architectural overview of the configured synchronization mappings that allows the users to understand the overall integrated architecture quickly, as well as a snapshot of the current health of the synchronizations between different pieces of the architecture.


  • Task Synchronization History Log

    Previous versions of Tasktop Sync provided output that summarized Sync's execution in the console view, together with an extremely detailed on-disk log that could be used for debugging errors during synchronization. To these, Tasktop Sync 2.3 introduces the Task Synchronization History log. This view presents the user with detailed logging output that is filtered to report only information relevant to the synchronization between a given task and its proxy. In addition in making it easier to track down problems during synchronization, this view also provides a detailed history of all of the synchronization steps that have been taken with respect to a task.


  • Automatic Configuration File Migration

    Sync now provides automatic configuration file migration. When upgrading to a new version of Tasktop Sync, Sync will automatically detect if there are any changes that must be made to existing configuration files and prompt the user to make these changes automatically. Sync will provide a detailed description of the changes that were applied, and old configuration files are always backed up for future reference.

  • Improved Error Handling and Reporting

    In 2.3, Sync's error handling capabilities have been further improved to provider a more fine-grained distinction between temporary error conditions and error conditions which require manual intervention. Errors such as a failure to connect to a repository or other network errors are typically temporal errors, whereas errors such as a proxy task missing required attributes require manual intervention. Sync now distinguishes between these types of errors by automatically retrying synchronizations encountering temporal errors a limited number of times. This further reduces the amount of time required to maintain a Tasktop Sync instance by only requiring administrative attention when absolutely necessary.


  • Synchronization of Newly Created Attributes

    Many repositories and repository configurations setup default attributes on a newly created task (specifically the assigning of a new task ID to the created task). Sync now supports seemlessly synchronizating these intialized attributes on a newly created proxy task back to the source task during the initial synchronization. This means custom attributes can be configured in both repositories to the store task ID of the task's proxy in the other repository.

  • Disable Task Mappings Dynamically

    To improve the process of configuring Sync, task mappings can now be enabled and disabled dynamically while Tasktop Sync is running allowing the user to easily switch back and forth between mappings while testing different configurations without making extensive edits to the configuration or starting and stopping Sync.


  • Proxy Associations Can Be Stored on a Specified Attribute

    The default attribute that Tasktop Sync uses to store the proxy association URL can now be overridden so that proxy associations are stored in an arbitrary attribute. This is especially useful for repository configurations that have restrictions on the creation of additional custom attributes, or if the default storage strategy for that repository is otherwise not suitable.