2025 release notes

V2.128.0 (01/Dec/25)

IMPROVED Various performance improvements were made to creating assets as part of ongoing performance improvement efforts.

AMCS Field Worker

FIXED Addressed an issue where loading spinners were not consistently showing on the Login page and Workflow Report Editor were not always showing. These will now show normally to clearly show the app is loading.

FIXED Addressed an issue where users were not able to enable permissions in the iOS and Android versions of the app. This applies to both adding photos to workflows and the QR Code Scanner.

NOTE: Due to an issue in the verification process, the latest version of AMCS Field Worker was not published in the Google Play and Apple App stores on our normal release schedule. We’re working on resolving these issues as soon as possible.

V2.127.0 (17/Nov/25)

FIXED When saving a workflow report for any In Progress work order, one-shot triggers were not evaluating correctly if that trigger’s condition had already been met on saving to In Progress. One-shot triggers will now only account for conditions when saving to Complete rather than In Progress.

FIXED In some scenarios, hitting the Enter key on a field in the Workflow Report Editor would prevent expressions from evaluating correctly. Hitting Enter will no long affect expression evaluation.

FIXED When creating or editing a custom asset filter, not available users were showing when assigning users to a filter. All users available will now show correctly.

AMCS Field Worker

IMPROVED In the Workflow Report Editor, longer workflow fields were not showing the full text in that field’s label. The full field’s title will now show.

FIXED When using AMCS Field Worker on Android, the Back button was sometimes causing users to unexpectedly exit the application. This will now navigate users appropriately.

V2.126.0 (03/Nov/25)

IMPROVED Various performance improvements were made to finding and viewing assets from the Map as part of ongoing performance improvement efforts. These changes specifically improve performance on panning and zooming in or out on the map.

AMCS Field Worker

IMPROVED Behavior around the Can Only Perform Workflows If Stakeholder security right have been implemented in AMCS Field Worker. Users with this right will not be able to complete work unless they are added as a workflow stakeholder, consistent with the core Utility Cloud application.

FIXED When completing any workflows configured with compare and confirm enabled, the compare and confirm drawer was not consistently showing the full width of a user’s screen on mobile devices. This will now show the width of the screen.

V2.125.0 (20/Oct/25)

FIXED When editing a route, adding or removing a workflow was preventing a user from saving their changes without updating a routes schedule. These changes will no longer prompt changing a route’s schedule.

FIXED When adding a work order trigger to an asset class or workflow class, the available to contractors flag was not showing appropriately. This field now appears normally.

FIXED From the Asset Editor page, header fields set with visibility conditionals were not always showing or hiding correctly. Header fields will now show or hide the same as other asset attributes.

FIXED In some scenarios, saving an account from the Account Details would show an error even though the account saved normally. These error messages no longer appear on successful saves.

FIXED On the Print Queues page, scrolling would sometimes bring users to the bottom of their search results rather than scrolling normally. Scrolling now behaves normally on the Print Queues page.

AMCS Field Worker

FIXED When opening any In Progress work order, that work order’s workflow report was loading offline data from a user’s most recent sync rather than the latest details online. In Progress work orders will now load the latest details online first if able.

V2.124.0 (06/Oct/25)

IMPROVED Performance improvements were made to finding and viewing assets generally as part of ongoing performance improvement efforts. For users integrating with APIs, these changes will be relevant to the Get Assets and Get Assets by Search Term endpoints.

FIXED When viewing a route, users were unable to sort routes by sequence. This sorting now works normally.

FIXED When adding asset attributes to an asset class, the option to flag a field as available to contractors was not visible until that field was first saved. Available to contractors will now show immediately when creating new asset attributes.

AMCS Field Worker

NEW Users are now able to search for assets by their asset tag in AMCS Field Worker using the new QR Code Scanner page.

IMPROVED For contractor users using the Work Order Lookup tool, that search was updated to search on selecting the search icon instead of on keystroke.

FIXED In some scenarios, the close icon on popup modals was not closing those modals. These modals will now close normally.

FIXED When submitting an In Progress work order as a draft, those work orders were sometimes remaining in the In Progress status despite being completed. These work orders will now correctly show as Complete.

Excel Add-in

IMPROVED When downloading and installing the Excel add-in, the download link in use was using http instead of https. The add-in will now use https.

V2.123.0 (22/Sep/25)

IMPROVED Performance improvements were made to finding and viewing assets from the Map as part of ongoing performance improvement efforts.

IMPROVED Updates were made to the /assets/getassets API to support additional filtering using advanced search criteria.

AMCS Field Worker

IMPROVED Various updates to styling throughout the app.

V2.122.0 (08/Sep/25)

NEW Utility Cloud now supports creating new contractor users with limited access to Utility Cloud through the AMCS Field Worker application. Additionally, work orders and attributes can be flagged as available to contractors for use with AMCS Field Worker. You can learn more about contractor users and the Field Worker contractor portal here.

