A custom field and a widget was successfully created and published via command line. But, I could not find the field or widget via App Studio. Trying to add the new field and widget to the MediaCo sample application.
Ran the following:
npm run create
npm run buildComponent
npm run authenticate
npm run publish
When I ran npm run list and selected server, I can see both custom components being listed.
When you run npm run publish it asks for the ruleset, so can you please check that the published component is available in that ruleset and if that’s available then it takes time to reflect but i don’t know why it takes time to reflect but it will, as it took time for me to reflect.
@PPRANEETH007 Thanks. I can confirm that the components exist under the ruleset as ‘component’. How do I get the components available for selection on my Case Type?
When I published the component, I did not specify any ‘application name’ when prompted. So, it should be available to all applications.
Are the components only available to specific org, operator id, app, or any other conditions?
We have received feedback that we can do a better job making published DX components easily visible from App Studio.
Once they get uploaded you can find them in the places that you would use them – e.g. the “display as” option for a field on a view, the list of widgets you are adding to a landing page, or the view templates you can use when creating.
We have gotten feedback that it would be helpful to see all published custom components somewhere in App Studio and are planning to add that functionality, although we cannot yet say what release that will be in.
Hello, I encountered the same issue as @AlfredL17033194. The problem is that the requested steps of the tutorial are not allowed in Pega 23 with Constellation.
Click the User interface tab, click the Views tab, and click an existing form view.
In the Edit field dialog box, in the Display as list, select My Local Action Launcher.
The above tutorial is included in the documentation. What we have to do to execute the exercise? Did we miss any configuration or setting? Why we see “UX” tab in the case type view and not “User Interface”? Why “Display as” does not include the new field component?