Snap Send and Solve Integration - Release Notes

Added a fix for scenarios where the error below was encountered during property linking: “The Property Type for this Property is not valid for linking to this module”

The solution will now automatically fall back to the configured default property key when this error occurs, preventing processing failures.

Fixed an issue where the solution could crash when processing non-SMTP email addresses.

Enhanced solution stability and error handling during property association and email processing workflows.

As Microsoft is deprecating SMTP auth for sending emails, we have updated the solution to support sending emails through the Microsoft Graph API using Azure App Registration. This change ensures continued support for email functionality well into the future.

Some clients require that requests are only created when there is a one-to-one mapping between SSS incident types and internal pathway request types. We have added support for this configuration.

If no direct mapping exists and no generic request type is configured, no request will be created.

The Daily Report has been enhanced to include:

• Property Address
• Longitude (LONG)
• Latitude (LAT)

This provides richer context for reporting and analysis.

A new configurable feature now allows councils to specify a note type in the mapping table.
The solution will:

• Read the most recent note of that type on a request, and
• Transmit it to Snapper.

Councils can now control whether Snapper notifications are sent based on request type. This feature allows more granular control of outgoing notifications and reduces unnecessary messaging where not required.

In previous versions, NAR record was searched based on First Name Surname and Email address. This was causing issues with mapping to correct NAR record. An improvement is implemented in this version where NAR record is search and mapped based on Full name and Email address received from SSS.

Previous versions did not track changes to request status within the integration. Version 2.8.0 introduces full auditing of status changes to improve traceability and reporting on state transitions.

Intermittent object reference exceptions that occurred in certain scenarios have been fixed.

An intermittent issue where database connections would close unexpectedly has been resolved, improving stability and reliability.

When enabled, the solution will automatically match and link the relevant Street/Suburb record from Pathway to a request. If no match is found, a nominated generic Street/Suburb will be linked — ensuring every request is properly recorded.

Now you can configure the solution to map questions from Snap Send and Solve to Pathway questionnaires. When enabled, the system will populate answers provided via SSS directly into the Pathway request.

You now have granular control over which request types use the Property, NAR, Street/Suburb and Questionnaire mapping features. Enable these features selectively based on your operational needs.

Previously, the solution sent multiple email alerts for the same failure or error, which could lead to inbox clutter. This has been improved so that the solution now sends a single email notification per issue, while continuing to record full details in the log file for reference.

All configuration settings previously stored in files have been migrated to the database, enabling centralized management and easier updates without code changes.

The daily report format has transitioned from CSV to PDF for improved readability and professional presentation. The PDF includes tabular summaries and visual data representations.

A bar chart summarizing the number of requests per request type is now generated daily. This chart offers a quick visual overview of request distribution.

The daily email now includes the request type bar chart embedded within the message body for immediate visibility. The full PDF report remains attached for detailed review.

The system now performs sentiment analysis on customer-submitted notes from SSS (Snap Send Solve). Each request is tagged as Positive, Neutral, or Negative based on the tone and language used.

Requests with identified Negative Sentiment can trigger automatic alerts:

• Notifications sent directly to a Microsoft Teams channel.
• Optional email alerts to designated recipients.

Additional Data/Questions from SSS reports are now stored in notes.

There are two additional attributes introduced in this version. These attributes allow Council to nominate different reference types to store Customer Given Name and Surname.

AlertEmailRecipient attribute can be configured to accept comma separate list of multiple email addresses.

In certain cases, mandatory fields were found to contain NULL values in reports received from SSS. This was causing an issue when creating Pathway request. This problem has been resolved by introducing measures to validate against NULL values, thereby definitively resolving the problem.

Error "The remote server returned an unexpected response: (413) Request Entity Too Large" was returned for attachments and as a result solution was creating duplicate requests. The fix now records the error and avoids creating duplicate request in Pathway.

A new attribute offers Councils the flexibility to deactivate the Property module linking as needed. This enhancement empowers administrators with increased control over the system's behavior in response to their specific requirements.

A new attribute that can be customized by Council to deactivate the linking functionality of the Name module. This enhancement empowers administrators with increased control over the system's behavior in response to their specific requirements