Hi Team,

We are looking on finding a way to do data segregation on CONFIG TABLES for multi-site & multi-org scenario:

OBJECTS INCLUDED:
1. MAXDOMAIN
2. MAXINTOBJECT
3. MAXIFACEIN
4. MAXEXTSYSTEM
5. AUTOSCRIPT
6. CRONTASKDEF
7. WFPROCESS
8. CONDITION
9. DMPACKAGEDEF
10. MAXINTMSGTRK
11. MAXLAUNCHENTRY
12. OSLCRESOURCE
13. APIKEYTOKEN

Following ways tried so far but not allowed on above tables-

1. New attribute creation.
2. Script Creation.

Business would be interested to know how can we show/hide data based on ORGID/SITEID filter in above raised objects.

Thanks!

------------------------------
Shivangi Goyal
------------------------------

I find it strange that you would need to restrict access to these tables based on Org/Site as these are administration application objects.

When you have two or more organisations using the same instance the configuration of the instance should be managed centrally to ensure the configuration complies with your central design and is tested across all organisations to check for conflicts.

Even if at some point you needed to move one of the organisations onto a new instance your configuration would need to be assessed and re-applied and then your org/site specific data migrated.

------------------------------
Steve Lee
Maximo Technical Sales Specialist
IBM
Leeds
------------------------------