Posted: 7 Oct 2019 4:43 EDT Last activity: 24 Mar 2020 10:10 EDT
Ask the Expert - Dynamic and Ajax Containers with Sreedhar Ganduri
Join Sreedhar Ganduri (@SreeGanduri) in this Ask the Expert session (14-18 Oct) on Dynamic Containers and Ajax Containers.
About Sreedhar: Sreedhar Ganduri is a Senior Product Manager in User Experience area. He has been in technology industry for around 15 years, he joined Pegasystems in 2012 and is responsible for UI technology features in the Pega Platform. He has driven several key UI features in the last several releases. He was also part of the mobile and reporting areas of Pega platform. He currently leads Pega’s UI Product Management team in India.
Message from Sreedhar: I’m very excited to be a part of this community initiative and eager to hear directly from our partners and customers. I'm glad and excited to share my learnings and knowledge in configuring and using dynamic content in UI.
1) What is the core difference between Dynamic and Ajax containers?
Ajax containers are light weight version of Dynamic containers. Dynamic containers are typically tied to portal’s screen layout center panel, where as you can drop Ajax containers any where in your portal layouts.
2) If I am not wrong from Pega 8.3 , we can have a max of 3 Ajax containers in a defined tab. Can 3 containers communicate and share data with each other?
Yes we have 3 variants of Ajax containers. You can if you handle your data pages properly. You can also target opening of a work item/section from a link/button in one Ajax container to another.
3) Should the Ajax containers be used to use display another case or it can just include simple section with some static information?
Just like dynamic containers, you can show ‘case information’, you can also use the new action “launch section” to just show a section in Ajax container.
4) Does Pega Pulse at the right hand top the screen uses the Ajax containers?
5) What are use case to use Ajax container? And 6) Are there any best practices or guidelines when using an Ajax container?
Use Ajax containers to separate your dynamic content from static content. They are useful in organizing dynamic content across your portal especially if your application is single page. Full page reloads can be avoided. Since Ajax containers are just div based containers, you have flexibility to place them in relevant locations that you think are valid.
Many times users are interested in specific amount of information about a case instead of the entire baggage of information that comes with case object, you can use Ajax containers to show this specific information and if required, show the rest in stages.
Another major use case of Ajax container is when your application is dealing with multiple case types. You are on a specific case context and would like to see information about a related to child case type. With Dynamic containers, you either open this info in a new tab or replace the existing document. Where as with Ajax containers, you can achieve this without losing the existing context, by loading this information in a “secondary” Ajax container - like a peek and preview panel.
One example for iframe based version is the tabbed Dynamic containers that you see in Designer studio, the SPA version of Dynamic container is Div based, but it takes the entire center panel of screen layout. Every refresh is going to refresh the entire center panel. Also, SPA mode can host only one document at any given point of time.
Yes, you can completely avoid Dynamic containers by using Ajax containers. You can also use them together, depends on the type of application you have.
If I have an application which has ability to do several different jobs which are independant in nature at one place, like creation of cases/opening reports/spaces/documents, I can use a top level dynamic container to host these independant jobs in the center panel of the portal and inside each of these documents, i can use Ajax containers to perform its own multiple tasks.
We are using the customer service framework (8.1.4 ) where the service items are loaded in the AJAX container . Thanks for this feature ,UI is really quick now and users are happy.
We have one typical use case where we need to reload the content of the work object that was already loaded in the AJAX container . Is there a way to do that OOTB . Also I dont see the option to "reload document" for the "open Assigment" action event but the option is available for "OpenWorkByHandle" action event . Was that a deliberate decision ?
Thanks for the response . Since we are in 8.1.4 and currently dont have any schedule in near future to upgrade to 8.3 , is there a function that we can use to close the "microdc" so that everytime a new document is created when we use "OpenAssignment" . I do see that Customer Service maintains the "microdc" name in a data page .
Hi Sreedhar, I have seen when two or workitems are opened in Ajax container tabs and if you try press cancel button on one of the items; the tab closes and other tabs become blank.
The same phenomenon happens when a workitem is opened in review harness and you press begin button.
If there is just a single tab then begin or cancel works fine.