Question
Scotiabank
CA
Last activity: 4 Oct 2018 13:54 EDT
Multitenancy Instance visibility
Hello
This is related to Multitenant Pega instances, generally class instances created in 'shared' layer are not visible to tenant layer, we can configure this by using these below three DASS
-
Multitenant/InstanceVisibility/TenantOnly - Class instances (belonging to Shared application) are not visible to tenants. Similar to 3rd one.
- Multitenant/InstanceVisibility/TenantCanOverrideShared - Class instances (belonging to Shared application) are visible to tenants.
- Multitenant/InstanceVisibility/TenantCannotOverrideShared - Class instances (belonging to Shared application) are not visible to tenants.
Can anyone please let me know differences between 1st and 3rd DASS? i.e. TenantOnly & TenantCannotOverrideShared, I could not find any differences when I tested it.
Regards,
Sandeep
Message was edited by: Lochan to add Category
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
IN
Hi Sandeep,
Below are the differences:
Tenant Only(Multitenant/InstanceVisibility/TenantOnly): A tenant can see instances in his own tenant plus instances in the shared layer. Tenants can create their own versions of instances that were originally defined in the shared layer.
Tenant Can Override Shared(Multitenant/InstanceVisibility/TenantCanOverrideShared): A tenant can see instances in his own tenant plus instances in the shared layer, but CANNOT create instances that override instances in shared.
Tenant Cannot Override Shared(Multitenant/InstanceVisibility/TenantCannotOverrideShared): A tenant can see only instances in his tenant layer, and cannot view shared instances.
More details:
In MultiTenant instance, there must be a distinction made between what can be visible and modified only in the "shared" context, what can be visible and modified only in the "tenant" context, and what can be visible and modified in both. In order to define these distinctions, the following three categorizations have been created:
Hi Sandeep,
Below are the differences:
Tenant Only(Multitenant/InstanceVisibility/TenantOnly): A tenant can see instances in his own tenant plus instances in the shared layer. Tenants can create their own versions of instances that were originally defined in the shared layer.
Tenant Can Override Shared(Multitenant/InstanceVisibility/TenantCanOverrideShared): A tenant can see instances in his own tenant plus instances in the shared layer, but CANNOT create instances that override instances in shared.
Tenant Cannot Override Shared(Multitenant/InstanceVisibility/TenantCannotOverrideShared): A tenant can see only instances in his tenant layer, and cannot view shared instances.
More details:
In MultiTenant instance, there must be a distinction made between what can be visible and modified only in the "shared" context, what can be visible and modified only in the "tenant" context, and what can be visible and modified in both. In order to define these distinctions, the following three categorizations have been created:
- Tenant Only
- A tenant can only see instances of these classes that exist in the tenant layer.
- A shared system user can only see instances of these classes that exist in the shared layer.
- Modification (creation, deletion, etc) happens independently within each context ("shared" or "tenant").
- Tenant Can Override Shared
- A tenant can see and modify any instances created in the shared layer. (i.e. create a new, modified instance in the tenant layer that overrides the unmodified shared instance)
- A tenant can also freely create new instances of these classes.
- Tenant Cannot Override Shared
- A tenant can see any instances created in the shared layer.
- A tenant cannot modify or override any instances created in the shared layer.
- A tenant can also freely create new instances of these classes (except for Data-Admin-System-Setting).
-Supraja
Scotiabank
CA
Hello Supraja
I did a POC based on your post above. Everything went fine except one. I am not sure wheather this is as per product functionality or is a defect. PFB
Tenant Cannot Override Shared
You mentioned that "A tenant cannot modify or override any instances created in the shared layer.", I wrote an activity (In a Tenant) to open a data instance (The class of the Data instance is added in the above DASS and server restart done), then modify some non-key properties, then performed Obj-Save. I checked in the database and found out that a new record is created and pzTenantID of the new record 'shared'!! That means it is overridden in the 'shared' context while activity was run from a Tenant. As the new record is marked as 'shared', it is visible from other Tenants also.
Can you please confirm if it is a normal functionality or is a defect in Pega code? I am using Pega 7.1.9
Regards,
Sandeep
Centene
US
As a multitenant administrator I have created the rules in multitenant layer. And "Multitenant/InstanceVisibility/TenantCanOverrideShared" DSS has been modified to include the class but I am not able to view the datapage in the tenant application.
DO I need to mention that class in all 3 DSS's?
Pegasystems Inc.
IN
Hello,
I see that you have asked this question on one of your posts too! Multitenant Implementation Layer
Regards,