Publishing a custom DX component reports Success to ruleset myRulesetName:01-01-04, but no rule is created.
->No new rule is created in the target ruleset/version.
->Component does not appear in Rule-UI-Components
Publishing a custom DX component reports Success to ruleset myRulesetName:01-01-04, but no rule is created.
->No new rule is created in the target ruleset/version.
->Component does not appear in Rule-UI-Components
Command
npm run list Server
Note: i hope you have already gone through this Pegasystems Documentation
All the components I previously developed on my server are visible, and components from the Pega side are also shown.
→ Previously, we developed in Labs and exported to the application; now we publish directly to the application.
→ I noticed strange behavior: after I changed the OAuth configuration, the component was published to a different (open) ruleset—one that is not the ruleset specified in task.config.json.
@Akhilesh.MadalaHi Akhilesh,
Something similar happened to me recently, but in my case I had changed my operator’s default access group and I forgot to change it back to the application where I needed to publish the DX component… I think if you switch the default access group, that might resolve your problem.
Regards,
-Jose
Thanks for reply Jose
By default, we log in via SSO. When I create a branch or component ruleset, I’m unable to publish to it. The command shows success after running, but nothing gets published.
I created a separate operator, and with that, I’m able to publish to a branch but not to a ruleset. Again, the command shows success after running, but the component is not actually published.
Few things you need to take care.
The issue has been resolved. In Pega 24, there appears to be a platform-side glitch where users are unable to publish multiple times to the same ruleset version.