Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
preferences:frontlinesms [2017/07/18 22:33] – [Error Messages and Notifications] rozanna | preferences:frontlinesms [2023/09/02 00:53] (current) – [16.08. FrontlineSMS] Mark Glover | ||
---|---|---|---|
Line 1: | Line 1: | ||
{{indexmenu_n> | {{indexmenu_n> | ||
- | ===== FrontlineSMS ===== | + | ====== 16.08. |
- | + | <WRAP center round important 90%> | |
+ | * The preferences described here (accessed through **File > Preferences...**) apply to all stores on an mSupply server. | ||
+ | * In a [[synchronisation: | ||
+ | * There are some settings that are 'per store' - refer [[other_stuff: | ||
+ | </ | ||
If you use FrontlineSMS for sending information to mSupply via SMS messages (using mobile phones), this is the page where you enter all the settings. | If you use FrontlineSMS for sending information to mSupply via SMS messages (using mobile phones), this is the page where you enter all the settings. | ||
Line 10: | Line 13: | ||
== We use FrontlineSMS: | == We use FrontlineSMS: | ||
- | |||
Checking this makes mSupply periodically check the FrontlineSMS database for messages that have been sent to mSupply. If this checkbox is left unchecked, mSupply ignores all the settings on this page and will not check the FrontlineSMS database for new messages. | Checking this makes mSupply periodically check the FrontlineSMS database for messages that have been sent to mSupply. If this checkbox is left unchecked, mSupply ignores all the settings on this page and will not check the FrontlineSMS database for new messages. | ||
==== FrontlineSMS database (MySQL) settings ==== | ==== FrontlineSMS database (MySQL) settings ==== | ||
- | |||
To use FrontlineSMS with mSupply, FrontlineSMS must be configured with a MySQL database. In this section you tell mSupply the details of this database to enable it to connect to it and retrieve new messages. | To use FrontlineSMS with mSupply, FrontlineSMS must be configured with a MySQL database. In this section you tell mSupply the details of this database to enable it to connect to it and retrieve new messages. | ||
Line 47: | Line 48: | ||
This is what mSupply looks for at the very beginning of an SMS message received by FrontlineSMS to identify it as one that it must process. Can be made up of any alphanumeric characters. Keep it short and unique - not something that will appear at the beginning of any SMS messages not intended for mSupply. | This is what mSupply looks for at the very beginning of an SMS message received by FrontlineSMS to identify it as one that it must process. Can be made up of any alphanumeric characters. Keep it short and unique - not something that will appear at the beginning of any SMS messages not intended for mSupply. | ||
- | ==== Error Messages | + | |
+ | ==== Error messages | ||
Because the process is otherwise silent, mSupply needs to notify users when a new message has been processed or if errors occur in the process (e.g. a message is missing some information). mSupply will email such error messages and notifications to the users ticked in the list in this section. The list contains all users in the system and you must select at least one of them. | Because the process is otherwise silent, mSupply needs to notify users when a new message has been processed or if errors occur in the process (e.g. a message is missing some information). mSupply will email such error messages and notifications to the users ticked in the list in this section. The list contains all users in the system and you must select at least one of them. | ||
Line 53: | Line 55: | ||
// Previous: | // Previous: | ||
+ | \\ | ||
+ | \\ | ||
+ | | // Previous: | ||
---- struct data ---- | ---- struct data ---- | ||
+ | pagestatus.status | ||
---- | ---- | ||