Refresh the folder in PTF if it throws a .Net exception during re-run of a test case

Tips for formatting issues in XMLP

Hi, I have the below observations regarding formatting and alignment issues that i have frequently faced. I will keep this updated!

1. Leave at least one empty line at the beginning of the document. This will help you to understand the page margins when you place the cursor there. Then you need to align your tables with the margin.
   
2. If you want to expand the table, FIRST go to empty line and expand/adjust the page margins and THEN the table margins  . With these alignments, any custom table should show up as-is without any problem
   
3. If two tables seem to have stuck to each other, try marking the below table's text wrapping as "Around" and you can drag it out and place at a desired position
   
   
4. It is best if you wrap the full document as a repeating group with For-each of the topmost parent node (here , disciplinary action)
   
5. Any bullet item pushed off by extra spaces(even though in the template it doesnt seem to have any), place the cursor in the begin of the bullet and hit backspace sufficient times(you wont see anything getting cleared) till you see it right in the preview
   
6. For checkboxes, first go to Developer tab and switch on the "design mode". Always insert ONLY 'Legacy" checkbox. NEVER "Active" ones:
   
   
7. Also if you want to see the checkbox, associate it with some dummy tag. For example:
   

Size of a laptop bag means WHOLE size!! not screen size...

Committed a basic blunder sans common sense..Misunderstood the size mentioned on a tag of a laptop bag for the screen size...while it actuallu means the corner to corner diagonal dimension....Another thumb rule is we can add 2'' to our laptop's screen size and search for that size...

Quick Finds

•  Secondary Pages:
• Secondary page should be included on the Main Page to link its records with the Parent page's Records
• If OPRID is one of the key fields, place the peoplecode to ensure it is populated(..donno why..others fields take values from their parent records..Most of the delivered sec.pages also do the same)
• <your record>.OPRID = %OperatorID
•  A secondary Page with just a Close/Return Box will not update any of its records in the Component buffer bu itself. For this we need to choose the Secondary page to be of "OK/Cancel Button"; OK would update the Component Buffer and Cancel will not.
  Eg: If the secondary Page (with OK/Cancel) has a Grid, any row changes would not show up when we click cancel and return to the Main (Standard) Page. 
• Secondary pages can be nested.
• Peoplecode:
•  There are two places for peoplecode because the if the event code is to be same in any component it is used, it would be in Record Peoplecode. Likewise if we reference some Component specific peoplecode, then place it in component peoplecode to restrict to that component