The tenant layer represents tenant-customized content. The level of customization may vary by tenant, ranging from a customized login screen that displays a tenant’s company logo to a highly customized business process that is integrated into other customer systems and processes.
If you think about it like your enterprise class structure; Your Framework layer is the "Shared" layer across all tenants. Than you specialize at the implementation layer (Tenant layer) based on the requirements of each tenant.
I agree the sentence "The shared layer does not usually store any rules even if they are common to different tenants." Is confusing and should be re-written. The sentence should have the context that the tenant cannot create any rules in the shared layer even if they are common to different tenants.
One thing to note is the multi tenant implement layer which is located in the shared layer can be amended by the tenant but not directly. The changes are made in a development system and tested before the administrator moves amended rules into the shared multi tenant layer.
Posted: 5 years ago
Updated: 5 years ago
Posted: 2 Mar 2016 21:54 EST Updated: 2 Mar 2016 21:55 EST
can you please elaborate on the following statement I found in the same lesson : . In a multi-tenant system different customers share the assets, however the customer data is stored in the tenant layer and is not accessible to other tenants.
How is this managed? When it says customer data, I am not referring to the customer specific process/UI/integration customizations. How does Pega ensure that the transactional or other customer data for one tenant is not visible to another tenant ? Is there any documentation on PDN related to this ?
Hi thanks for your response. So when we create a new tenant or say 2 tenants, my understanding is that we should also do the following :
Create full implementation layer , i.e. classes, rulesets, application rule for each of them. The Application rule for implementation layer will obviously sit on the top of the framework or shared layer.
Create new access groups (does the wizard creates these automatically?) for tenant developers, end users, admin users and map each of them with the tenant specific application.
Any tenant specific customizations will be done in the implementation layer.
Is this correct? Or can tenants still point to the shared layer application/application rulesets, since customizations for a tenant will be done through their specific URL and hence that rule will be picked up by rule resolution automatically as the pzTenantID matches. Please confirm my understanding.