Differences

This shows you the differences between two versions of the page.

--- preferences:frontlinesms [2013/02/07 03:01] – [FrontlineSMS] hayley
+++ preferences:frontlinesms [2023/09/02 00:53] (current) – [16.08. FrontlineSMS] Mark Glover
@@ Line 1: / Line 1: @@
-===== FrontlineSMS =====
+{{indexmenu_n>80}}
-{{entry>55.Preferences/22.FrontlineSMS|*}}
+====== 16.08. FrontlineSMS ======
+<WRAP center round important 90%>
+  * The preferences described here (accessed through **File > Preferences...**) apply to all stores on an mSupply server.
+  * In a [[synchronisation:introduction|synced system]] there will be multiple 'sync satellites' and these settings can be different on each sync satellite.
+  * There are some settings that are 'per store' - refer [[other_stuff:virtual_stores#the_preferences_tab|Store preferences]], and store preferences can be different for each store on an mSupply server.
+</WRAP>
 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 9: / Line 13: @@
 == 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.
 ==== 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.
-**Server**: The name of the server hosting the FrontlineSMS database. You can enter the server's name e.g. myserver.mydomain or its IP address.
+== Server: ==
+The name of the server hosting the FrontlineSMS database. You can enter the server's name e.g. myserver.mydomain or its IP address.
-**Database name**: The name of the FrontlineSMS database. This is the name it was given when it was created in MySQL.
+== Database name: ==
+The name of the FrontlineSMS database. This is the name it was given when it was created in MySQL.
-**User**: The username that mSupply will use to log into this database.
+== User: ==
+The username that mSupply will use to log into this database.
-**Password**: The password that goes with the username above.
+== Password: ==
+The password that goes with the username above.
-**Port**: The port that the database is served at on the host. If you leave this blank, mSupply will set it to the default port used by MySQL (3306).
+== Port: ==
+The port that the database is served at on the host. If you leave this blank, mSupply will set it to the default port used by MySQL (3306).
-**Test Connection Button**: This button will test the connection to the FrontlineSMS database using the settings above. You should click it after you've entered all the settings or when you change any of them. It will tell you whether the settings allowed mSupply to connect to the database.
+== Test Connection Button: ==
+This button will test the connection to the FrontlineSMS database using the settings above. You should click it after you've entered all the settings or when you change any of them. It will tell you whether the settings allowed mSupply to connect to the database.
+<WRAP center round important 60%>
+If a connection cannot be made to the database when clicking the //Test Connection// button, the exact error message returned from MySQL is stored in the log. To view it go to //Special > View log//. This can be very handy when trying to figure out why you can't connect to the FrontlineSMS database.
-<note important>If a connection cannot be made to the database when clicking the //Test Connection// button, the exact error message returned from MySQL is stored in the log. To view it go to //Special > View log//. This can be very handy when trying to figure out why you can't connect to the FrontlineSMS database.</note>
+</WRAP>
-**Check database every //x// mins. for new messages**: This is the time in minutes between checks of the FrontlineSMS database for new messages. The minimum is 2 minutes and if you don't set it, this is the value it will be given.
+== Check database every //x// mins. for new messages: ==
+This is the time in minutes between checks of the FrontlineSMS database for new messages. The minimum is 2 minutes and if you don't set it, this is the value it will be given.
 ==== Message settings ====
-**Keyword to identify mSupply message**: 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.
+== Keyword to identify mSupply message: ==
+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 and Notifications ====
+==== Error messages and notifications ====
 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.
-// Back to: [[preferences:general|General preferences]]//
+// Previous:  [[preferences:synchronisation|Synchronisation]]    Next: [[reports:introduction|Reports Basics]]//
+\\
+\\
+|  //  Previous:  **[[preferences:synchronisation]]** | | Next: **[[preferences:barcode_scanning]]** //  |
 ---- struct data ----
+pagestatus.status    :
 ----