IMPROVED Various error pages across Utility Cloud have been updated to use a new, standardized error page. This is part of a larger effort to update older pages across Utility Cloud, with more updates coming soon.

IMPROVED In certain scenarios, Esri subscriptions were failing to sync with an InProgress error due to Esri processing changes on a layer. The error log now clearly indicates this error is coming from Esri instead of Utility Cloud.

IMPROVED Performance improvements were made to creating and editing an asset as part of ongoing performance improvement efforts.

FIXED In certain scenarios, Google reporting was receiving an error when a Google account was linked to an account in Utility Cloud without having the proper authorization for Google reporting. These scenarios will now send a clearer error and prompt users to relink their Google account.

FIXED In certain scenarios, advanced search criteria was not persisted when returning to the Asset Search from Asset Details. Search criteria should now persist consistently.

FIXED When exporting workflow reports from the Workflow Class Builder page, some workflow reports were not exporting correctly due to an error caused by importing workflow reports without an associated asset. Importing workflow reports without an asset will now cause an error, and exporting will now export all reports consistently despite the error.

FIXED When creating or editing an Esri subscription, feature servers were sometime showing as duplicated. These duplicates will no longer appear.

AMCS Field Worker

NEW AMCS Field Worker now supports contractor users completing work flagged as available to contractors in Utility Cloud, either through work queues or the new Work Order Lookup tool for contractors. You can learn more about contractor users and the Field Worker contractor portal here.

IMPROVED Expressions in AMCS Field Worker were evaluating on keystroke and, to improve performance with larger workflows, will now evaluate on leaving a field.

V2.121.0 (25/Aug/25)

IMPROVED Performance improvements were made to creating and editing a work order as part of ongoing performance improvement efforts.

FIXED After editing an asset class to remove a field’s visibility conditions, previously-hidden fields were still hidden when exporting instead of showing after that change. Fields updated this way will now be visible when exporting assets.

V2.120.0 (11/Aug/25)

FIXED The Email Log page was sometimes timing out when trying to load results on visiting the page. Results now load normally.

FIXED When updating a route by adding an asset or new workflow, that route was recreating all new work orders for every asset and workflow rather than only creating work orders for the new assets and work orders. Routes now will only add the new work orders when editing rather than recreating the entire route.

Field Worker Application

NEW The Field Worker Application is now available as an installable application under its new name, AMCS Field Worker. It can be found in the Apple App Store here and the Google Play Store here.

IMPROVED Improvements were made to improve retrieving updates through when logging in after a new version has been published.

V2.119.0 (28/Jul/25)

IMPROVED Previously, the asset attachment file tree only displayed up to 1000 files and/or attachments in the tree, and any additional files/folders would not display even if they uploaded successfully. This limit was removed and now all files/folders will display. To accommodate for larger numbers of files/folders, the root folder now defaults to closed.

IMPROVED Made additional changes to improve asset-related performance. Performance changes in assets and other areas will continue to be an ongoing effort.

V2.118.0 (14/Jul/25)

IMPROVED Made changes to improve performance around loading assets and related areas relying on asset data (such as work orders) across the application.

IMPROVED Removed internal errors from error emails relating to Esri syncs.

FIXED In some scenarios, work orders that are a part of a route were not showing in the results for a work order advanced search when searching specifically for work orders in any route. These work orders will now show in results as expected.

FIXED In some scenarios, analytics were showing inconsistent dates between the Analytics page and that same analytic on the Landing Page. Both now show consistent dates.

FIXED When editing a route set to reoccur by completed date, users were prevented from setting start date before the current date. Users are no longer prevented from selecting a date in the past for routes set to reoccur by complete date.

FIXED When adding a relationship between a parent and child asset through the Relationships panel on the Asset Details page, the child asset’s last modified date was not being updated and that same asset was not receiving an audit. Both will now update appropriately.

FIXED Users were not automatically being deactivating based on inactivity and will now deactivate normally.

V2.117.0 (30/Jun/25)

IMPROVED In certain scenarios, when rotating an image in a photo field when editing an asset or saving a workflow report, that image’s dimensions were not retained after rotating. Images will now consistently retain their dimensions.

Field Worker Application

FIXED If a work item that was in a user’s offline work queue and then no longer in that queue after saved offline, then that work item was no longer loading properly. Work items will now load consistently if they are not part of a work queue.

V2.116.0 (16/Jun/25)

IMPROVED In some scenarios, the Email Log was was encountering errors without informing users. These errors will now be more prominently displayed.

FIXED When changing time zones on a user, audits were not correctly displaying the new time zone. These audits will now more accurately display the newly-selected time zone.

Field Worker Application

FIXED Addressed an issue where drawing a signature in a workflow’s signature field was not correctly following where a user drew in the form.

V2.115.0 (02/Jun/25)

IMPROVED Implemented additional CDN improvements across the app to help improve performance.

FIXED In certain scenarios, users were encountering an unexpected error on redirecting instead of the page loading normally. Redirection in these scenarios will now load the page normally.

