Error creating new application in existing organization-division

I have a Pega environment which has 2 Implementation applications. Both the apps follow Org-Div-app1-Work class structure.

In the current environment, there are two Org level rulesets, which were both skimmed and currently at 03-01-01

Also there are two Division level rulesets OrgDivxx:03-01-01 and OrgDivxxInt:03-01-01, here are also they are skimmed, and OrgDivxx:01-01-01 and OrgDivxxInt:01-01-01 ruleset versions doesn’t exist in the environment.

Now, I’m creating a 3rd impl. application say, Org-Div-app3-Work, I go to New Application wizard-> build from scratch → Choose UI architecture->Name my app-> Advance configuration-> Application structure=Implementation->Select Generate Division Layer → Hit save-> Hit Create application.

The wizard fails with this error “There was a problem while creating rulesets versions.
.pyApplicationGenerator.pyRuleSetVersionsToCreate(1).pyRequiresRuleSetVersion(1): OrgDivInt:01-01-01 is not a valid Rule Set Version”.

The log file has the below errors:

(GenerateApplicationTransaction) ERROR - !!! There was a problem while creating rulesets versions.[[pzInsKey : RULE-RULESET-VERSION app3INT 01-01-01] [Direct dependency(ies) of this RuleSet/Version:OrgDivInt:01-01-01 is not a valid Rule Set Version]

2024-05-17 16:54:34 [TABTHREAD1] (plication_Configuration.Action) ERROR - !!! Error while configuring application objects. [ [Direct dependency(ies) of this RuleSet/Version:OrgDivInt:01-01-01 is not a valid Rule Set Version]

I have tried by adding PRPC:Administartors access group, also by cloning [email protected] to a new operator id and so on, but the error is still there.

Obviously I can’t use a new Org name or new division name as some of the community discussions have suggested, because it’s a new app for the same division, and it should work. After skimming to a new major version, we delete the older version per pega best practices, but why the new application wizard is looking to create a division level Int ruleset version for a Divison instance that’s existing in the system for over 5 years?

I reviewed the below community posts that were not solved.

@ravi9779 it sounds like you need to log a support issue as the product is not behaving as documented. Please provide the INC id here so we can help track it.

@ravi9779 can you tell us if you logged a INC for this?

Did you resolve the problem?

@MarijeSchillern Hi Marjie, I will log an incident and post it here.

@ravi9779

Do the following 3 and it should work most likely.

  1. Try and check the Rulesets stack anywhere the reference of OrgDivInt:01-01 or OrgDivInt:01-01-01 (OR) on the ruleset versions for REQUIRED RULESETS AND VERSIONS. Make sure it’s changed to latest Major-Minor versions do not give patch version i.e., like 03-01; not like 03-01-01
  2. Make sure all other ruleset versions below skimmed version are locked.
  3. While creating 3rd implementation / app on advanced configuration if available manually select latest version after skimmed version.

Hope this helps.

@ravi9779 please could you provide the INC ticket id and the resolution details if the issue is now resolved?