SMS ADLS the dev versions are different.
Tim
I just noticed that the SMS archetypes are that are being built inside the dev version are actually not the same ones that we end up distributing the dev version include a senderID node yet the build we distribute is missing them.
Is in the build yet the distribution is missing the senderID node.
Re: SMS ADLS the dev versions are different.
Also I used the dev ADL that includes the SENDER ID node and the updated
message field that adds FROM:SenderID
It doesnt seem to take notice of it..
I updated the ADL - do I need to recreate a new entry to use it or will it update my exisiting one to use the new concat.
Re: SMS ADLS the dev versions are different.
Created a new entity SMS and it works with the new ADL. Just need to distribute it properly now
Re: SMS ADLS the dev versions are different.
See https://openvpms.atlassian.net/browse/OVPMS-1442
Re: SMS ADLS the dev versions are different.
Understood,
but the new adl isnt even in the 1.7 distribution... after archloading with the new distrib my current clickatell adl was still the old one with no sender id.
Maybe the best solution is to remove ALL the specific SMS adls from the distribution and place them in an optional ADL folder that isnt automatically uploaded on implementation. This means the admin will need to upload the correct adl for the users particular implementation.
either that or...
Given that uploading the new ADL is backward compatible I would have thought it sensible to do so..the upgrade notes should specify that administrators need to delete any old entities and create new ones to utilize the new feature...that old entities will not use the sender ID field even though it appears in the web interface.
No one is going to question why it isnt working (like I have) unless they are specifically chasing the sender ID feature. In which case they should either A read the CSH (which should mention this) or B come to the forums.
Just my thoughts.
Re: SMS ADLS the dev versions are different.
The Clickatell senderId change has not been formally released yet. Its scheduled to go in 1.7.1.
To make use of the change you need to create a new Clickatell configuration. This is because the textExpression node has an xpath expression that is initialised from the archetype.
I've updated http://www.openvpms.org/documentation/csh/1.7/sms/config/clickatell to include a note about the Sender ID.