Kenny Tang (WICLOUD CORPORATION)

Currently, the only out-of-the-box approach to identify a user’s last login time is to review the Audit Summary View and apply filters to locate the most recent “user access” entries.  This process is inefficient because the audit dataset can be very large and includes system-generated events, making it tedious to isolate true end-user logins.

It would be extremely helpful to have a more efficient, out-of-the-box option to identify each user’s most recent login. For example, adding a “Last login time” field on the systemuser table (automatically maintained by the platform) would make it much easier for administrators to quickly validate user activity without needing to look through audit logs.

After a recent Field Service update, the search behavior for requirements in the Schedule Board has changed. The filter now defaults to “Starts with” instead of the previous “Contains” behavior.

Although users can manually change the filter back to “Contains”, this setting is not persistent. After refreshing the requirements grid or navigating within the app, the filter automatically reverts to “Starts with.”

This change negatively impacts the user experience, as it introduces additional steps for users to locate the correct requirements during daily operations.

Restoring the previous “Contains” behavior or improving the persistence of the search filter would significantly enhance usability and improve the overall experience in the Schedule Board.