Comment 5 for bug 1667080
Revision history for this message
| Josh Stompro (u-launchpad-stompro-org) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I switched the text a call number feature over to flowroute sms yesterday, and it has some issues due to how the feature is designed, which I'm trying to figure out how to get around.
When the text an item is first loaded, it triggers the event before the phone number is specified, and then shows the output. The output for the flowroute sms is a json string, which doesn't seem all that friendly to show to the customer.
It also causes the reactor to try and send an invalid text message, one without a phone number to send to.
I think I'm going to go on the assumption that the user doesn't need to see what the text message is going to look like, both in the preview and once it is sent. And add some logic to not create an event if the phone number wasn't submitted to prevent extra events from being created.
Josh