This topic has been locked.
15 replies Latest Post - 2012-08-29T14:10:59Z by MerlinUK
Pinned topic Recursion in Rhapsody
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
What are the tricks to getting recursion to work in a Rhapsody template ?
Updated on 2012-08-29T14:10:59Z at 2012-08-29T14:10:59Z by MerlinUK
Dragos.Cojocari 270001QUCG1606 Posts
SystemAdmin 110000D4XK1299 PostsACCEPTED ANSWER
Re: Recursion in Rhapsody2010-03-22T19:07:26Z in response to Dragos.CojocariHello Merlin,
RPE and rhapsody seemed to work fine for me and its a degree of magnitude faster (probably more) than reporterplus.
I suggest you do what I did and download Dragos's example and then pick a particular reporterplus template and reproduce it in rpe, you need to watch out for where you put your filters (use native rhapsody filters) and you need to mimic the exact context using containers/ tables and rows (this is easy to get wrong). I remember getting caught out with the context a couple of times.
There is a little bit of a learning curve with RPE and it is easier to use with DOORS than with Rhapsody, but (for me anyway) it beats reporterplus hands down and I think repeated use will make it a lot faster.
Our rhapsody consultant stated that rpe was buggy, but it has worked fine for me so far limited testing, but I migrated a fairly complicated reporterplus template succesfully.
I think an automatic reporterplus to rpe migration tool would be nice and is possible, but probably a fairly difficult proposition, this would however speed up the learning curve and rhapsody user take up massively.
<Dragos> Any plans for this?
Dragos.Cojocari 270001QUCG1606 PostsACCEPTED ANSWER
Re: Recursion in Rhapsody2010-04-06T05:15:20Z in response to SystemAdminHey Richard,
>> Our rhapsody consultant stated that rpe was buggy, but it has worked fine for me so far limited testing, but I migrated a fairly complicated reporterplus template succesfully.
Well RPE is new and uses very different concepts compared to older tools such as ReporterPLUS, DocExpress, SODA etc. But some users sometime approach it with the same mindset and patterns as they did older tools and that doesn't work well obviouslly. We strongly recommend learning RPE and not trying to use it as a reloaded DocExpreass/SODA/ReporterPlus. :)
>> I think an automatic reporterplus to rpe migration tool would be nice and is possible, but probably a fairly difficult proposition, this would however speed up the learning curve and rhapsody user take up massively.
We are considering a ReporterPlus->RPE migration utility but it is something for 2011 and beyond.
purban 270001P4BH1 Post
Re: Recursion in Rhapsody2010-08-11T21:32:25Z in response to MerlinUKIf someone could post a very simple template showing recursion in Rhapsody that would be great - doesnt have to be much - just a container that recurses over the package structure and prints out the name of the package would be all i need - i still cant get it working
Re: Recursion in Rhapsody2012-08-23T20:13:49Z in response to MerlinUKHi
Did anyone create the RPE & Rhapsody recursion template. Playing with the recursion levels & segments at the pacakge and project lvel. Not having much luck. Using Rhapsody 18.104.22.168 and RPE 1.1.2. Already lloked at the tutorial that really doesn't explain well (as it does not work :).
One other issue i have is all the pacakges are output the correct information (without recursion ) but the first pacakge seems to be down in the weeds (3 level nesting), the top level package is output somewhere in the middle?
Regards Mick Driver (BTI)
firstname.lastname@example.org or email@example.com
Re: Recursion in Rhapsody2012-08-29T13:57:58Z in response to MerlinUKHi
Got the recursion to run, outputs the correct list. Now working with IBM RPE support to dynamically set header styles depending on level during the recursion. Apparently there is a variables that internally tracks the level you are at called "_element_level". Think we can use this some how ....