| Id: | 12430 |
| Product: | finPOWER Connect |
| Type: | FIX |
| Version: | 2.02.03 |
| Opened: | 18/11/2014 |
| Closed: | 18/11/2014 |
| Released: | 04/12/2014 |
| Job: | J014499 |
SMS; fixes and enhancements to auditing
Several fixes and enhancements have been made to SMS messaging auditing.
Note, there is no guarantee that a successful SMS within finPOWER Connect ever made it to the destination handset. However, these changes should make it easier to reconcile and audit charges made for SMS messages.
ClickSend (Intelligent Technologies)
If the SMS failed to send, e.g. the credentials were incorrect, the audit logs showed the SMS as being successful - but with failed and success counts of 0.
If multiple SMS recipients and no successfully messages, i.e. all failures, the message returned was "Failed to send to all Recipients". This has been updated to "Failed to send to any Recipients".
If the SMS failed to send, the Response text was not saved on the ISServiceLog record. The Response is now always saved, if a response is received. Note, the Response can include error information.
TxTStream Australia/ New Zealand (.NET V2 interface)
The "SuccessCount" is now saved on the ISAuditLog table - being the number of recipients of the message.
The full Message including the "Reply Name" and colon is now saved in the ISServiceLog record.
The Request version has been updated to version 2.00 to denote the change in information stored for the message.
Note, unlike the other two services this service does not immediately fail to send, therefore it will not return errors such as the destination mobile phone number being invalid.
TxTStream Australia/ New Zealand (XML over HTTP interface)
If the SMS failed to send, e.g. the credentials were incorrect, the audit logs showed the SMS as being successful - but with failed and success counts of 0.
If multiple SMS recipients and no successfully messages, i.e. all failures, the message returned was "Failed to send to all Recipients". This has been updated to "Failed to send to any Recipients".
If the SMS failed to send, the Response text was not saved on the ISServiceLog record. The Response is now always saved, if a response is received. Note, the Response can include error information.
The full Message including the "From Name" and colon is now saved in the ISServiceLog record.
The Request version has been updated to version 2.00 to denote the change in information stored for the message.