Auto entry
In translations, the GUI auto-populates a default variable name to the
Variable field. For
example,you must create a new action within the ITERATE
, and use an address that uses the ITERATE
variable. When this is completed, the GUI fills in that ITERATE
variable from the basis ITERATE
.
For example, an iteration is on 0(0).ORU
.
The ITERATE
action should auto-populate the variable name to be %s1
.
In another example, a field is copied within that ITERATE
,
0(0).ORU.#2
. Clicking on that address in the tree
populates the repetition of the segment, so that it is 0(0).ORU(%s1).#2
.
When using %s1
for HL7 segments, the %s1
variable is populated. Inside the
ITERATE
, the input/output field automatically has %s1
in the address. This also works for
nestedITERATE
s.
For the ITERATE
action, Basis is auto-populated when you double-click a node
on the format tree. The Variable field value is set as %f1
,
%s1
, or %g1
for
different ITERATE
types.
For actions inside an ITERATE
, the Source and Destination
texts address content is auto-substituted with the correct Variable name of the parent ITERATE
action. This happens when you double-click any node within the ITERATE
basis.
In addition, if you manually update the Variable name for an ITERATE
action, all references to the old Variable name are updated automatically.
For some users, setting the basis and ITERATE
variables in
the ITERATE
action can be complicated. The Auto Entry feature helps by
decreasing the time to configure ITERATE
.