Backend: Consequent separation of appointment and normal function tables #59
Labels
Comments
This was referenced Apr 13, 2017
Closed
Last part fixed in 4.6.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need general separation of normal tables and appointment tables. If user clicks on "new", than he is asked, what kind of table he wants to create. [Alternative solution: Two Buttons: "New normal table" / "New appointment table"] If user chooses normal table, the tab name is "Normal table" [ger: "Normale Tabelle"], else "Appointment table" [ger: Terminbuchungstabelle].

Of course, in MYSQL, the variable "table function" (value "normal" or "appointment") is saved. We need this for csv/xml export/import.

When we export the "table function" variable, we should remove the csv/xml import option "Imported table is appointment table".
In both tabs "Normal table" and "Appointment table" we have to remove the option "function". We don't need it anymore.
For the tab "Normal table" we have to remove the "Additional row sorting and deleting column" and create TWO NEW OPTIONS:
(this is issue #49 (Frontend / Layout: Seperate delete buttons from change sort order column)
We have to ensure that new options (Row sorting column +Deleting column+Function variables) are imported and exported correctly in CSV/XML Export!!
In frontend, we need a new column called "Deleting", where all red "X" are shown. We have to ensure that layout is correct in every layout mode. For example in stack view.

For the tab "Appointment table", we can remove the following options:
For the tab "Style" we can remove:
The text was updated successfully, but these errors were encountered: