Scenario:
When retrieving DateTime values via the API, timestamps are now returned with millisecond precision. For example:
When retrieving DateTime values via the API, timestamps are now returned with millisecond precision. For example:
- In DocuWare 7.11, a stored DateTime may appear as: /Date(1751034782000)/
- In DocuWare 7.12, the same value is now presented as: /Date(1751036955137)/ (...137 is the millisecond identifier)
Solution:
Commencing in 7.12 and by product design, timestamps with millisecond precision are now returned. This improves the accuracy of scheduling, as well as auditing activities such as workflow tracking and index value changes.
Note: If you have integrations that only support whole-second precision, you may safely ignore the fractional (millisecond) portion of the timestamp. No additional configuration changes are required.
KBA applicable for both Cloud and On-premise Organizations
Commencing in 7.12 and by product design, timestamps with millisecond precision are now returned. This improves the accuracy of scheduling, as well as auditing activities such as workflow tracking and index value changes.
Note: If you have integrations that only support whole-second precision, you may safely ignore the fractional (millisecond) portion of the timestamp. No additional configuration changes are required.
KBA applicable for both Cloud and On-premise Organizations