Today, The Omni Group announced OmniFocus 4.7, which brings interesting new productivity and workflow features. However, an optional database migration is needed to enable some of them. Here are the details.
About that new database
In a blog post announcing the new features, the company explains that while it worked hard to maintain backwards compatibility between OmniFocus 3 and 4, some of the features announced today will require an update that moves the database to a new format.
Still, the company says that this migration is optional, and that “OmniFocus will only prompt you to migrate if it detects that all syncing copies of OmniFocus are compatible with the newer format.” The company also says that while some new features require this migration, that is not the case for all of them.
What’s new in OmniFocus v4.7
While some projects have hard kickoffs and deadlines, in which case, Defer Dates and Due Dates do the trick in OmniFocus, that may not be the case for all types of projects. That’s why OmniFocus v4.7 introduces Planned Dates, which are meant “for scheduling when you plan to work on an action, action group, or project.”
Here’s how Planned Dates work:
“Planned Dates are available everywhere you might have previously interacted with a Defer or Due Date, and they behave in much the same way. Items assigned to a project or group inherit Planned Dates set on parent items, although a child action can also have a Planned Date before or after their parents’ Planned Date. Items can be displayed on their Planned Date in Forecast, and items that aren’t completed on their scheduled Planned Date will persist in the “Past” section of Forecast. Planned Date-based rules are also a great addition to custom perspectives!”
This feature requires the database migration.
This is perhaps one of the most useful new features, depending on how you organize your workflow.
... continue reading