Close popover
Victor Talukdar (VTALUKDAR)
Cognizant Technology Solutions
Technology Architect
Cognizant Technology Solutions
VTALUKDAR Member since 2010 19 posts
Cognizant Technology Solutions
Posted: April 4, 2020
Last activity: April 10, 2020

Implementation of Specialized Data Pages per entity


  I have a design clarification question : I work in an application which cuts across more than one country/entity (let us call the countries X and Y). Now, there is a strict regulatory requirement to have a segregation of data between the entities : users of Country X would NOT be able to view the data of country Y.


Now, we have certain Data Types which are to be used for both X and Y , but with different data. For example, there is a Referential Data object which pulls the list of options for all drop down in the application. Some dropdown values might be the same for both X and Y entities (for example, a list of Countries) , but the data is mostly different.

Now, from the 7.4 CLSA course, it seems that PEGA usually recommends creating Data Types in the Organization or, at most, in the Framework Layer. But here the only approach seems to be to specialize the Data Type into the Implementation Layer (Org-X-Data-DataType and Org-Y-Data-DataType). 

Can this be considered a good design, considering the requirements ? Is there any other approach we can try ?

I had also considered the approach to create a Data Type in Framework layer called Org-FW-Data-DataType and then have an entity column to indicate the relevance of the data. But this means that, the data is filtered only for relevant entity users, the data is not being "strictly" seggregated between entities. Hence this approach was not considered.

Pega Platform 7.3 Case Management Financial Services Lead System Architect
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.