diff --git a/.gitignore b/.gitignore index e5ad1d5..2714bdf 100644 --- a/.gitignore +++ b/.gitignore @@ -7,4 +7,5 @@ static/css/uikit.min.css instance/application.cfg.py test.py .VScodeCounter -celerybeat-schedule \ No newline at end of file +celerybeat-schedule +instance/application.cfg.py diff --git a/application/access_module/templates/login.html b/application/access_module/templates/login.html index 1a5d763..f37aec3 100644 --- a/application/access_module/templates/login.html +++ b/application/access_module/templates/login.html @@ -3,6 +3,7 @@
+
+ Generating a shopping list is as powerful as you wish to make it. In this form you will make the choices of what and when you want to + generate the list for. You will be adding specific items in the system, even can add all the safety stock items or specific ones, recipes, even other shopping lists + can be added to this one list. This is a snapshot of a moment though and any calculated safety stocks become static and can change if there is a long wait. +
+Choosing the shopping list type informs the system of your intent when actually using the list when viewed. It will inform the system if it should + completely delete the list (known as a "Temporary" list) or if it should just change the states of all items to new (known as a "Permanent" list). Permanent lists would be used + for reoccuring lists that never change and can be reused. Temporary lists will generally be used when generating a huge one time list, or something small that you just want to + track quickly. +
+Fill out the basic info asked for here, the description could be helpful to remind yourself and others what the list was generated for. + The shopping list name must be unique! +
+Operators are what drives the engine that is a shopping list. You can configure each on specifically for the list you + want to generate and each will operate in their own manner behind the scenes. +
+| Name | +Qty/UOM | +Operations | +
|---|
| Name | +Qty/UOM | +Operations | +
|---|
| Name | +Operations | +
|---|
| Name | +Operations | +
|---|
| Name | +Operations | +
|---|
A custom Item is an item that does not exist in your system but you would like to show up on your shopping list. This is useful for items + you dont often have to buy or do not want to keep track of but give the users the ability to see it. +
+| + | + |
|---|---|
| Name | ++ |
| QTY | ++ |
| UOM | ++ + | +
| Main Link | ++ |
+ + +
+An Uncalulated System Item is an item choosen from the configured SKUs in your + system. The uncalculated part means the quantity asked for in the list will always remain to be what + you set it to during configuration of the list or while editing. +
+| Name | +Qty | +UOM | +Operations | +
|---|
An Uncalulated System Item is an item choosen from the configured SKUs in your + system. The uncalculated part means the quantity asked for in the list will always remain to be what + you set it to during configuration of the list or while editing. +
+| + | + |
|---|---|
| Name | ++ |
| QTY | ++ |
| UOM | ++ + | +
| Main Link | ++ |
+ + +
+A Calculated System Item is an item choosen from the configured SKUs in your + system. The calculated part means the quantity asked for in the list will be calculated at the time + that the list is generated based on set safety stock and quantity on hand. +
+| Name | +Operations | +
|---|
Recipes can be built into the system and when added through this operator each ingrediant will be added to the list at the recipes quantity and UOM.
+| Name | +Operations | +
|---|
This operator allows you to select other shopping lists that already exist to have their + items added onto this lists items.
+| Name | +Operations | +
|---|