I am new to Constellation. I’ve created an application and REST Connector. Here are my findings:
New Application does not seem to create “Int” ruleset and class any more.
REST Connector wizard creates a class at the root level instead of “MyOrg-Int” or “MyOrg-MyApp-Int” class.
Is this an intended design? Or, is Pega expecting developers to create “Int” class and ruleset by themselves? I know both approach should work, and my question is what is the best practice, and if “Int” concept has been changed recently, I want to know why, and its background.
Yes, what you’re seeing is intended behavior in Constellation and newer Pega versions. When you create a new application, Pega no longer automatically generates an “Int” ruleset or class. Similarly, the REST Connector wizard now creates classes at the application’s root level instead of under something like MyOrg-Int. This is part of a design shift where Pega avoids enforcing a strict layered structure by default.
The “Int” layer itself has not been removed or deprecated. It is still a valid and recommended concept for separating integration logic from your core application. Earlier versions of Pega automatically created this layer to enforce best practices, but in Constellation, Pega gives developers more flexibility. The platform assumes that not all applications need that level of structure, especially smaller or simpler ones.
From a best practice perspective, you should still create an “Int” layer manually when working on enterprise-level or scalable applications. It helps in decoupling external integrations, improving reusability, and managing changes more cleanly. However, for smaller applications or quick implementations, it is acceptable to keep integration rules within the main application layer.
Pega has shifted from enforcing architecture to allowing architects to decide it. The “Int” layer is now optional, not automatic—so you should use it when it adds value, not just because it existed in older versions.
It’s also worth noting that instead of creating Int- classes with the REST wizard, it directly leverages JSON data transforms to parse the incoming response into your data model. Just in case you were wondering how we handle mapping responses to the applications data model.
Thank you very much for your clear explanation! Understood, and I will create an Int class and rulesets only if client is planning to have many integrations.