Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
other_stuff:virtual_stores [2018/11/15 10:23] – [The Visibility tab] mark | other_stuff:virtual_stores [2024/02/12 09:59] – [Master lists tab] Rachana Kunwar | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{indexmenu_n> | + | {{indexmenu_n> |
- | ===== Virtual stores ===== | + | ====== 26.07. |
From the //Special// menu, choose //Show stores// | From the //Special// menu, choose //Show stores// | ||
- | ==== What is a " | + | ==== What is a virtual store? ==== |
In mSupply a //virtual store// is a way of segregating particular stock so that some users only see that stock and the transactions associated with it. When a user logs into mSupply, they choose a particular store to login to - this we call the current store. mSupply then operates as if: | In mSupply a //virtual store// is a way of segregating particular stock so that some users only see that stock and the transactions associated with it. When a user logs into mSupply, they choose a particular store to login to - this we call the current store. mSupply then operates as if: | ||
- | - the stock in that store is the only stock available. | + | - The stock in that store is the only stock available. |
- Only stock from the current store will be available for issuing, | - Only stock from the current store will be available for issuing, | ||
- Reports will relate to stock in that store | - Reports will relate to stock in that store | ||
Line 18: | Line 18: | ||
* A hospital pharmacy where you have two dispensing locations: an inpatient pharmacy and an outpatient pharmacy. | * A hospital pharmacy where you have two dispensing locations: an inpatient pharmacy and an outpatient pharmacy. | ||
* A pharmaceutical warehouse where stock from a particular donor is received, issued and accounted for separately to stock in the rest of the warehouse. | * A pharmaceutical warehouse where stock from a particular donor is received, issued and accounted for separately to stock in the rest of the warehouse. | ||
- | * A hospital pharmacy where the pharmacy store stock is treated separately to the dispensary stock. You would set up mSupply with a store called " | + | * A hospital pharmacy where the pharmacy store stock is treated separately to the dispensary stock. You would set up mSupply with a store called " |
* A pharmaceutical warehouse where you have 2 or more actual warehouses. These may be adjacent or several hundred kilometres apart. (Of course you need network connectivity between sites to run mSupply at each site). | * A pharmaceutical warehouse where you have 2 or more actual warehouses. These may be adjacent or several hundred kilometres apart. (Of course you need network connectivity between sites to run mSupply at each site). | ||
* You're using mSupply mobile- each mobile site will synchronise data with a virtual store on the mSupply server. | * You're using mSupply mobile- each mobile site will synchronise data with a virtual store on the mSupply server. | ||
Line 42: | Line 42: | ||
==== Creating new stores ==== | ==== Creating new stores ==== | ||
- | To create a new store click the //New store// button in the Store list window shown [[other_stuff: | + | <WRAP center round important 60%> |
+ | This new store will inherit the same user and group permissions (but not login permissions!) as the store which you are logged in to when you execute it. It is therefore worth logging in to a store that has similar user and group permissions to those that you want to have in the new store. | ||
+ | </ | ||
+ | To create a new store click the **New store** button in the Store list window shown [[other_stuff: | ||
- | {{ : | + | {{ : |
- | **Store code:** The code used to identify | + | <WRAP center round alert 60%> |
+ | If you want to create | ||
+ | </ | ||
- | **Store type:** Set in the drop down list to the right of the //Store code// field. Can be one of: | + | |
+ | === Name === | ||
+ | The name used to identify the store throughout mSupply. It must be unique and mSupply will tell you if another store has the same name; you will need to change it before you can save. Any non-printable characters entered before or after the name will be removed. Any entered in the name will be replaced with an underscore ('' | ||
+ | |||
+ | === Store code === | ||
+ | The code used to identify the store. If you have a lot of stores it would be helpful if you decide on a good pattern to use for the codes. The code must be unique too; mSupply will tell you if the code is already in use and you will need to change it before you can save it. Any non-printable characters entered before or after the code will be removed. Any entered in the code (and spaces) will be replaced with an underscore ('' | ||
+ | |||
+ | === Store type === | ||
+ | |||
+ | Set in the drop down list to the right of the //Store code// field. Can be one of: | ||
* Store: a normal store used for managing inventory and issuing to customers | * Store: a normal store used for managing inventory and issuing to customers | ||
* Dispensary: a store used for managing inventory and dispensing to patients | * Dispensary: a store used for managing inventory and dispensing to patients | ||
- | * Report: a special type of store used for reporting information only, not managing inventory. Don't use this unless specifically told to do so! | ||
- | **Name:** The name used to identify the store throughout mSupply. | ||
- | **Organisation name:** The name of the organisation running the store. Defaults to the organisation name entered in File > Preferences. | + | === Organisation name === |
- | **Address line 1-5, Postal /Zip code, phone:** Enter the address and contact details for the store in here if there are any. These details can be used in reports | + | The name of the organisation running |
- | **Disable this store:** Check the //Disable this store// checkbox to stop the store from being used. You might want to use this feature if the store is not ready for use yet or is no longer to be used and can't be deleted. You will be asked to confirm the disabling after clicking on the //OK// button on this window. | + | === Address details === |
+ | |||
+ | Enter the address and contact details for the store in here if there are any. These details can be used in reports | ||
- | **Responsible officer:** Select the officer responsible for the store in this drop down list. A helpful reminder for others and can be used in reports. | + | === Disable |
+ | Check the //Disable this store// checkbox to stop the store from being used. You might want to use this feature if the store is not ready for use yet or is no longer to be used and can't be deleted. You will be asked to confirm the disabling after clicking on the //OK// button on this window. | ||
+ | |||
+ | === Responsible officer === | ||
+ | |||
+ | Select the officer responsible for the store in this drop down list. A helpful reminder for others and can be used in reports. | ||
+ | |||
+ | === Store credentials === | ||
+ | These are used when the store needs to be identified securely over electronic communications. An example of this is when using the cold chain app for monitoring temperature in cold storage and freezers. | ||
+ | |||
+ | To tell mSupply to use the credentials, | ||
+ | |||
+ | This will enable the **Username** and **Password** text fields and you can enter the appropriate details. | ||
+ | |||
+ | * The // | ||
+ | * The // | ||
+ | |||
+ | If you need to view the password you have entered to check it is correct, click on the {{: | ||
=== Tags === | === Tags === | ||
- | Tags are used in reporting to group stores together. This area shows the tags that the store currently has. To add a tag, simply click into the area and type the tag's name. When you have finished typing the tag's name then press the Tab or Space keys on the keyboard (not Enter or return, that will close the window!). You know when you have done it right because the tag will appear in its own little box with an ' | + | Tags are used in several ways: |
+ | * for determining which programs a store can use. | ||
+ | * for contronlling some customisation features. | ||
+ | * for reporting to group stores together. | ||
+ | * | ||
+ | This area shows the tags that the store currently has. To add a tag, simply click into the area and type the tag's name. When you have finished typing the tag's name then press the Tab or Space keys on the keyboard (not Enter or return, that will close the window!). You know when you have done it right because the tag will appear in its own little box with an ' | ||
+ | |||
+ | When you click on the **OK**, **OK & Next** or **OK & Previous** buttons, any new tags you have created here will be added to the list of name tags in your system. See the [[names: | ||
After having created a new store, the Stores list window will display the new list of all stores and you may double-click an entry to edit that store' | After having created a new store, the Stores list window will display the new list of all stores and you may double-click an entry to edit that store' | ||
<WRAP center round alert 90%> | <WRAP center round alert 90%> | ||
- | To do a number of the following steps, you will need to log in to the new store. | + | To do a number of the following steps, you will need to log in to the new store. |
</ | </ | ||
Line 74: | Line 112: | ||
* Set the store' | * Set the store' | ||
* Set the [[other_stuff: | * Set the [[other_stuff: | ||
- | * Setup Synchronisation if you are going to use a synced system. See [[other_stuff: | + | * Setup Synchronisation if you are going to use a synced system. See [[other_stuff: |
* Setup any [[other_stuff: | * Setup any [[other_stuff: | ||
- | * Set the [[items: | + | * Set the master lists used by the store (a convenient method for controlling item visibility). |
<WRAP center round alert 90%> | <WRAP center round alert 90%> | ||
- | If this newly created store will be ' | + | If this newly created store will be ' |
</ | </ | ||
- | ==== The preferences | + | ==== Preferences |
- | This tab contains | + | <WRAP center round important 90%> |
+ | * The preferences | ||
+ | * The preferences | ||
+ | * In a **synced system** there will be multiple 'sync satellites' | ||
+ | * Other preferences (accessed through **File > Preferences...**) apply to //all// stores in an mSupply datafile. | ||
+ | | ||
+ | </ | ||
- | {{ :other_stuff: | + | This tab contains the preferences that can be set for a store. Each store has its own settings for these preferences: this is different for the settings in //File > Preferences// |
- | This is what each preference does: | + | |
- | ** Sort available batches by VVM status ** If the store is only to be used for vaccines, this option allows you to sort the list of available batches by the vaccine status column rather than the expiry date | + | This is what the tab looks like: |
- | ** Patient created in this store not visible in other stores ** If you check this box, patients that are created in this store will not be visible in any other stores - they will only be visible in this store. | + | {{ : |
- | ** Names created in this store not visible in other stores | + | The **Search |
- | ** Allow users to enter total quantities to distribute to appropriate packs** If you check this checkbox, users will be able to enter the total quantity that they wish to distribute to appropriate packs. | + | This is what each preference does: |
- | ** Round up the distributed quantity** | + | |<100% 40%>| |
+ | ^ Sort available batches by VVM status rather than Expiry | When issuing stock, this will sort the list of available batches by vaccine status first, then by expiry date rather than by expiry date first (e.g. [[issuing_goods: | ||
+ | ^ Patients created in other stores not visible in this store| If this is checked, patients that are created in other stores across all sites will not be visible in this store. If it is **off**, all patients from all stores from all sites will be visible to this store. It is set to true by default when a store is created. **USE CAUTION:** Turning this **OFF** for many stores does not scale well and can overload the sync system. See the [[dispensing: | ||
+ | ^ Names created in other stores not visible in this store| If this is checked, names (customers, suppliers, manufacturers, | ||
+ | ^ Allow users to enter total quantities to distribute to appropriate packs| On a customer invoice an additional **Total** field is displayed so that users can enter the total quantity of units that they wish to distribute or the number of packs.| | ||
+ | ^ Round up the distributed quantity| The value for distributed quantities will be rounded upwards.| | ||
+ | ^ Able to pack items into multiple boxes| Checking this enables the functionality for packaging goods into boxes on the // | ||
+ | ^ Store: Able to issue in foreign currency| Foreign currencies can be used on supplier invoices for overseas suppliers.| | ||
+ | ^ Allow editing selling price on customer invoice lines| Individual selling prices can be edited on customer invoice lines. Please note that the **Price editable when issuing** checkbox on the //General// tab of an item's details page must also be checked for each item that the price is to be editable for. | | ||
+ | ^ Purchase order must be authorised| Turns on purchase order authorisation. See [[purchasing: | ||
+ | ^ Finalise customer invoice automatically| Automatically finalise customer invoices with confirmed status, which is normally when the goods are dispatched.| | ||
+ | ^ Customer invoices must be authorised| Turns on customer invoice authorisation (i.e. goods can only be sent to a customer after the action has been authorised). See [[other_stuff: | ||
+ | ^ Authorisation needed only if over budget| This additional option is enabled when customer invoice authorisation is turned on. | | ||
+ | ^ Confirm customer invoices automatically| Set a New Customer Invoice status to confirmed when the OK button is clicked. This means that it is not possible to print a picking slip for the issued goods.| | ||
+ | ^ Supplier invoices must be authorised| Turns on supplier invoice authorisation (i.e. goods can only be brought into stock when the action has been authorised). See [[other_stuff: | ||
+ | ^ Confirm supplier invoices without asking | Set a New Supplier Invoice status to confirmed when the OK button is clicked. The goods are made available in stock without informing the user.| | ||
+ | ^ Goods received lines must be authorised: | ||
+ | ^ Locations must be entered for goods received | A shelf location must be entered on the goods receipt item line form when receiving goods into stock. | | ||
+ | ^ Able to specify manufacturer when receiving, ordering or quoting for items | Gives users the option to record the manufacturer of goods when making purchase orders, goods receipts or entering a quotation from a supplier.| | ||
+ | ^ Show item unit column when issuing| If checked, when goods are issued on a customer invoice or prescription, | ||
+ | ^ Log transaction edit | | | ||
+ | ^ Set pack to one for all visible items in this store| | | ||
+ | ^ Use remote authorisation for response requisitions | Turns on remote authorisation for response requisitions. See [[other_stuff: | ||
+ | ^ Include requisitions from this store in suppliers' | ||
+ | ^ Can manually link requisition to supplier invoice | When receiving stock, users can match the supplier invoice to the initial requisition. They can then add items from the linked requisition, | ||
+ | ^ Automatically populate supply quantities with requested quantities | On requisitions, | ||
+ | ^ Show extra fields on requisitions | When a line is selected on a response requisition, | ||
+ | ^ Keep requisition lines with zero requested quantity on finalise | If this is checkled, lines on requisitions | ||
+ | ^ Show comment field when entering supplier invoice lines | Allows users to type a comment for individual items received on a supplier invoice. | | ||
+ | ^ Use EDD placeholder lines in supplier invoices from this store | If turned on, any placeholder lines on a customer invoice that is a stock transfer are duplicated on the supplier invoice in the receiving store when the customer invoice is finalised. The placeholder lines in the supplier invoice appear on an // | ||
+ | ^ Consolidate batches | Items with the same batch, expiry date, pack size, location, donor, cost and sell price will // | ||
+ | ^ Edit prescribed quantity on prescriptions | When checked an additional **Prescribed quantity** field is available when entering a prescription line. See [[dispensing: | ||
+ | ^ Allow users to choose diagnosis on prescriptions | When checked an additional **Diagnosis** drop down list is available on a prescription. See [[dispensing: | ||
+ | ^ Use consumption and stock from customers for internal orders | If checked, when calculating | ||
+ | ^ mobile: Alert if a patient is dispensed the same vaccine multiple times in a week | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ mobile: Enforce lookback period | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ mobile: Uses vaccine module | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ mobile: Uses dispensary module | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ mobile: Uses dashboard module | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ mobile: Uses cash register module | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ mobile: Uses payment module | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ mobile: Uses patient types | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ mobile: Uses Hide Shapshot column | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
+ | ^ Pickface replenishments must be authorised | If checked, pickface replenishments in this store must be authorised by a user who has permission to authorise them before they can be finalised. See the [[items: | ||
+ | ^ Able to specify VVM status when receiving items | If checked then a new **VVM status** field will be available on a supplier invoice for the user to select the current VVM status of the batch when it is received on a supplier invoice or inventory adjustment. See the [[receiving_goods: | ||
+ | === Notification preferences === | ||
+ | These are used by the notification/ | ||
- | ** Able to pack items into multiple boxes** If this box is checked, then mSupply will provide a detailed way of packaging goods in to boxes to be distributed to clients. | + | == Threshold for overstock == |
- | ** Store: Able to issue in foreign currency** If you check this box, you can use foreign currencies | + | The minimum months of stock an item must have to be considered as overstocked. i.e. in danger of expiring on the shelf before it is used. An alert is triggered for an item if the total quantity in stock (including all batches) divided by the average monthly consumption of the item (calculated using the last 12 months' |
+ | This value should be set no lower than the maximum amount of stock that you would expect to regularly have in stock. | ||
+ | </ | ||
- | ** Allow editing selling price on customer invoice lines** Checking this box means that you can edit individual selling prices on customer invoice lines. | + | == Threshold for understock == |
- | ** Purchase order must be authorised** If checked then purchase order authorisation | + | Also called <wrap em> |
+ | This alert should only be triggered when your stock levels fall below your buffer stock levels. | ||
+ | </ | ||
- | ** Finalise customer invoice automatically** | + | == Expiring items period == |
- | **Customer invoices must be authorised** | + | An alert will be triggered for an item if a batch is due to expire in less than this number of months. The default is 3 months.<WRAP center round tip> |
- | + | This alert should be triggered if there is a reasonable risk that your store, //or your store' | |
- | **Confirm customer invoices automatically** | + | </ |
- | **Supplier invoices must be authorised** If this preference is checked then all supplier invoices must be authorised by a user with permission to do so before they can be confirmed (i.e. goods can only be brought into stock when the action has been authorised). See [[other_stuff: | ||
- | **Confirm supplier invoices without asking** This setting is used to set a Supplier Invoice' | ||
- | **Goods receipt lines must be authorised** This setting is used to restrict authorisation of a Goods Receipt to authorised users only. Only when a Goods Receipt is authorised can it be processed | + | === Custom data === |
+ | This section is for store specific custom data fields that must always | ||
- | ** Locations must be entered for goods received** This setting requires the user to type a shelf location on the Goods Receipt Item Line form when receiving goods into Store. This feature enforces identification of shelf location of stock. | + | **Monthly consumption lookback period**: The number of months of consumption information |
- | ** Able to specify manufacturer when receiving, ordering or quoting for items** This setting gives the user the option | + | **Months lead time**: The number of months before ordered goods normally arrive. Used to calculate how much stock to order for the suggested quantity in requisitions, |
- | **Custom stock fields ** In this area you can choose to use up to four custom fields for labelling incoming stock. The checkboxes tell mSupply to use the various custom fields and the textboxes contain the labels that mSupply will use for these fields. Each custom field that is checked here will appear (with the label it has been given) on a supplier invoice when an item is being received (see [[receiving_goods:goods_receipts|here]] and [[receiving_goods: | + | === Suggested packing in boxes === |
+ | These preferences affect | ||
- | === When finalising a Goods Receipt | + | * **Prefix for generated boxes:** Defaults ot no prefix. Each box created in a suggested pack has a number which starts at 1 and increments by 1 for each new box created. Whatever you enter in this text field will be added before these numbers to give you the box names. For example, if you enter " |
+ | * **Percentage space to leave empty:** Defaults to 0. Boxes will be packed as close to 100% of their volume minus the value entered in here. This is helpful to account for situations where the size, shape and possible orientation of packs make it hard to pack them all into the actual volume expected. | ||
+ | === When finalising a goods receipt | ||
There are three options: | There are three options: | ||
* Don't receive goods into stock until supplier invoice is taken off hold - for goods to enter stock you must finalise the goods receipt and then take the automatically generated supplier invoice off hold | * Don't receive goods into stock until supplier invoice is taken off hold - for goods to enter stock you must finalise the goods receipt and then take the automatically generated supplier invoice off hold | ||
Line 141: | Line 236: | ||
* Choose **On hold** if the store is being used by mSupply mobile, and the goods receipt needs to be confirmed before receiving. | * Choose **On hold** if the store is being used by mSupply mobile, and the goods receipt needs to be confirmed before receiving. | ||
- | ==== The logo tab ==== | + | === Location code pattern |
+ | This is used with phased stocktakes (see the [[items: | ||
+ | |||
+ | An aisle is a whole row of racking like this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | A level is a horizontal level of the racking like this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | And a position is a vertical column of the racking like this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Use the letters A, L and P to represent the aisle, level and position parts of the location code. | ||
+ | |||
+ | Let's use an example to show how it works. Let's say that the shelf location codes are in the format B01.C.01 where B01 represents the aisle, C represents the position and 01 represents the level. Then in the **Location code pattern** text box you would enter the text **AAA.P.LL** | ||
+ | |||
+ | It doesn' | ||
+ | |||
+ | |||
+ | ==== Logo tab ==== | ||
{{ : | {{ : | ||
- | Here you can paste in a logo you have copied to the clipboard - you must copy the contents of a file to the clipboard, not the file itself. The file can be in .jpg, .png, .bmp, .gif, or .tiff format. This logo will be displayed at the bottom right of the navigator when you login to this store only. It will override any logo saved in the [[preferences: | + | Here you can set the **store logo** by pasting |
- | Note, after saving | + | This store logo will override the logo saved in the [[preferences:general#logo_tab|Settings > Preferences > Logo]] tab. |
- | ==== The Custom fields tab ==== | + | To print this store logo on standard customer and supplier invoices etc. you will need to go to the [[preferences: |
+ | |||
+ | Note that after saving the store logo you must login to mSupply again or use the [[admin: | ||
+ | ==== Custom fields tab ==== | ||
{{ : | {{ : | ||
- | This tab is used to save any custom | + | This tab shows the custom |
=== Adding a custom field === | === Adding a custom field === | ||
Line 162: | Line 282: | ||
To delete any custom field simply select its row in the table and click on the //Delete line(s)// button. You can use Shift+click, | To delete any custom field simply select its row in the table and click on the //Delete line(s)// button. You can use Shift+click, | ||
- | ==== Controlling Item Visibility: the Master lists tab or the Visibility tab ==== | + | ==== Master lists tab and Visibility tab (controlling item visibility) |
Controlling the visibility of items in different stores is important because you can only order, distribute, receive goods for and report on items that are visible in your store. It's also important that stores don't have items visible that they don't use so that they don't accidentally order them etc. | Controlling the visibility of items in different stores is important because you can only order, distribute, receive goods for and report on items that are visible in your store. It's also important that stores don't have items visible that they don't use so that they don't accidentally order them etc. | ||
Line 170: | Line 290: | ||
Each are useful in different situations and are described below. | Each are useful in different situations and are described below. | ||
- | === The Master lists tab === | + | === Master lists tab === |
If you have a lot of stores in mSupply, we recommend that you use master lists to control item visibility. Especially in a [[other_stuff: | If you have a lot of stores in mSupply, we recommend that you use master lists to control item visibility. Especially in a [[other_stuff: | ||
Line 180: | Line 300: | ||
- Click on **Special > Show stores...** (or click on the //Stores// icon on the //Special// tab of the navigator) | - Click on **Special > Show stores...** (or click on the //Stores// icon on the //Special// tab of the navigator) | ||
- Double-click the store who's visibility you would like to manage:{{ : | - Double-click the store who's visibility you would like to manage:{{ : | ||
- | - Click on the //Master lists// tab: {{ : | + | - Click on the //Master lists// tab: |
- | - Select which master list(s) you would like to control the visibility of items in your chosen store by checking their checkbox in the //Use master list// column: {{ : | + | - Select which master list(s) you would like to control the visibility of items in your chosen store by checking their checkbox in the //Use master list// column: {{ : |
- Click the **OK** button to finish. As soon as you do that the items on the selected master list(s) are made visible in the store and any items **not** on the selected master list(s) are made **invisible**. Any new items added to the selected master list(s) will be made visible in the store and any items removed form the master list(s) will be made invisible in the store. | - Click the **OK** button to finish. As soon as you do that the items on the selected master list(s) are made visible in the store and any items **not** on the selected master list(s) are made **invisible**. Any new items added to the selected master list(s) will be made visible in the store and any items removed form the master list(s) will be made invisible in the store. | ||
- | === The Visibility tab === | + | === Visibility tab === |
<WRAP center round important 90%> | <WRAP center round important 90%> | ||
If your system is a Sync system (with Primary and Satellite servers) and your store is hosted on a Sync Satellite server, then you will not see the Visibility tab. These settings need to be made while logged in to the Sync Primary Server. | If your system is a Sync system (with Primary and Satellite servers) and your store is hosted on a Sync Satellite server, then you will not see the Visibility tab. These settings need to be made while logged in to the Sync Primary Server. | ||
Line 216: | Line 336: | ||
* The **Make found names visible in this store ** will make all names in the last selection made with the **Query names** button visible in this store. Ask Sustainable Solutions for help if you're not sure about getting the right selection of names, as the consequences of making a mistake can be time consuming to fix! | * The **Make found names visible in this store ** will make all names in the last selection made with the **Query names** button visible in this store. Ask Sustainable Solutions for help if you're not sure about getting the right selection of names, as the consequences of making a mistake can be time consuming to fix! | ||
- | ==== The Synchronisation | + | ==== Users tab ==== |
- | mSupply has a synchronisation system designed to cope with environments which have weak or intermittent internet. The system passes information between a server and satellite (or tablet running mSupply mobile) when there is an internet connection and stores information to be sent when there is not. | + | {{ : |
- | This tab is where the store specific settings for synchronisation are mad. See [[other_stuff: | + | The users tab shows which users have permission to log into this store. |
+ | The table shows a list of all the users in alphabetical order. If a user can login to this store then their corresponding //Can login// checkbox will be checked. If the store is the user's default store then the checkbox in the //Default store// column will be checked. | ||
+ | |||
+ | You can add or remove permission for a user to login to this store by checking or unchecking their //Can login// checkbox (only if you have permission to edit store details though). | ||
+ | |||
+ | |||
+ | ==== Synchronisation tab ==== | ||
+ | mSupply has a synchronisation system designed to cope with environments which have weak or intermittent internet. The system passes information between a server and remote site (or tablet running mSupply mobile) when there is an internet connection, and stores information to be sent when there is not. | ||
+ | |||
+ | See the [[synchronisation: | ||
+ | |||
+ | This tab displays some of the synchronisation settings for this store: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The **Resync patient records when store is saved** checkbox forces all patient records to be re-synchrionised with the server when the **OK** button is clicked. This is useful if there appears to be something wrong with one or more patient records. | ||
+ | |||
+ | |||
+ | ==== Names tab ==== | ||
+ | This tab shows a list of all the names (customers, suppliers, stores, donors, manufacturers etc.) in the datafile and which are visible in this store. You are also able to edit the visibility of names: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The table shows whether the name is a customer or supplier (or both). The checkboxes in the **Visible in this store** column are editable. If checked then the name is visible in this store, if unchecked then the name is not visible in this store. Click on one of the checkboxes to change its state. | ||
+ | |||
+ | * **Store checkbox:** If checked then names thast are stores are shown in the table | ||
+ | * **Facility checkbox:** If checked then names that are not stores are shown in the table | ||
+ | * **Search names field:** If you type in here then only names that contain what you type will be displayed in the list. Useful if you want to find a particular name or group of names in a long list. | ||
+ | * **All off button:** Clicking this will uncheck all the checkboxes in the **Visible in this store** column (so making all names invisible in this store) and the button will change to **All on**. Clicking it then will check all the checkboxes in the column (and therefore make all names visible in this store). | ||
+ | * **Copy button:** Copies the current state of all the checkboxes in the **Visible in this store** column. | ||
+ | * **Paste button:** Pastes the states of checkboxes saved using the **Copy** button to the names in the table. Doesn' | ||
+ | |||
+ | Clicking on the **OK**, **OK & Next** or **OK & Previous** buttons will save any changes you make on this tab. | ||
==== Deleting a store ==== | ==== Deleting a store ==== | ||
- | To delete a store, click on the //Delete// button in the View stores window. **Note:** deletion of a store is a serious thing to do and is only possible when that store contains zero stock and there have been no transactions recorded. mSupply will check and tell you that deletion is not possible if these criteria are not met. If you can't meet these criteria and you still want to stop people using the store then you can disable | + | To delete a store, click on the //Delete// button in the View stores window. **Note:** deletion of a store is a serious thing to do and is only possible when that store contains zero stock and there have been no transactions recorded. mSupply will check and tell you that deletion is not possible if these criteria are not met. If you can't meet these criteria and you still want to stop people using the store then you can [[other_stuff: |
+ | |||
+ | <WRAP center round alert 60%> | ||
+ | If the store is **Active** on a sync satellite site, then this process will not delete the sync satellite site. | ||
+ | </WRAP> | ||
+ | |||
+ | |||
+ | ==== Transition a customer to a virtual store ==== | ||
+ | |||
+ | You may have a customer that is about to start using mSupply. | ||
+ | |||
+ | * The ' | ||
+ | * The recommended :-D method: | ||
+ | |||
+ | <WRAP center round important 90%> | ||
+ | **Whichever method is used, this is difficult to reverse. | ||
+ | </WRAP> | ||
+ | |||
+ | === Create new store and then merge with the existing customer name === | ||
+ | |||
+ | Until version v5.02 (see below), the procedure was: | ||
+ | |||
+ | - [[other_stuff: | ||
+ | - Use mSupply' | ||
+ | |||
+ | <WRAP center round important > | ||
+ | * You **must** choose the newly created store' | ||
+ | * mSupply may prevent the merge due to unfinalised CIs from other stores in the system. | ||
+ | * These can be hard to find on a multi-store system where the transactions could have come from a number of places. | ||
+ | * If these transactions are on a number of stores on satellite sites on dodgy internet connections, | ||
+ | * These inconveniences are why the [[other_stuff: | ||
+ | </ | ||
+ | |||
+ | === Turn an existing customer into a store === | ||
+ | |||
+ | Due to the limitations of the method described above, from mSupply v5.02 onwards, you can choose to convert an existing customer into a store, and thereby retain all of its properties. | ||
+ | |||
+ | |||
+ | <WRAP center round alert 60%> | ||
+ | If the name is not visible to the store that you are logged in to, this method will not work! First make the name visible, then start this process... | ||
+ | </ | ||
- | ==== Transition from a customer to a virtual store ==== | ||
- | If you have a customer that is about to start using mSupply mobile, once you create the virtual store you will end up with two customers with the same (or similar) names, as creating a virtual store also creates a linked name. | ||
- | Fear not: you can use mSupply' | ||
+ | - Log into a store that will have the same or similar user and group permissions as the new store. | ||
+ | - **Customer > Show customers...** to find the customer that you want to convert into a store and copy the Name. This will ensure that you are converting the correct name into a store - see warning below! | ||
+ | - **Special > Show stores... > New Store** | ||
+ | - Click on the **Turn an existing customer into a store** checkbox | ||
+ | - Enter the existing customer name into the **Name** field. | ||
+ | - Populate the [[other_stuff: | ||
+ | - Click **OK** | ||
- | // Previous: [[other_stuff: | + | \\ |
+ | \\ | ||
+ | | | ||
---- struct data ---- | ---- struct data ---- | ||
+ | pagestatus.status | ||
---- | ---- | ||