Processing Sequence

The sequence in which the level-one sections of the report appear in the RDA workspace determines the process flow of the level-one sections. For example, if a report has multiple level-one sections and each has its own business view, then the first level-one section executes before the next level-one section executes. Any level-two sections that exist between the level-one sections are processed when and if they are called from a level-one section. If the report includes a subsection join following the level-one sections, which creates a parent/child relationship, then the parent/child sections are processed independently of the first level-two section.

If level-one sections are moved within the report template, the execution sequence is affected. In report processing, the system processes all level-one sections in the order in which they appear. Level-two sections, however, are processed as dependents of level-one sections. Moving conditional sections, subsections, level break sections, page headers, page footers, and report headers does not affect the sequence of execution. Report execution takes place from top-to-bottom for sections; and from top-to-bottom and left-to-right for objects within a section.

The system reads and processes all records in a section from beginning to end based on the defined data selection. If you do not specify data selection, then the system reads all of the records in the table until it reaches the end of the file.

Note: Data sequencing and data selection defined at runtime affects only the first level-one section of the report or batch process. Therefore, when you design a report or batch process, consider how users will be affected since they cannot easily change data selection and sequencing for additional level-one sections.A level-one section is executed at least once whether or not it has a business view attached to it. Consider this fact in your decision to execute special event rule logic using the Do Section event of that section.