Hi,

I have a problem with Application Tenancies not working the way I want, I
want to drive it off a field 'region', such that a person is assigned a
tenancy of GLOBAL, NORTH, SOUTH, NORTH-WEST and these are also the regions
that they are working in too, so when they create a record their region
gets assigned to the new record and that controls who else can see the
record.

This mostly works, but there is one small glitch. The main problem I have
is setting it up so that region is non-null and any records created by a
GLOBAL tenancy user are seen by all users, while those created by a NORTH,
SOUTH or NORTH-WEST user are seen only by users with the same tenancy. By
changing the region of a record it can change tenancy.

Presently this is broken, or at least it I think it was working correctly
when I allowed a record with a region of null to be the GLOBAL ones. I need
to have this working for a demo tomorrow, so advice is welcomed on how best
to set this up properly.

My base class that controls all this here:
https://github.com/Stephen-Cameron-Data-Services/isis-chats/blob/master/dom/src/main/java/au/com/scds/chats/dom/AbstractChatsDomainEntity.java

The other small glitch is that a person record created in the process of
creating a participant doesn't get assigned a region automatically. I have
a work-around for that in place at present, anything that has a null region
gets presented as having a global tenancy.


Thanks

Steve Cameron

Reply via email to