FIXED When attempting to update an asset through a trigger, text fields were not mapping properly to multiple choice fields, even if the text value would be a valid option for the multiple choice field. Multiple choice fields will not update normally if the provided text value is valid for that field.

V2.114.0 (19/May/25)

FIXED In some scenarios when creating a route or work orders, users' time zone settings were not being applied correctly for Start Dates. Start Date will now always match a user’s time zone settings.

V2.113.0 (05/May/25)

IMPROVED Made general performance improvements to the asset import.

FIXED In certain scenarios, analytic charts on the Landing Page and the Analytics pages were not loading properly. These charts will now populate normally.

FIXED When populating autogenerated asset IDs, the next autogenerated ID was not always populating correctly when encountering a large number of IDs already in use. Autogenerated IDs will now generate without issue when encountering an ID already in use.

V2.112.0 (21/Apr/25)

FIXED When exporting list definitions, some special characters were causing that export to fail. List definitions will now export successfully with special characters.

V2.110.0 (07/Apr/25)

IMPROVED Implemented additional CDN improvements across the app to help improve performance.

FIXED When searching for assets and navigating to an asset from the search results sidebar on the Asset Details page, assets were not loading properly after navigating to the first result. The Asset Details page will now load normally in this scenario.

FIXED When creating a work order from the Asset Search or Asset Details page, the Create Work Order modal was not loading properly after creating a work order successfully and attempting to create additional work orders. This is now loading normally after creating a work order.

FIXED In certain scenarios, reoccurring work orders in a route where no reoccurring correctly, namely :

• When editing the scheduling details of a route, some work orders were not being created correctly if the current work order had been completed before a new occurrence was created.

• When removing an asset from a route, some work orders would continue to reoccur as if the asset were still a part of that route.

In each scenario, routes will now reoccur normally.

Field Worker Application

FIXED Resource costs were not always validating correctly on loading the Workflow Report Editor and will now validate normally.

V2.110.0 (24/Mar/25)

NEW The support phone number has been updated from 1 (800) 962 9264, extension 3 to 1 (800) 962 9264, extension 1, and this has been updated across the app to reflect the new number.

Field Worker Application

FIXED Addressed an error when attempting to log in to a single tenant environment.

V2.109.0 (10/Mar/25)

FIXED In certain scenarios when uploading an image to a photo field in the Workflow Report Editor, once an image was removed, users were no longer able to upload a new image. Users can now upload a new image consistently after removing a previous image.

FIXED In certain scenarios when configuring a number field on the Workflow Report Editor, a user’s selection for the String Literal For Reports field was not saving correctly. This field will now save correctly consistently.

FIXED When logging in using Edge as a browser, users were incorrectly being audited as using Chrome instead. Audits will now correctly identify if a user is using Edge or Chrome for their browser.

V2.108.0 (24/Feb/25)

IMPROVED Implemented general CDN improvements across the app to help improve performance.

FIXED Inactive workflows were showing in the Workflow Compliance Report page. Now, only active workflows will show.

FIXED In certain scenarios when syncing an Esri subscription, asset data was failing to send to ArcGIS due to missing z-values on features. Missing z-values will now no longer cause an Esri subscription to fail to sync with ArcGIS.

FIXED In certain scenarios when editing a reoccurring route, future reoccurring work orders were not created with the correct start date. Various improvements were implemented to ensure work orders are created with the correct start date.

Field Worker Application

FIXED Addressed an issue where previous workflow report data was not being retrieved correctly while offline.

FIXED Addressed an issue where resource tracking data was not loading correctly for in progress workflow reports.

V2.107.0 (10/Feb/25)

NEW Implemented and improved support for Power BI integrations on single tenant servers.

IMPROVED Implemented changes to improve performance on viewing and saving an asset throughout the application, as well as adding or editing an asset via the asset import.

IMPROVED Implemented improvements throughout the application to better handle any unexpected job failures.

Field Worker Application

NEW Implemented whitelabeling capabilities to match current-day Utility Cloud whitelabeling functionality.

NEW Added current-day compare and confirm functionality to the FWA Workflow Report Editor.

IMPROVED Made improvements to how user information is retrieved throughout the application.

V2.106.0 (27/Jan/25)

FIXED In certain scenarios, users were able to save a workflow with duplicated workflow fields. Users will no longer be able to save workflows in such a way that duplicate fields are entered.

FIXED For some users, when editing a work queue, a work queue’s criteria was not loading correctly. This criteria will now load correctly consistently for all users.

Field Worker Application

FIXED When a numeric expression evaluated so that the result were 0, that value was instead saving as null. Expressions will now evaluate correctly to 0.

V2.105.0 (13/Jan/25)

IMPROVED When adding a trigger to a workflow or asset class from the Workflow Class Builder or Asset Class Builder, triggers will now default to one-shot.

FIXED When editing an asset’s location from the Asset Editor, users were not able to enter coordinates for a point on a linear asset. Users can now enter these coordinates normally.

Field Worker Application

FIXED Users were not able to rotate images added to photo fields and now are able to rotate normally.

Related Articles