This is what I’m thinking. The reports have particular tables and columns from which they’re generated. So we can sort those tables and columns, and create ‘table components’ which have ‘column draggable components’ which appear as dropdown list under the particular table. This is going to be lots of components to display. We’ll use tooltips to show more information for a particular column. This route is painful, but this is what I have for now.
Terry suggested we use the lists in the system to create the draggable components. In his method it’ll be easy to get the query that we’ll need to execute at the back. ‘Wise Gramps Terry’ explains that we’ll have draggable components like this:
Patient_Full, Patient_Last_first and Patient_full_reverse will be the draggable components (and will appear as title in the list). patient_data is that table, that has columns fname,lname, mname. the user will choose the component in any order that suits them.
The lists in the system have fields, id, title, order, default, active which are mandatory. We’ll fill these fields accordingly. ‘The wise man’, @teryhill says we’ll add fields; notes, toggle_1 and toggle_2.
- notes is something like this: patient_data|lname|fname|mname. This will give the field the generator needs to generate a report.
- toggle_1 : sorts each column depending on the value of the checkbox
- toggle_2: From my understanding, this will act the same as ‘ACTIVE’. Except Terry has another thing in mind.