Usage Overview - TaskClone 1.0 vs 2.0

Learn how usage patterns will change from TaskClone 1.0 to TaskClone 2.0.

We know that workflow patterns can be difficult to change. While we're extremely excited about the upcoming launch of TaskClone 2.0, we wanted to highlight some of the usage differences to better prepare our existing clients. Overall, TaskClone 2.0 should be easier to use, easier to configure and substantially more powerful and flexible.

To make this possible, TaskClone was rewritten from scratch to support new features, but also stability, speed and future changes.

The key difference that allows 2-way sync and other features is the introduction of "Connections". Briefly, Connections link one source app account (e.g. Evernote) and one destination account (e.g. Todoist). Read on to learn about this and other usage changes.

	TaskClone 1.0	TaskClone 2.0
Integration Method	Destination set up once and used with any source based on trigger tag	“Connections” are set up to link a source and a destination. This method allows multiple source and destination accounts per TaskClone account and allows more flexibility than a trigger tag Connections allow processing the same note to different destinations with different settings simultaneously by having multiple connections. For example, processing checklist items and note titles simultaneously
Tasks Processed	All checklist items or note titles of notes with the “Trigger Tag” are processed	OneNote. All checklist items or note titles of notes in the notebook(s) and/or section(s) you indicate during setup of a connection Evernote. All checklist items or note titles of notes in the notebook(s) and/or with tag(s) you indicate during setup of a connection You can alternatively setup a connection to only process individual tasks you specify (using our special syntax) You can skip individual tasks (using our special syntax) You can send an individual task to the destination of a different connection (using our special syntax)
Sync Timing	Sync is immediate based on notification received and presence of Trigger Tag. User instructed not to edit note after adding Trigger Tag to prevent processing during continued editing	Sync is delayed until system detects you have stopped editing the note for at least 30 seconds to prevent processing tasks while you are still typing. No Trigger Tag needed. Backup processing at regular intervals to address notification failures and other disruptions Updates retried if failure occurs at source or destination
Activity Logs	Skip Code indicates task was processed Account history contains sum of tasks and events processed to any destination over entire account history	6 months of task by task activity indicating including timestamp of each task created, completed and the apps involved in that process.
Task Customization	Add notebook name and specified text to all tasks sent to a destination	Specify due date, label, priority and assignee to individual tasks (API-connected apps only)* Add notebook, section and specified text to all tasks of a connection Set up default due date, label, priority and assignee which can be overridden at time of writing task (API-connected apps only)*

* The ability add due dates, labels/tags, priority and assignees is dependent on the capabilities of the destination app you use. We will publish a table showing supported features by app.