Multi Tenant Question

customaware

I am setting up my app for Multi-Tenancy using the unique code per tenant method rather than a separate BS for each tenant.

Regarding the Unique Code for each tenant.....

I obviously need to include the Tenant Code in every BO that is unrelated to any other BO.
But for BOs that Own Reference BOs, I am interested to hear if others include the TenantCode in EVERY BO or only those BOs which
own Reference BOs?

My thinking is add it to EVERY BO so that I can easily set up Export processes to Export ALL of the Data for a particular Tenant. Is this the right logic
or am I making a simple job harder?

Any advice or comment would be appreciated.

BenHayat

Mark, back in Nov. I started a thread related to this subject. My original thinking was to include the Tenant ID in other BO as well (sort of having a peer relationship between them). But as I read through docs and watched Vlad's videos, he made a point of having a clean hierarchical relation (which is more of OO relationship) than adding additional relations, which makes the model more convoluted. I started thinking that way and built my first model and I agree with him.
Yes, back in the day, I did create the Tenancy ID in other records, but with Aware IM, you can travel up or down the hierarchy with ease, and Aware doesn't need to create/maintain extra indexes.
Just make sure you maintain a clean/strong chain of relationships in your entire object graph, then you should be good to go..
Just my two cents.

customaware

Thanx Ben,

Yes, how it is described in the HowTo is much simpler and more elegant. Just need to trust the BO References which certainly have not ever let me down.

A further question.

If I have ALL the users of the system in RegularUser this means that I cannot have an admin for each tenant as the login names need to be different. Is there any way to overcome this.

BenHayat

eagles9999 wrote
If I have ALL the users of the system in RegularUser this means that I cannot have an admin for each tenant as the login names need to be different. Is there any way to overcome this.

I have created two exact BOs, one is called RugularUser and the Other is AdminUser. The only difference is their Access Level.

customaware

Hi Ben...

Yes, I understand that but that still does not get around to need for say, 10 all belonging to different Tenants but all with the loginName as admin.... or am I missing somehting?

BenHayat

eagles9999 wrote
Hi Ben...

Yes, I understand that but that still does not get around to need for say, 10 all belonging to different Tenants but all with the loginName as admin.... or am I missing somehting?

Then I wouldn't put them under the umbrella of any Tenant, but rather outside as independent, but create another table that stores the relationship of a tenant with Admin. So, a single Admin can serve multiple Tenants and yet have one login. This way, the Admin and Tenant are on parallel level.

Another Approach to have Admin as the parent of the Tenant. That has it's own ways of doing things.

I don't know your true logic structure, but based on what I have read so far, that's how I would go.
See which one will serve you better.

customaware

Have sent PM Ben.

kklosson

Just create another role for something like Manager. Leave Admin to yourself.

customaware

Hi Kingsley,

The roles and access levels are not the issue.

Say I have 3 Tenants..... ACME Birdseeds, ACE Playing Cards and Dodgy Panelbeaters.

Imagine each of these Tenants has an Employee called John Smith.

Is there any way to have a LoginName of jsmith for each Tenant.

Clearly it is inappropriate to have the same LoginName for a particular Tenant.

However, when a New Tenant "ACE Playing Cards" creates their first Employee and enters a LoginName of jsmith, it will be a bit bizarre when they get told that LoginName already exists when it is in fact their first Employee...because they are not aware of an Employee named John Smith in in Tenant "ACME Birdseeds"

Of course the problem is that if you only have a login page with LoginName and Password, then the system does not know which Tenant to use for the jsmith logging in.

BenHayat

Mark, now that you explained it, I can tell you that once you explain to your clients that Login names are global in the system, just like they are in FB, Twitter, Google and many multi tenant system. It's best to have a unique login name to be able to jump into the tenant. Your user can simply prefix their login name with a couple of letters. For example my company name is "Micro Intelligence Corp.", so in many places I prefix MIC_BenHayat.
Secondly, if you're using email as login, then they should be unique anyway.

Hope this helps.

tford

Secondly, if you're using email as login, then they should be unique anyway.

This is what I encourage users to use in ALL apps, not just multi-tenant.