Hello, your statement and question is vague.  Please provide more background.  Is this question based on the course lesson contents for the Enterprise Class Structure lesson in the SSA 7.1 course? 

The statement you've made is not in that lesson.   The lesson contains some examples of data assets for each of the layers, Organization, Framework, Division, and Implementation.  

Or from another lesson?  I don't want to provide the wrong guidance if I'm misunderstanding the context of the question.

Tara

Pega Academy Support Team

Hi Pott,

This is not part of any lesson.

Let me be more specific on my question,

I have a implementation layer, which has Work class,Data class & Integration class.

My understanding is that rules that belong to work and data should be kept in a common ruleset and integration rules in a different ruleset. Correct me if am wrong.

Now I want to know, in any of the scenario do we require to create a dedicated ruleset for Data rules? If yes, I like to know such scenarios.

Hello, since your question is not directly related to SSA course which this forum is specifically about I'm going to recategorize this posting to the Pega Platform General questions.

Correct, we recommend keeping integration assets in a separate ruleset.  This is because those may need to be versioned at a different time than the implementation layer.

Yes, it is reasonable to put data assets in a separate ruleset if there is a versioning benefit to do so for a specific application or for the purpose of sharing that same ruleset across multiple applications.  It's more about the benefit of the assets in a separate ruleset than the type of asset.

Tara

Pega Academy Support Team

Hello SHARATHVISWA,

Remember some data rules also go into org rulesets. Most of the time implementation work and data compliment each other and that is the reason of putting them together. As in any other architecture INT is isolated as they are reusable across applications in any organization.

In a typical large organization, the org rulesets contain all data classes across the org. You can further have another org data ruleset apart from ORG in particular if it is needed. ( I assume in rarity) .

Thanks,

Ashok