Ability to set column headings and number of columns dynamically

Standard RPE usage is to build a table header row, then iterate through data and build rows one at a time. 

This usage assumes I, as the template author, no exactly how many columns I will have in my table before I build the table.

The out of the box printModuleTable.dta that ships with DOORS Next gets around this by counting the number of fields in the view that's exported. That's great.

But in a case where I want to go down X link hops and put each hop into its own column, if I don't know what X is until after I'm done with the table, well, we have a problem.

The point of this idea request is to allow me, as a template author, to essentially insert an entire column onto my table after I've passed the header row. So in the middle of my table logic, after the header row has been set, I should be able to add a new column (not just a new cell in a given row where the previous row had 4 cells but this row now has 5, but the entire column) and I should have the ability to set the name of the column header while I'm in the middle of the table logic.

I have a client right now that wants me to report on link hops from the top to the bottom in DOORS, but instead of just hops in each column, they want the links separated by columns based on what source module they end of the link is in.

So if Module A links to Modules, B, C, and D, then the report is run from Module A, and then for each link if the link goes to Module B, I put it in the column for Module B. If it's in Module C, I put it in to Module C, etc.

Again, I would have to know this information before rendering the table, which I can do by building a custom java object/json structure and then rendering the table based on that, but that's much more complicated to maintain and transfer ownership of the template to -- at that point it might be easier to write a python script, when the goal is to use RPE.

Instead, when I create a cell in a row, that cell could have a property that states it's a new column (true/false) that can be set dynamically, as well as column title that could be set dynamically. Boom, done.