Topics:

Auto-Accept User Settings

Updated "Payment Pending" Messaging

Enforcement Report Updates

California State Report Enhancement

Test Report Deletion Improvement

Resolved Issues

Auto Accept is an optional feature that enables test reports and surveys to be automatically accepted based on predefined criteria.

You can configure Auto Accept settings to streamline your workflow by reducing the number of manual approvals required, minimizing administrative tasks, and decreasing notification volume. Unique rules can be applied separately for test reports and surveys to meet your specific compliance needs.

To view your Auto Accept settings, navigate to the Settings tab and click the “+” to expand the Compliance Reports Settings and Rules section.

Four settings that impact whether a test report can be auto accepted:

SP Org where Organization level auto accept settings for Test Reports and Surveys are both disabled.

Tester User where Organization level auto accept settings for Test Reports and Surveys are both disabled.

SP Org is enabled for auto accept for Test Reports because Organization level auto accept setting for Test Reports is enabled. Organization level setting for auto accept for Surveys is disabled.

Tester User is not enabled for auto accept for Test Reports because while Organization level auto accept for Test Reports is enabled, the Organization level ‘default auto accept users’ is set to disabled. All users start as disabled and have to be specifically enabled.

In this case, Organization level auto accept setting is enabled and ‘default user auto accept’ is set to enabled.

Settings will be displayed separately for Test Reports and Surveys. In this case, because the Organization level auto accept setting for Test Reports is enabled, the SP Org auto accept for Test Reports is enabled by default. At the same time, Organization level auto accept setting for Surveys is disabled.

Similarly, Organization level auto accept setting for Surveys is disabled and Organization level auto accept setting for Test Reports is enabled. For this tester to be enabled by default, the ‘default user auto accept’ is also enabled.

The end result (Tester is enabled for auto accept for Test Reports) is due to this user being specifically enabled for Test Report auto accept when the ‘default user auto accept’ is disabled. In this case the Organization level auto accept for Test Reports does have to be enabled, which automatically means the SP Org is enabled by default.

Lastly, this scenario shows what happens if Organization level auto accept for Test Reports is enabled and ‘default user auto accept’ is enabled. The user would have to be specifically disabled for auto accept for Test Repots in order to not be eligible.

*Click Image to Enlarge

Problem:
The test reports page previously displayed the total number of pending payments for all Service Provider companies that a Service Provider User was connected to. However, when users clicked to make a payment, the view was automatically filtered to show only the test reports tied to them as the tester. This caused confusion, as some users thought reports were missing and didn’t always realize they needed to check the filters.

Solution:
We have updated the wording on the test reports page to clarify that the initial pending payment count includes all Service Provider companies. This change helps users better understand the filtering process and reduces confusion.

We've introduced new reporting functionality to enhance enforcement processes. This update provides improved visibility into compliance data, making it easier to track violations and take action efficiently.

By default, this report will display assemblies with a compliance expiration date that has passed or is not assigned.

By default, this report will display locations with a survey expiration date that has passed or is not assigned.

By default, this report will display assemblies with a last accepted test result of "Fail."

By default, this report will display locations where the last accepted survey result was "Fail."

We have updated the California State Report to now include PVB assembly types. This change has been confirmed with the state and several customers to ensure accuracy and compliance. The update applies to all numbers that are not air gap only—meaning RP, DC, and now PVB assemblies are included in the report.

Problem:
The bar graph for the "Assemblies Next Test Date" report was not displaying data for months 11 and 12 in the rolling bar chart. While the chart updated over time, the last two months remained blank, even though assemblies were scheduled for testing during those months.

Solution:
We have fixed the issue so that months 11 and 12 now correctly display the scheduled assemblies in the rolling bar chart. This ensures that all upcoming test dates are accurately represented, improving visibility and planning.

Problem:
Users encountered an error message when attempting to load the "Incomplete Contacts List," preventing them from accessing and managing incomplete contact records.

Solution:
We have resolved the issue causing the error, ensuring that the "Incomplete Contacts List" now loads correctly. Users can now view and manage incomplete contacts without interruption.