We are deploying the following enhancements to Daptiv on May 20, 2022. This post is designed to help you understand how new and enhanced features can improve your Daptiv experience, and to guide you in making decisions about how to configure those features (if applicable). To facilitate training and testing ahead of this release, the features below will be deployed in Sandbox environments on Monday, May 16, 2022. The next Daptiv Release is June 10, 2022.
For detailed information about these and all Daptiv Features, see the Daptiv Online Help.
In addition to the fixes below, this release contains various background improvements that lay the groundwork for future enhancements. They should not have an impact on your current Daptiv experience.
In June 2022, the Daptiv release cadence will shift to being once monthly, on every second Friday of the month. This will bring Daptiv in line with monthly cadence used by other Planview products.
DeskDocs and Outlook Integration Disabled
As we announced in March, DeskDocs and Outlook Integration have been removed. Unfortunately, there is no readily available substitute for our Outlook Integration. However, Daptiv has an excellent alternative to DeskDocs in the drag and drop functionality in the Documents app. There, you can simply and quickly drag and drop documents into any project.
Timesheet totals update in real-time
Timesheets totals now automatically update daily totals in real-time as users enter values in the timesheet. This gives users a running total of the values assigned to each day before they save their changes.
Allocation Hours rounded down in Reports
We fixed an issue where allocation hours were being rounded down rather than being displayed with the correct number of decimal places. This no longer happens and allocations hours are displayed correctly in reports.
Hide Not Started Workspaces Filter applied incorrectly
When the Hide Not Started Workspaces filter is applied to a timesheet, it continues to hide In Progress workspaces if they are set to track time at the workspace level. Now, the filter correctly displays all In Progress workspaces.
OData connection failed to connect in reporting tool
The OData Connection would fail under the following conditions:
If there were hidden fields in the data set, resulting in a mismatch between visible fields and the query
If the data set had multiple queries joined together
These issues no longer block the OData connection.