This commit is contained in:
@@ -46,6 +46,17 @@ CURRENT TODOs
|
||||
=-=-=-=-=-=-=
|
||||
|
||||
TODO: FORM CUSTOMIZATION FORM
|
||||
- Customize option on every form if user is logged in with BizAdminFull rights
|
||||
- When customize is selected a generic form pops up with a list of fields provided by the backend and their current settings and controls
|
||||
- This form can then be re-used everywhere as it's a stock object and this way we don't need to have a customize form for every existing CRUD form
|
||||
- Choosing to expose one or more of up to 16 custom fields on form in custom field section that shows when at least one is enabled
|
||||
- NO ability to edit localized text here, that's a separate central UI thing.
|
||||
- Yes, v7 allows editing of lt in a form but I've decided to focus on one thing for this and not confuse it
|
||||
- Set whether a field is visible or not to user
|
||||
- Some stock fields will never be able to be hidden, they will be "core" fields required for AyaNova operations and will have their hidden checkbox grayed out
|
||||
- Set whether a field custom or stock is required to have a value entered or have it's value changed
|
||||
- If required then it's like a business rule and treated just like that at the back and front end
|
||||
- During business rule validation check at backend it checks if the fields are required and have entries and returns a validation error if not exactly the same as for built in rules
|
||||
- Do before main grid stuff below
|
||||
- Where is it exposed in the UI?
|
||||
- In each form or centrally? or both?
|
||||
|
||||
Reference in New Issue
Block a user