We hava a callcenetr application designed using CSI FW. In Interaction Composite section we have a tabl called Coverage Tab where system display list of Coverages. It is not simple list, rather each each coverage is showed with lot of details and subsections. So we are using Repeating Dynamic layout UI element to impliment this, functinality is working fine, but problem is Automation Scripts are failing to navigate/identify to Each coverage list sections. When we analysed, we obserevd that for Repeating Dynamic layouts HTML Pega is using <Div> tag but no <table> <tr> tags for each row. So Automating tool is idenetifying each record in Repeating Dynamic layout as WebElement ( last element of Object Hirerachy). Because of this Automation tool is not able to identify this as WebTable objects so it cannot traverse inside section details.
We have a other tab called Plan tab, where we have similar plan list, but here we shows very limited information. So in this we are using Repeating Grid UI element. For this Pega HTML is adding <table> <tr> html concept. For this Automation tool can able to read each element as WebTable object in there Object hirerchy so it can travers all elements inside WebTable as WebElement succesfully.
Now we thought to change to Repeat Grid instead of using Repeat Dynamic Layout but this coverage details has so many inner section and we have some difficulty in presenting this big section in Repeat Grid rather Repeat Layout is better choice.
Now the questions is, to solve Automation script roadblock, is there a way Pega team can help to add <table> <td> concept to Repeating Dynamic Layout as well. Idially any Repeating list should have been like this.
Please help with possible alternatives. We are in last stage of QA testing and we dont want to change to much code for this.
Repeating Dynamic Layout is Div based to enable the layout to be more fluid and responsive. Making it Div based allowed us to provide lot of OOTB formats like stacked, inline, inline grid double and inline grid triple.
Think of RDL as a container which is repeating another container (section include) so even semantic wise RDL is not displaying tabular data unlike grid which is displaying data from multiple columns. This is also one of the reason for choosing div over table tag for generating RDL.
One alternative which I could think of is having a 100% grid with single column(section included) but seems like you have already exhausted this option from your end.
Is there any way of fixing the automated script for RDL at your end ?
Hi Sathish.. Thanks for your response. I understand what you are saying but now i was asked by Customers to get some solution around this.
I already explored Repeating Grid.. we are facing seprate challanges there regarding section jumping up and down and some collapsible sections inside grid need two clicks to expan (one click to bring that recod in focus and next click is actually expaning collapsible section). I raised SR for this, but didnt get solution