recently, i learn [branch development], pega suggests create a branch development application(set the main application as built-on application),then create branch,and check rules to branch to update…
This action will avoid affecting the main application and so it does.
But the development application doesn’t have main application’s case types.
What if i want to run case type in development application to check branch rules,and switch to main application to run again to check main application rules are not affected by development application’s branch ?
@yikaiz17254581 To ensure the branch development application can run case types from the main application for testing, you need to verify the setup. First, confirm that the branch development application is correctly set as built-on the main application. This allows it to inherit the main application’s rules, including case types. If the case types are still missing, make sure the ruleset containing them is included in the branch application stack. You can then run case types in the branch application to test changes made in the branch without affecting the main application. To validate the changes, switch back to the main application by logging in with its access group and run the same case type to confirm the branch changes haven’t impacted it. If the case types are inaccessible in the branch application, revalidate and save them to refresh rule references. Always test in a non-prod env and ensure dependent rules are accessible in the branch application.
@yikaiz17254581 Yes thats correct; the ruleset stack is managed in Configure > Application > Structure > RuleSet Stack, and if it’s auto-configured correctly, that part should be fine. However, if you still cannot see the main application’s case types in the branch development application, ensure the main application’s case type rulesets are explicitly accessible. You might need to check the Application Rulesets or Inheritance Settings in the branch development application to confirm that the rulesets containing case types are properly inherited. If everything is set up but case types are still not visible, try opening the case types in the main application, revalidating them, and saving them to refresh references. Additionally, check if the operator you are using has access to the branch development application’s access group and its associated rulesets. This should resolve the issue and allow the branch development application to access the main application’s case types.
Today, I wake up the [low-code App Builder] academy exercise environment, and create a development application, And the dev app shows the case type that the main app has…So i think it is trial environment’s bugs.