Synchronization Logic
- The Outlook To Do list is created when the user creates or updates the Outlook Sync configuration. The default name for the list is "Maximizer", however, if a "Maximizer" list already exists in Outlook it will create the list with a versioned name, for instance, "Maximizer (2)".
- The synchronization between Maximizer and Outlook tasks happens in two steps – the initial sync and subsequent syncs. The first sync runs just once, after it, only subsequent sync happens, unless the user changes the settings. Note: Disabling and re-enabling the sync will trigger a fresh synchronization of tasks.
- Initial sync – the first sync retrieves all the overdue tasks (incomplete tasks) from last two weeks to today and all the tasks (complete and incomplete) from today and forward from Maximizer and creates them in Outlook. As the first sync starts with a new/empty Outlook To Do list, it does not pull any data from Outlook into Maximizer. Note: The sync range mentioned above only applies for the initial sync. Maximizer reserves the right to change the sync range. To ensure a smooth first sync, please make sure your Outlook To Do list is clear of any existing tasks.
- Subsequent sync – the sync retrieves newly created, modified or deleted tasks from Outlook and from Maximizer since the last sync run.
Note: To be synced your tasks in Maximizer must not be empty, as well as the title of your Outlook tasks must not be blank.
- Tasks classification list:
- Outlook:
- Created: tasks that were created, including new recurring series, that are not in sync.
- Updated: non-recurring tasks that were modified and are in sync.
- Deleted: tasks that were deleted and are in sync.
- Recurrences in sync: recurring tasks where its series is already in sync.
- Maximizer:
- Created: tasks that were created, including new recurring series, that are not in sync and are assigned to the user.
- Updated: non-recurring tasks that were modified and are in sync.
- Deleted: tasks that were deleted and are in sync or tasks that were unassigned from the user.
- Recurrences in sync: recurring tasks where its series is already in sync.
- Outlook:
Task Mapping Rules
Mandatory properties to sync tasks:
- Maximizer – the task subject must not be empty
- Outlook – the task title must not be empty.
From Maximizer to Outlook:
- Subject
- The first line of Subject of the Maximizer task will be mapped to the Title of the To Do Task in Outlook.
- If the length of the first line exceeds 255 characters, the exceeding content will be shifted to the second line.
- Any content below the first line will be mapped to the Outlook’s To Do Task Note.
- DateTime
- As Outlook’s To Do Task/DueDate supports only the date, Maximizer’s tasks with both date and time will be converted to full-day tasks (date only) before syncing to Outlook.
- Priority
- Maximizer task priority can be customized by the user.
- Only default values (HI, LOW, MED) will be mapped.
- Other customized values, such as "high" in a different language, will be mapped as MED.[EZ1]
- The default value from Maximizer "MED" is mapped to "Normal" in Outlook.
The below table contains which property in Maximizer Task is mapped to Outlook Task.
| Maximizer Task Property | Outlook Task Property | Comment |
| Task's 1st line | Title | Extra information on item 4 of the above list |
| Task's 2nd line and forward | Body | |
| Status or Completed | Status | Completed and Status are two different properties in Maximizer, when the Completed is true, it will set Completed Status in Outlook Task, otherwise it will map using the Status property |
| DateTime | DueDateTime | |
| Priority | Importance | Default value from Maximizer "MED", which is mapped to "Normal" in Outlook |
| CompletionDate | CompletedDateTime | |
| Alarm | IsReminderOn | if Alarm in Maximizer is not null, then it will set IsReminderOn to true, otherwise false |
| Alarm | ReminderDateTime | It will user Alarm datetime from Maximizer and set TimeZone to UTC |
| Recurrence.Pattern.Type | Recurrence.Pattern.Type | |
| Recurrence.Pattern.FirstDayOfWeek | Recurrence.Pattern.FirstDayOfWeek | When null, the default is "Sunday" |
| Recurrence.Pattern.Interval | Recurrence.Pattern.Interval | |
| Recurrence.Pattern.Index | Recurrence.Pattern.Index | When null the default is "first". Property is also known as WeekIndex |
| Recurrence.Pattern.Month | Recurrence.Pattern.Month | |
| Recurrence.Pattern.DayOfMonth | Recurrence.Pattern.DayOfMonth | |
| Recurrence.Pattern.DaysOfWeek | Recurrence.Pattern.DaysOfWeek | |
| Recurrence.Range.StartDate | Recurrence.Range.StartDate | |
| Recurrence.Range.EndDate | Recurrence.Range.EndDate | |
| Recurrence.Range.Occurrences | Recurrence.Range.NumberOfOcurrences | This property value is always 0 in Graph API (Outlook), even when the sync forces a value. |
| Recurrence.Range.RecurrenceTimeZone | Recurrence.Range.RecurrenceTimeZone | Default is UTC. |
From Outlook to Maximizer
- Alarm
- Due to Maximizer not allowing alarm time after the due datetime, the alarm time will be adjusted to the due datetime if set after the due datetime.
- DueDate
- In Outlook, the due date is an optional field, and in Maximizer it is mandatory. If the due date is not specified in Outlook, and if alarm time is set, alarm day + 1 day will be utilized as the due date, otherwise the creation date will be utilized as the due date before syncing with Maximizer.
The below table contains which property in Outlook Task is mapped to Maximizer Task.
| Outlook Task Property | Maximizer Task Property | Comment |
| Title | Task's 1st line | If the title is null or empty, the default value will be a "." |
| Body | Task's 2nd line and forward | |
| Status | Completed | If outlook status is completed, it will set true, otherwise false |
| Status | Status | If outlook status is completed, value will be set to null, otherwise map accordingly |
| - | AssignedTo | Will assigned the task to the user for new tasks, and for updates it will ignore the update in case the task has been unassigned from the user |
| Importance | Priority | Will map accordingly, if Importance in outlook is null the default value will be "MED" |
| DueDateTime or ReminderDateTime or CreatedDateTime | DateTime | When outlook's Due Date is not null, will use it, otherwise will check if reminder is on, in case it is on it will use the ReminderDateTime. If previous are false, it will use the outlook's created date |
| CompletedDateTime | CompletionDate | |
| IsReminderOn and ReminderDateTime | Alarm | When reminder is off, it will set maximizer alarm as null. When reminder is on, will set alarm using the reminder date |
| Recurrence.Pattern.Type | Recurrence.Pattern.Type | |
| Recurrence.Pattern.FirstDayOfWeek | Recurrence.Pattern.FirstDayOfWeek | When null, the default is "sunday" |
| Recurrence.Pattern.Interval | Recurrence.Pattern.Interval | |
| Recurrence.Pattern.Index | Recurrence.Pattern.Index | When null the default is "first". Property is also known as WeekIndex |
| Recurrence.Pattern.Month | Recurrence.Pattern.Month | |
| Recurrence.Pattern.DayOfMonth | Recurrence.Pattern.DayOfMonth | |
| Recurrence.Pattern.DaysOfWeek | Recurrence.Pattern.DaysOfWeek | |
| Recurrence.Range.StartDate | Recurrence.Range.StartDate | |
| Recurrence.Range.EndDate | Recurrence.Range.EndDate | |
| Recurrence.Range.NumberOfOcurrences | Recurrence.Range.Occurrences | This property value is always 0 in Graph API (Outlook), even when the sync forces a value |
| Recurrence.Range.RecurrenceTimeZone | Recurrence.Range.RecurrenceTimeZone | Default is UTC |
FAQ
What happens if I update the Task Sync settings?
At the moment, you can't select a specific Outlook To Do List for syncing. You can only enable or disable the task sync feature. If you disable and re-enable the sync, it will automatically trigger a complete resynchronization of your tasks.
web outlook only have "important" tasks, without segregation into Low, Med, High [EZ1]