We're looking at adding a new feature to our solution where we can SMS staff with job details. The idea was to have a pop up window which displays a 'To' field and a 'Message' field. This layout is run by a temp table (sms_table) which will get cleared once the message(s) have been sent. They're going to be sent through email so all copies of the message will be stored in the email client.
So, I have a portal the shows jobs which, when clicked, builds the message part up. I worked out a nifty counter (proud of this
My issue is the address field. I don't know how I should go about setting it up. What I was thinking is having a list of staff, that, again you could click and it would build the address field like the message field. Separating the addresses with the appropriate separator (i.e. comma). My issue is, if you want to remove an address, it'll be a bit fiddly to highlight the address and delete. I was planning on having the selectable list "dwindling". This would cause problems if the address field was simply a text field.
Then I thought I could make the address field a portal, so it would just list all the addresses. Dwindling lists between portals would work how they should. The problem is, I don't know how to relate this to the message part. If I have a portal for the address field, I will have 1 record for every address. At the moment, the sms_table is set up to have only 1 record; To and Message. The To field can have multiple addresses, and the message field just has the message the same for everyone. Using the portal setup, each record will have their own address and the message repeated for every record. I suppose this is fine since it's a temp table and will be cleared but doesn't seem the best way.
The simple way would be to leave everything as it is, build the To field from clicking on the staff list but not have the staff list dwindling. Simple, but not very flash
Any ideas on how I should set it up?


































