Draft:Specification Module Public Portal: Difference between revisions

Jump to navigation Jump to search
m
Tag: 2017 source edit
Tag: 2017 source edit
Line 11: Line 11:
A table already exists to store login/pass for external portals.  
A table already exists to store login/pass for external portals.  
It is already used to store :
It is already used to store :
- login from external website (for example stripe customer key of a thirdparty). The column site contains "stripe".
* login from external website (for example stripe customer key of a thirdparty). The column site contains "stripe".
- login from website for users of a website. The column site contains "dolibarr_website" and we store the id of website into fk_website
* login from website for users of a website. The column site contains "dolibarr_website" and we store the id of website into fk_website
So we will also use it to store login for the external portal:
So we will also use it to store login for the external portal:
- the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty
* the column "site" will contains "dolibarr_portal" and fk_soc will contains the id of the thirdparty


On the record of a thirdparty, the module Public portal must enable the new tab will be visible to show all accounts/login (=record of table llx_societe_account) linked to this thirdparty.
On the record of a thirdparty, the module Public portal must enable the new tab will be visible to show all accounts/login (=record of table llx_societe_account) linked to this thirdparty.

Navigation menu