2.0 Release Notes
Public Release Date: March 12, 2025
The following is a list of what's new in Trimble Unity Maintain and Trimble Unity Permit 2.0.
Overall
- Trimble Unity Maintain and Permit have been updated to .NET 9. (15579)
- Plugins cannot be installed or removed in Trimble Unity. (15683, 15831)
- Domain administrators are the only users who can assign employees to a plugin. (16007)
- Security updates were made. (15943)
- The authorization token has been updated to JSON Web Token (JWT). Note that existing authorization tokens are no longer valid. If you have any integrations that use authorization tokens, they will need to be updated. (15653)
- Cookie settings have been updated. (15904)
Admin
- Changes made on the Contractor Setup and Contractors pages are tracked in the audit log. (15759, 15760)
- Action Logs has been renamed to GIS Errors for clarity. (15828)
- License names have been updated. (15612)
- Syntax validation and error code improvements have been added to the custom fee formula section. (15747)
- Bulk import and bulk export options have been added for notification conditions. (15748)
Respond
- Work orders can be opened from a Case Object query type's results and from a dashboard. (15578)
- On a work order or inspection, if a Submit To Crew is selected, the Submit To is automatically set to the crew lead. (15824)
- In the query results, counts for attachments, comments, and documents have been added for certain query types. (15669)
- The Data Source is no longer configured in the Report Designer. (16026)
API
- Security updates were made to the Attachments service. (15868)
- The following APIs have been added. (15898)
- CasePaymentRefund > SearchObject
- CaseTask > ScheduleInspection
- MessageBoard > GetListByUntilDate
- ScreenFlow > GetPAControlsByBusCaseId
- The following APIs have been optimized to enable fast and efficient database queries. (15808)
- CaseRelDocs > ByCaObjId
- CaseRelDocs > ByCaObjectIds
- A parameter has been removed from the AuthenticateTidToken API and two parameters have been added. (15879)
- Authentication > AuthenticateTidToken > TidToken (removed)
- Authentication > AuthenticateTidToken > AccessToken (added)
- Authentication > AuthenticateTidToken > IdToken (added)
Resolved Known Issues
The following is a list of resolved issues in Trimble Unity Maintain and Trimble Unity Permit [version number].
Overall
- Security updates needed to be made. (16288)
- Trimble Unity Maintain and Permit 2.1
- The core site crashed after syncing multiple comments to a task in the mobile application. (16079)
- Trimble Unity Maintain and Permit 2.1
- If a user logs in using Single Sign-on, then they are taken to the landing page. (16192)
- Trimble Unity Maintain and Permit 2.1
- Swedish special characters (åäö) upload as question marks in Style and Respond when a profile file was uploaded. (16154)
- Trimble Unity Maintain and Permit 3.0
Admin
- Field Validation map functions for conditions on events are not working. (16195)
- Trimble Unity Maintain and Permit 2.1
- The EquipmentCost value is misspelled in Field Validation. (16273)
- Trimble Unity Maintain and Permit 2.1
- ArrayAny and ArrayCount field validation functions were not working with _idx fields (for example, WorkOrders_idx). (16397)
- Trimble Unity Maintain and Permit 2.2
- When adding a condition, the Comments field was limited to 256 characters even though it should have been 2000. (16324)
- Trimble Unity Permit Admin 4.5
Respond
- Adding more than 27 assets to a case results in a GIS Alerts error. (16016)
- Trimble Unity Permit Respond 6.4
- Status change notifications are inadvertently sent upon case creation. (16011)
- Trimble Unity Permit 2.1
- When a child UID was entered during an Equipment Change Out replacement, the entered value did not get saved.(16208)
- Trimble Unity Maintain Respond 6.4, Trimble Unity Maintain and Permit 2.1
- The GIS event layer displays all fields, no matter how it is configured. (16152)
- Trimble Unity Maintain and Permit Respond 6.4
- The Report Designer displays an error message that doesn't outline the specific the problem. (16251)
- Trimble Unity Maintain and Permit 2.1
- When printing work activities, .docx print templates did not load. (16395)
- Trimble Unity Maintain and Permit 2.1
- The delete option for attachments only appeared when the case template included required or recommended attachment labels. (16325)
- Trimble Unity Permit Respond 6.6
- The Hide Codes in Respond setting in Admin caused inconsistent display behavior in Respond. Some permit panels still showed codes when the setting was enabled, and others incorrectly listed duplicate descriptions or just the codes when it was disabled. (15977)
- Trimble Unity Permit Respond 6.6
- GIS attachments could not be viewed or attached in Asset Details. (17089)
- Trimble Unity Maintain and Permit Respond 7.0
The following is a list of issues addressed in Trimble Unity Maintain and Trimble Unity Permit 2.0.
Overall
- The core site crashed after syncing multiple comments to a task in the mobile application. (16078)
Admin
- Notifications that included conditions using multiple tables or views did not work properly. (15712)
- After a service request template was cloned, if any fields were edited, the service request hierarchy was removed entirely. (15580)
- If the Inspection Template was changed on an MQA survey template, the Score Mapping panel appeared empty. (15610)
- When a MQA survey template was cloned, the Network Class fields were not copied to the new template. (15609)
- Email notifications configured to send when a comment was added to a service request or work order were sent for all templates. (15685)
Public Access
- An error occurred when opening an incomplete case if an existing case with a status of done had the same or next sequential CA_Object_ID in the WIP_CA_Object table. (15863)
Respond
- Geocoding during case intake did not populate map layers. (15709)
- The system did not send notifications when a case template configured to send a notification on task result status change was used. (15856, 16114)
- When a large number of assets with multiple map layers was added to a case, each asset's map layer was populated in the Map Layers panel. (15430)