In all our projects, we use the following development structure:
AppTarget - built on Constellation
AppTest - built on AppTarget
AppDEV - built on AppTest
Working with the Traditional version was seamless, but switching to Constellation didn’t work quite right.
Development is being done in branches of the AppDEV application and was later merged into AppTarget.
After finishing development in the AppDEV branches and running tests, everything worked fine, but when merging into AppTarget (Ruleset version) things that worked with the branches stopped working.
To get them working again, I had to save all the data pages back to the branch. Working this way isn’t very efficient, so I wanted to know the best way to work in a Constellation development environment. Should I continue with the mentioned structure or just have one application (target)?
I appreciate any suggestions or advice on following PEGA best practices.
Hi @HalynaK2 : I don’t see any issues with the approach. Will you be able to explain the nature of issue when you merge to the application rulesets which made you to save them back to the branch?
When working in the AppDev application, a branch is created and by default all rules related to views and configurations get stored in the AppDev rule sets.
To avoid issues later, it’s better to include the main target rule set (for example, AppTarget RuleSet) in your development application on top of Dev ruleset while you are building. This way, any rules you create will be stored in the correct target rule set version of the branch, instead of ending up in the AppDev rule sets.
If you don’t do this, rules created in App Studio (like views, localizations, or paragraphs) will automatically go into the AppDev rule sets. Then, during consolidation, you’ll face errors because you cannot directly merge AppDev rule sets into AppTarget rule sets.
In that case, you would need to manually “Save As” those rules into the AppTarget rule set before merging, which adds complexity.
So the recommended approach is:
Add your main rule set to the AppDev application before starting development. Do your branch development with that rule set included, so rules are stored correctly.
After merging, remove the branch from the application. This avoids errors and keeps all rules aligned with the target rule set from the start.