The 14.2 release of in4mo Building Claims includes feature improvements and bug fixes, as well as security, stability, and performance improvements. Below you will find a summary of the main changes.
To make task assignment more reliable, improvements have been made to how locations are handled in in4mo. When an address that is entered into the system can’t be confirmed by our current map provider Bing Maps, coordinates will not be defined for the case. This way we ensure that the location is not set in the wrong place, and distances between the damage site and the partner offices can be calculated more accurately.
Cases that are missing coordinates will have the red exclamation mark shown by the address, which indicates that the address could not be found exact by Bing Maps and needs to be validated manually.
This has an impact on both manual and automatic task assignment (through case creation rules), as well as integrations.
If a task in a case where the coordinates for the damage site can’t be verified is assigned manually, the recommended office list will be empty, and a notification explaining this will be shown.
If a task has been defined in case creation rules or integrations to be automatically assigned, the automatic assigning will not take place unless the system is confident that the location is correct. The grand log of the case will then show an explanation of why the automatic assignment did not happen: “Automatic task assignment is prevented due to inaccurate or missing geolocation.”
Previously the Last activity shown on the case list included all activities in the case except for chat messages. Now the sending of chat messages or internal notes will affect the latest activity timestamp, and the order in which cases are listed in the case view. The reading of chat messages will have no effect on the timestamp and will therefore not affect the order in the case view.