Module printing with RRDG is numbered incorrectly in output documents
We have several modules in RRC 4.0.5 that have various levels of nesting. Some of the items number themselves correctly in their section of the module, each line being 1, 2, 3, etc. However, when generating a document, the spacing between the items is increased. The output docs pick up that these lines are supposed to be part of a numbered list, but the spacing separates them into different lists, so each are labeled 1, 1, 1.
If any of these list items have sub-lists, the sublists are numbered correctly, but the top level list items remain independent and incorrectly numbered. I would have suspected an output template being the cause, but this behaviour is expressed in all output types (PDF, Word, HTML) and happens with sophisticated or performance formatting.
Accepted answer
I believe you have hit the limitation of specifying start point for numbered list.
When adding numbered list, you can specify the start numbering property which will allow you to show the proper numbering in the artifact. In the source code of the artifact, you would see something like:
ol start="2" style="font-size: 12pt;"
xxxxx
/ol
Here the start numbering is "2" and it will show 2 in your list.
During export, all these type of numbering will change to 1 because RPE (where RRDG template is from) does not support this property in 4.0.5.
The good news is that from 4.0.6, RRC adopts newer version of RRDG 1.2.1 which starts supporting this start=x property.
When adding numbered list, you can specify the start numbering property which will allow you to show the proper numbering in the artifact. In the source code of the artifact, you would see something like:
ol start="2" style="font-size: 12pt;"
xxxxx
/ol
Here the start numbering is "2" and it will show 2 in your list.
During export, all these type of numbering will change to 1 because RPE (where RRDG template is from) does not support this property in 4.0.5.
The good news is that from 4.0.6, RRC adopts newer version of RRDG 1.2.1 which starts supporting this start=x property.