Obzervr Cloud v41.80.3 - to preview on 07/03/2023 and production on 14/03/2023 includes the following updates:
The V1 Work API is a tool that allows software developers to create applications that can interact with Obzervr for managing work items.
One issue that was identified in this API was that it was not possible to update the Status Reason using a code (e.g. a keyword or short text string) instead of an ID (a unique numerical identifier).
The fix for this issue solves this problem, allowing developers to update the Status Reason using a code instead of an ID. This means that it will be easier and more convenient to work with the API, as developers can use simpler and more intuitive codes to update the Status Reason of work items.
When using Obzervr, there was a problem where if you tried to update a "Team" (a group of people who can access certain tasks) without adding or removing any locations, the system would start a process called "Team Mapping" unnecessarily.
The fix for this issue solves this problem, so that when updating a Team without any changes to its locations, the system will no longer start the Team Mapping process. This should mean, when syncing the Obzervr Capture app, the Team Mapping process should not be initiated.
- In Obzervr's new system for managing exceptions and feedback (such as errors or suggestions from users), there was a problem where it was not possible to load the lists of exceptions or feedback in a different "tenant" (a separate instance of the system for a different organization or group) from the one where they were originally created. The fix solves this issue.
- Solves an issue where changes were not saved in the Completed PDF section in the Tenant Settings.
Please sign in to leave a comment.