Dolibarr ERP & CRM » Tasks and Feature requests » task #172 Can attach an event to several contactsDernières modifications
Répondre
État| Détails |
| Submitted on: | 17/09/2011 00:00 | | Submitted by: | Laurent Destailleur |
| Last Modified On: | 11/11/2013 20:24 | |
| Summary: | Can attach an event to several contacts |
| Description: | Can attach an event to several contacts.
This is a prerequisite to manage meeting rendez-vous. |
| Priority: | 9 - Highest | | Open to Any Developer: | Yes |
| Subproject: | Module Agenda | | Assigned to (multiple): | jfefe,HENRY Florian |
| Planned for version: | | | | Etat |
| Start Date: | - | | End Date: | - |
| Completion (0-100%): | 10 | | Status: | Open |
Commentaires- jfefe 02/01/2014 09:01
- Ok I've made a complementary module to manage resources which bring llx_element_resources table and UI to manage relations between objects and resource : https://github.com/aternatik/dolibarr-resource/tree/develop
This was done while coding a module to manage places (and building and rooms...) and link them to an event : https://github.com/aternatik/dolibarr_place/tree/develop
TPL are used into resource module to allow usage of another table to store specific datas. Another task exist to link several contacts to a thirdparty, I think we must use element_resources table to do that, with a new table llx_resource_contact (rowid,fk_element_resource,...). Also we could implement extrafields in this table :)
- Laurent Destailleur 19/10/2013 14:48
- Using llx_element_contact is not the good solution for doing what you want to do.
llx_element_contact is good to link a contact (thirdparty or user) to an element (invoice, proposal, order, ...)
But events into agenda are not "standard" element. There are transversal objects. Also linking to thirdparty and user is not enough. We will want also to link to a "location" (a room for example).
Also into the calendar standard, we need to follow the status "busy" or not for each linked contact and "mandatory or guest".
For this reason (and other one), we need another table. I suggest
llx_actioncomm_resources
This table will contains id of event, id of element and type of element (type may be user, thirdparty and later room). Table will also have field "busy" and "mandatory".
So, I am afraid you must forget to use the contact existing template. The need is more specific and can not be compliant with "contact" template used for common elements.
- jfefe 29/03/2013 21:59
- Should we use a new table actioncomm_contact as attaching contact on propal/invoice ?
Or does it use the table element_element?
It would be great to define type of contact too with existent dictionary.
|
|
This was done while coding a module to manage places (and building and rooms...) and link them to an event : https://github.com/aternatik/dolibarr_place/tree/develop
TPL are used into resource module to allow usage of another table to store specific datas. Another task exist to link several contacts to a thirdparty, I think we must use element_resources table to do that, with a new table llx_resource_contact (rowid,fk_element_resource,...). Also we could implement extrafields in this table :)