Question

2
Replies
189
Views
MGR007 Member since 2008 54 posts
Incessant Technologies
Posted: April 7, 2016
Last activity: April 7, 2016
Closed

Dynamic Repeating Layout  - Automation script failures

Hi,

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.

Pega Customer Service User Interface
Moderation Team has archived post
Share this page LinkedIn