304
edits
m (→Objects) |
m (→Objects) |
||
| Line 37: | Line 37: | ||
Objects are the generic terms to speak about records managed by the application. It can be for example: a customer, a supplier, an invoice, an order, a proposal, an agenda event, a user, ... | Objects are the generic terms to speak about records managed by the application. It can be for example: a customer, a supplier, an invoice, an order, a proposal, an agenda event, a user, ... | ||
Each object is managed by a Dolibarr module. | Each object is managed by a Dolibarr module. Depending on the module you enabled or not, some objects may or may not appear in the application. | ||
Dolibarr policy is to use a common way of working for each managed modules or objects. | Dolibarr policy is to use a common way of working for each managed modules or objects. | ||
So, for each object, you will find a menu entry to Create (menu is called "New Object") and a menu entry to list all objects (menu is called "List"). | So, for each object, you will find a menu entry to Create (menu is called "New Object") and a menu entry to list all objects (menu is called "List"). | ||
| Line 46: | Line 46: | ||
[[Image:Screenshot thirdparty.png|480px]] | [[Image:Screenshot thirdparty.png|480px]] | ||
Also, each object may have different status to define where object is | Also, each object may have different status to define where object is within the workflow. Status of object is always visible in the last column of list of objects. | ||
Number of status will depends on object and options defined in the module setup dedicated to object management. | Number of status will depends on object and options defined in the module setup dedicated to object management. | ||
Current definition and signage of status are (with default theme "eldy") : | Current definition and signage of status are (with default theme "eldy") : | ||
edits