5.0 DataEntryModule

[hafeezminhas]

DataEntryModule Scaffolding DataEntryModule Routing & Services DataEntryBaseComponent DataEntry Tab based navigation DataEntry DailyForm2 Implementation

[isedwards]

Form states

All data entry forms should implement the following states:

• [x] isEditable
  • isEditable is false when the user has not completed the 'Form Selector'. When false, the form fields are disabled and cannot be edited
  • isEditable is true when a the user has completed the 'From Selector'. When true the form fields are enabled and can be edited
• [ ] isModified
  • isModified is false when the form fields are either empty or contain data from the database that has not been changed. When false, both the form fields and the form selector are both enabled - the user can either modify the data OR change form by altering the form selector
  • isModified is true when the user has altered the data in the form. When true, the form selector should be disabled until the user either saves their changes or cancels the edit. When isModified is true, isEditable will also be true - a form can only change to isEditable being false when it no longer contains changes.

Daily data entry form behaviour

• [x] A month/year will always be selected. Default value is the current month/year. An empty data form with disabled fields should be shown if station and element are not selected (this gives feedback that will be interacting with the correct form before they start choosing station/element etc.)
• [x] An hour is always selected (range 0 to 23). Defaults to 0600
• [x] A form is always displayed, however all fields in the form are disabled until a valid choice is made using the form selector (isEditable = false)
• [x] For our initial implementation, the user can select any station/element combination – even if this is not listed in the stationelement table. This is consistent with the current behaviour of Climsoft. Stations and element can be selected in any order
• [ ] Unit selection is just read from/written to form_daily2 table. The choice has no impact on form values

Buttons

• [ ] Submit button should be called Save if record is being created for the first time
• [ ] Submit button should be called Update if an existing record is being updated
• [ ] A Delete button should be shown if a record exists and can be deleted
• [ ] Reset should be renamed Clear for consistency with old software

Next steps

Additional complexity can be added after all of the above is implemented (@isedwards to add more details in comments below)

The additional complexity includes:

1. Implementing form validation behaviours
2. A sequencer that determines which form should be automatically displayed next after the user submits data
3. Only being able to select those elements that are available for a particular station - or only those stations that have a particular element