@Kamil Janeczek Its better to give video series,as What ever small things we could do earlier those things are becoming complicated. Simple launching a pop up with Respected Data using Data Reference Case Reference and Embedded data  

@Kamil Janeczek@Kamil Janeczekwow, thank you all for the wonderful series .

Kindly share some notes on migration from older UI to constellation like major issues being faced, key takeaways etc.

Thanks again and can't wait for the next in list.👌

@Kamil Janeczek These articles are really great to understand the Constellation in detail. A big thanks for sharing these details. 

I have a few very specific questions on the architecture?

1. What contents are stored in CDN sever? Could you please share a few very specific examples?

2. What contents are stored in app-static server? Could you please share a few very specific examples?

3. Who initiates a call to the CDN server and at what point during a transaction? Is it initiated by the browser? What's the protocol for this communication? 

4. Who initiates a call to the App-static server and at what point during a transaction? Is it initiated by the browser? What's the protocol for this communication?

5. How the does the browser process the metadata of the UI and render it? Does it use the Pega Constellation JS libraries which are loaded when the constellation portal is loaded for the first time during a user session?

@Kamil Janeczek Thanks for these articles they are great. One topic I would like to see if how we would embed a web analytics tool (such as Google Tag Manager) into a constellation app.

@Kamil Janeczek 1. In the article - https://community.pega.com/blog/how-constellation-works-authoring-rendering - it is mentioned

"When creating Cases and displaying assignments in an application, users are sending requests from their browser to the Infinity Server through the DX API. The Infinity Server requests information from the App-Static UI service, where the JSON definition of the View is stored."

Aren't the JSON definition of views stored in pega data base itself? If we do not have any customer specific static asset do we really need App-Static service?

2. On receipt of the view meta data along with case data I assume the ConstellationJS interprets them with the help of contents available from CDN and renders the HTML? Please confirm on the understanding.

3. If so, when we develop a custom DX component and publish it, does it get published in the Pega CDN or else how does the ConstellationJS interpret this new implementation? Or although the component is custom but it is bound the broad syntax categories available and interpretable by ConstellationJS?

4. Now in case of SDK based implementation or Custom client implementations how does the ConstellationJS interpret the ui meta data received from Infinity server, that would not defined by the syntax available in the assets of Pega CDN?

Hi @Kamil Janeczek, 

I understand that, according to the current product design, landing pages can only support list views and not form/partial views. However, I’d like to present a scenario: imagine needing a simple search functionality from an external system or the Pega database containing 20-30 million records. In this case, I wouldn’t want the data page to retrieve all 30 million records through the list view and then filter them using the prompt filter.

This is a common use case in most of enterprise suite of Pega applications, which are implemented using Theme-Cosmos/ui-kit. We typically have a simple search button that queries the system of record with a large volume of data and displays the results to the user. Unfortunately, this limitation is forcing us to reconsider some of our apps in Pega Constellation.

It would be very helpful if Pega Constellation could offer the capability to query the database based on user-entered data and fetch the relevant records for display, without fetching the entire dataset.

Please let me know if you have any questions

@Kamil Janeczek

- The OOTB list display patters are like displaying tabular view with predefined actions like Add, Edit, delete, search etc.

Now consider a view in Traditional UI, where with each rows in the result table there is an action icon on-click of which user gets couple of menu options like - Attach File, Change Stage, Update Data etc. In OOTB constellation, we cannot incorporate these actions, so how do you recommend to implement these UI options in constellation, actions are needed against each row record ?

@Kamil JaneczekThank you for providing this resource.  I have a requirement where I need to add a button to a table row which would create another case based on the row context.  This was very easy in Cosmos, but I can't see to find the best way to do this in constellation.  On the right side of the table, we need a button for each row to launch a new case

@Kamil Janeczek

Consider the simple use case:

Parent Case

---- Child Case

A lisview for the child case needs to be created where one of the column needs to display the parent case id and parent case label.

Approach:

A list data page was created which gets loaded based on a report definition defined on child class. The report definition includes an inner join with parent class and the parent pyID and pyLabel are fetched. Using a response data transform parent Id and labels are mapped to child level attributes Primary Case ID and Primary Case Label.

Now, when in the list view the above data page is referred the attributes Primary Case ID and Label never appears and hence those values cannot be included in the table.

Question:

Is the only option for this use case is to copy parent data during  child creation or use a case reference field for this use case? If yes, how to use case reference while using a list data page for a table view