CalvinBackup/erpnext
1
0
Fork 0
mirror of https://github.com/frappe/erpnext.git synced 2026-02-12 17:23:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Form Design Guidelines (markdown)

Rushabh Mehta
2020-11-19 17:02:54 +05:30
parent dbc602d363
commit f33c8d7890
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Form-Design-Guidelines.md

@@ -42,4 +42,8 @@ Make field and section labels and titles as self explanatory as possible. Descri
### 11. Positioning of "Enabled" or "Disable"
If the form has an "Enabled" or "Disabled" field, it must be in the last field in the first column of the first section. When the form is disabled, all fields other than the enable/disable field should be read-only.
If the form has an "Enabled" or "Disabled" field, it must be in the last field in the first column of the first section. When the form is disabled, all fields other than the enable/disable field should be read-only.
### 12. Logs related to a transaction / sync / integration must be linked in the "Settings"
If there are any logs related to background activities related to an integration or transaction, they must linked from the parent transaction or the configuration object. (Example: General Ledger Entries for an invoices are linked form the Invoice, or Email Queue linked from Email Account).