Merge pull request #1466 from vjFaLk/develop
More improvements to the documentation
This commit is contained in:
commit
e1ca0a89a7
3 changed files with 13 additions and 10 deletions
|
|
@ -34,21 +34,24 @@ You can also set other properties of the field like whether it is mandatory, rea
|
|||
We can add the following fields:
|
||||
|
||||
1. Article Name (Data)
|
||||
1. Author (Data)
|
||||
1. Status (Select): For Select fields, you will enter the Options. Enter **Issued** and **Available** each on a new line in the Options box. See diagram below
|
||||
1. Publisher (Data)
|
||||
1. Language (Data)
|
||||
1. Image (Attach Image)
|
||||
2. Author (Data)
|
||||
3. Description
|
||||
4. ISBN
|
||||
5. Status (Select): For Select fields, you will enter the Options. Enter **Issued** and **Available** each on a new line in the Options box. See diagram below
|
||||
6. Publisher (Data)
|
||||
7. Language (Data)
|
||||
8. Image (Attach Image)
|
||||
|
||||
|
||||
#### Add Permissions
|
||||
|
||||
After adding the fields, add Permissions. For now, let us give Read, Write, Create, Delete and Report access to **Librarian**. Frappe has a finely grained Role based permission model. You can also change permissions later using the **Role Permissions Manager** from **Setup**.
|
||||
After adding the fields, hit done and add a new row in the Permission Rules section. For now, let us give Read, Write, Create, Delete and Report access to **Librarian**. Frappe has a finely grained Role based permission model. You can also change permissions later using the **Role Permissions Manager** from **Setup**.
|
||||
|
||||
<img class="screenshot" alt="Adding Permissions" src="{{docs_base_url}}/assets/img/doctype_adding_permission.png">
|
||||
|
||||
#### Saving
|
||||
|
||||
Click on the **Save** button. When the button is clicked, a popup will ask you for the name. Enter it and save the DocType.
|
||||
Click on the **Save** button. When the button is clicked, a popup will ask you for the name. Give it the name **Article** and save the DocType.
|
||||
|
||||
Now login into mysql and check the database table created:
|
||||
|
||||
|
|
@ -87,7 +90,7 @@ Now login into mysql and check the database table created:
|
|||
18 rows in set (0.00 sec)
|
||||
|
||||
|
||||
As you can see, along with the DocFields, a bunch of standard columns have also been added to the table. Important to note here are, the primary key, `name`, `owner` is the user who has created the record, `creation` and `modified` are timestamps for creation and last modification.
|
||||
As you can see, along with the DocFields, several standard columns have also been added to the table. Important to note here are, the primary key, `name`, `owner`(the user who has created the record), `creation` and `modified` (timestamps for creation and last modification).
|
||||
|
||||
{next}
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ When you create a **DocType** a new folder is created in the **Module** and a mo
|
|||
|
||||
### Developer Mode
|
||||
|
||||
To create models, you must set `developer_mode` as 1 in the `site_config.json` file and execute command `bench clear-cache` or use the user menu in UI and click on "Reload" for the changes to take effect.
|
||||
To create models, you must set `developer_mode` as 1 in the `site_config.json` file located in /sites/library and execute command `bench clear-cache` or use the user menu in UI and click on "Reload" for the changes to take effect.
|
||||
|
||||
{
|
||||
"db_name": "library",
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Then let us create the other DocType and save it too:
|
||||
|
||||
1. Library Member (First Name, Last Name, Email ID)
|
||||
1. Library Member (First Name, Last Name, Email ID, Phone, Address)
|
||||
|
||||
<img class="screenshot" alt="Doctype Saved" src="{{docs_base_url}}/assets/img/naming_doctype.png">
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue