I don't quite understand why those tables is split into different tables? What are the reasons? Is it semantically has different meanings?
Accounts: http://apidocs.sugarcrm.com/schema/6.5.18/corp/tables/accounts.html
Users:
http://apidocs.sugarcrm.com/schema/6.5.18/corp/tables/users.html
Users are those that log into your SugarCRM instance. Accounts are for keeping track of your customers, vendors, etc. They don't log into your SugarCRM.
Related
I have a list of initiatives (proposals) which have an originating team and impacting team.
For e.g.
There are leads for each of these teams and yes the impacted teams data is a continuous string of teams.
Originating team will be part of impacted teams too.
Given that there is a mapping between Originating teams and leads, I have created a user filter such that Leads only see the initiatives originating from their teams. That was pretty straightforward. User filter on Originating teams and mapped the users to the teams.
Now the ask is, they also want to see the initiatives that impact them.
For e.g. The Product lead also want to see the Initiative 2 where they are impacted.
How do I go about creating this complex user filter?
I am working on system that will manage orders. Orders can be created via admin or via customer. Employee can take orders and change it's status.
My system should have three global types of users:
Admin - this type of users mostly uses WEB interface. Admins have different access levels, so some of them can only create orders, and others - edit core info about pricing and so on.
Customer - this type of users uses customer's mobile app. Main action is to add and cancel orders.
Employee - this type of users uses employee's mobile app. Employees can see open orders, assign themselves to orders and change order statuses.
Also, Customer and Employee can be authorised with phone number, that can be changed at some time (independently of each other). Admins can be authorised with uname + pword.
Current solution has one table for Admins, one for Customers and one for Employees.
So first part of question is how to structure database properly?
The second part is about authorising in REST api. In current solution I have three endpoints, that are authireses usertype independently.
admins/auth
customers/auth
employees/auth
And my thoughts is to keep three tables as is, because each usertype is slightly different concept and really independent. And keep authorisation as is, but add something like roles and privileges to auth token to restrict access for some resources.
I see several SaaS companies, such as bitrix have different top level domains by country ex:
bitrix.de for germany
bitrix.in for india etc.
A lot of times this is required because of legal requirements that the data generated in Germany should stay within the EU/German data center, and vice versa same for India.
My queries
To achieve the above, there would be 1 database + 1 App Server in India, and a similar 1 database + App server for Germany also?
What should happen if a user created an account on bitrix.in ie in the Indian database, and then he goes and tries to accidentally log in to bitrix.com, should such a login go through or should I tell the user that he is on the wrong site?
Tx
You can create a central database for storing meta data - accounts, logins, etc. This could be common/shared across all countries/domains or it could be separate in each database but replicated at a central meta database.
Now when someone logs in, after authentication (using the central meta database) you can redirect them to the appropriate domain.
In such a configuration when creating a new user you will have to ensure that the user is unique across all domains/databases.
I recently started developing for Odoo and have created a few modules, but I'm having difficulty figuring out the structure for accounts, customers, and partners.
I'm trying to adapt one of our current applications in which it's Accounts>Customers> and Accounts>Billing accounts. I basically what to add a tab to the customer creation view called billing accounts. Problem is I can't figure out what is tied to what. It looks like it's Partners>Accounts>Customers or Sales>Accounts>Customers.
Thanks
If you are talking about a bank account (i.e. your customer or partner's bank account), I believe the relation is res_partner_bank (many2one relation).
If you are talking about another concept, please clarify what you mean by billing account (invoicing, pur accounting, etc...) in order to understand the context.
As a sidenote, every entity (person/company) is stored in res_partner. You then have a boolean flag specifying whether the entity is a customer and/or a partner
and/or a company (so in short partner_id is usually the relationship key).
As part of my work I need to test several flows between multiple accounts.
For that I would like to create multiple Facebook accounts and define specific relationships between them.
I would like to know if this is possible (even manually) in order to not abuse Facebook systems, and if so, then how.