Question
Health First
US
Last activity: 25 Jul 2023 8:54 EDT
Unable to create new views in landing pages
Hi,
We are currently using 8.8.2 and trying to build a new application based on constellation (cosmos-react).
We have a simple requirement to provide a search screen for user and upon entering the information and click on 'Search', we need to call the api. I am unable to see my view that I want to add in my new landing page.
I only see 4 out of the box widgets and few list views. I tried creating a section rule from Dev studio and configured it as 'Dashboard widget' but that is also not appearing when I go back to 'App Studio' landing page.
Any suggestions would be appreciated!
Pegasystems Inc.
IN
Hope you have configured all the required settings for constellation and accessing your application over HTTPS.
Section rule created from dev studio does not work to configure from APP Studio.
You have to use APP Studio only to configure the view as well.
Custom widget you want to inject needs to put in through REACT and pushed in. refer to how to build custom components https://docs.pega.com/en-US/bundle/constellation-dx-components-88/page/constellation-dx-components/custom-components/create-custom-components.html
Health First
US
@SriharshaAnika Thank you so much for your reply. Yes, we have configured necessary settings to run the constellation service. I tried creating a view in app studio, but the view that I created is not appearing in the landing pages. Is there specific type of views that I have to create to be shown in the landing pages? I can only see List type of views being visible in the landing pages.
Cognizant
GB
@prathimak4186 Hi, we are also facing a similar situation where we have created a new view through the user interface tab on a case type but the view does not show up as an option in the landing page view options when you go to add a widget.
Did you manage to find a solution to make your custom views show up in the landing page by any chance?
Thanks
Aaseya IT Services Pvt. Ltd.
NL
Hello @prathimak4186, few things here:
1. Sections are not used in Cosmos-React, we have views instead.
2. Views are to be created from the App Studio only.
3. Buttons are not available so you maybe you can redesign in a way that you have search fields in one view and the calling of the API happens when you submit the first view.
Hope this information helps!!
Tokio Marine HCC
GB
@SaurabhG7134 : can you pls provide some screen print for point 3 .
I have similar requirement to build custom search to fetch data via api and display on same screen. Many thanks in advance.
3. Buttons are not available so you maybe you can redesign in a way that you have search fields in one view and the calling of the API happens when you submit the first view.
Aaseya IT Services Pvt. Ltd.
NL
Hi @NavdeepK2565, what I was suggesting is to have a screenflow, where the first screen captures the data from the search field and then using that data you could perform the post processing DT/Activity and in the second screen build & display the results, this would be the ideal way imo. But, if anyway you want to display it on the same screen then you can make use of the DT- pyRefreshData, save it to your RS and class and build your search result list in there. Also, add the visibility condition to the view that will display the result grid.
Updated: 22 May 2023 12:40 EDT
Coforge
IN
1. In App studio, channels> web portal> landing page> home.
2. In region A, click +, click widget, and select the checkbox for your custom widget.
3. Perform integration testing in the widget by publishing it to infinity. Publish the widget to a pega infinity instance to view it in cotext of a landing page.
Branched Information: Originally posted as reply here.
Health First
US
@TusharC43 If we are creating a custom widget using pega react components, could you please clarify below questions:
1. Are there any downside of things during the pega upgrade process?
2. Is this considered as customization?
3. Also once the custom widget is published into pega dev environment, Rule-UI-Component gets created. To promote to higher environments, pushing this Rule-UI-Component is sufficient or need to do anything and promote the component source code?
4. If a custom component is developed locally and published. Is there a way another developer can get the source of this custom component? For future maintenance/changes, this will be helpfull.