Article Details
| Id: | 12020 |
| Product: | finPOWER Connect |
| Type: | NEW |
| Version: | 2.01.01 |
| Opened: | 30/05/2014 |
| Closed: | 30/06/2014 |
| Released: | 31/07/2014 |
| Job: | J013360 |
High Importance |
|
Breaking Change |
|
Business layer functionality to return Client Phone Numbers now validates that the Contact Method looks like a Phone Number
Using one of the following methods of finClientContactMethods now validates that the Contact Method value is a Phone Number:
- GetCurrentPhone
- GetCurrentPhoneHome
- GetCurrentPhoneWork
- GetCurrentPhoneSms (new method added for consistency)
These methods have also been updated to only include what appear to be valid Phone Numbers:
- finClientFunctions.GetContactMethodsListSms
- finAccountFunctions.GetContactMethodsListSms
Any Contact Method with a value that is not a Phone Number (or does not look like a valid Phone Number), e.g., 'NA' will not be included.
This functionality is used throughout finPOWER Connect, e.g., when sending an SMS Document (via Report Explorer, Workflows, Send SMS wizard etc).
High Importance
Breaking Change