Slide 1 -
Slide 1
Slide notes
This Report example uses a Unit to produce the
unpredictable number of Transaction lines, because the number of Transactions
lines may be different each time the Report is performed and depends on the
data selection as chosen by the User.
Slide 2 - Slide 2
Slide notes
A Unit is either based on Data Iteration within a
single Record, or else it is based on Iteration Keys from a selection of Data
Records. In this case, the Unit uses Iterated Record Keys that are selected by
a Data Selector.
Slide 3 - Slide 3
Slide notes
We are using a Report from the system Example
series.
Slide 4 - Slide 4
Slide notes
Slide 5 - Slide 5
Slide notes
When we use a Unit that is performed on the basis
of a Data Selector, then the Data Source on which the Data Selector and the
results are based will always be listed, together with the Data Selector to
use.
Slide 6 - Slide 6
Slide notes
Slide 7 - Slide 7
Slide notes
Slide 8 - Slide 8
Slide notes
The 1st Tag in the Unit Group of Tags will be the
Tag that calls the Unit.
Slide 9 - Slide 9
Slide notes
And in this case, it will use the Template for Unit
Execution based on a Data Selector.
Slide 10 - Slide 10
Slide notes
Slide 11 - Slide 11
Slide notes
We need to state the Unit to perform, and also the
Data Source.
Slide 12 - Slide 12
Slide notes
Slide 13 - Slide 13
Slide notes
Slide 14 - Slide 14
Slide notes
Slide 15 - Slide 15
Slide notes
Slide 16 - Slide 16
Slide notes
When we perform or test the Document, then the Data
Selector will pop up with runtime prompts.
Slide 17 - Slide 17
Slide notes
Slide 18 - Slide 18
Slide notes
Slide 19 - Slide 19
Slide notes
In this case, the Data Selector allows us to choose
a Purchase Order Number pattern.
Slide 20 - Slide 20
Slide notes
And this is followed by a Transaction Selection.
The results of the Data Selection are the Transaction Keys that are passed to
the Unit for execution.
Slide 21 - Slide 21
Slide notes
Slide 22 - Slide 22
Slide notes
Slide 23 - Slide 23
Slide notes
Slide 24 - Slide 24
Slide notes