In Saga 1.3.1 the Phone Recognizer now has a dictionary of Area codes that the user can fill and then use to filter phones by area code.
...
In order to fix the problem just remove the Phone Recognizer and add it again. When adding it again it will be saved with the correct mapping in the index.
In Saga 1.3.3 the Phone Recognizer now supports area codes for US and UK. This means the area code dictionary now contains an additional column for country code and consequently the corresponding index and index mapping in Elasticsearch was modified to include that field. To update from a previous version the following needs to be done:
Geonames index mapping changed in Saga 1.3.1. The field "id" changed from Integer to Keyword. This makes resources not to load for geonames, rest handler not to load in SagaServer and therefore the recognizer won't be displayed in the UI.
In order to fix this issue you can remove the geonames index by using DELETE http request using Kibana or something like Postman. SO if using "saga" indices prefix you'll need to do a DELETE saga_geonames. Then in the UI add the recognizer back to the tag and reload the dictionary.
There is a new field in the Processing Units index. This index is used to stored persistent Processing Units. Therefore if you have a persistent processing unit in Saga 1.3 and then migrate to Saga 1.3.1+ you'll get an error in the log when starting Saga.
...