Custom DX Component publish shows Success but no rule created / not visible in ruleset or Rule-UI-Components - Pega 24.2

User Experience
1

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

2

@Akhilesh.Madala

  • what is the output of below command ?
  • Does operator used for pushing for component checked access group ?
  • default access group has access to pushed ruleset ?

Command

npm run list Server

Note: i hope you have already gone through this Pegasystems Documentation

3

@PraveenP16892497

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.

4

@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

5

@josenavas

Thanks for reply Jose

  1. 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.

  2. 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.