·
Never considered in automatic actions directly. When release is
performed on any group, Count Only’s
are also processed if the group is currently held up in order to ensure they
remain so.
·
If valid DKDATADEF specified, counted up whenever a data record is
written (HAVEGOT is added to).
The user will
not be able edit the Lastaction field.
TGTACTION and MANACTION
fields dictate what to do, when quota targets are met, or the user is manually
adjusting the sample file. TGTACTION is the action to be performed when the
target is reached on Auto type quotas, and MANACTION the action to be performed
manually when the user confirms they wish to process actions but clicking on
the big tick ("Process Manual Quotas").
The button that currently re-counts the data will, after all the Havegots have been updated, set the MANACTION field as follows where each subsequent bullet point is an ELSE, and HAVEGOT includes ADDONEXPR :-
·
If the QUOTATYPE is not 0 (Count up), 1 (Auto) or 2 ({QUOTA...}),
nothing is set.
·
If the record is deleted, nothing is set.
·
If the sample file name does not match that in the SAMPLENAME field and
the SAMPLENAME field is not empty, nothing is set.
·
If MANACTION is not blank, nothing is set.
·
If QUOTATYPE is not 1 (Auto), MANACTION is set to LASTACTION.
·
If (HAVEGOT < TARGET) and LASTACTION is not HOLDUP or HOLDUPB,
nothing is set.
·
If (HAVEGOT < TARGET) and LASTACTION is HOLDUP or HOLDUPB, MANACTION
is set to RELEASE.
·
If LASTACTION is the same as TGTACTION, nothing is set.
·
MANACTION is set to TGTACTION.
Only type 0
(Count up), 1 (Auto) and 2 ({QUOTA...}) will be affected by manual hold up and
release from the Superwin program. If when the user
request actions to be processed and any other type of quota has an entry in the
MANACTION field they will be told “MANACTION field has entries on groups you
cannot manual process, clear these now?” Yes or Cancel will be the only
responses allowed.
When processing
actions, RELEASE is done first, then HOLDUP, and lastly HOLDUPB. The logic
(executed in the following order 3 times, once for each "PASS") on
each record will be:-
·
If the record is deleted no action is taken for this group.
·
If the sample file name does not match that in the SAMPLENAME field and
the SAMPLENAME field is not empty, then no action is taken for this group.
·
If the MANACTION matches our "PASS", then MANACTION is performed
on this group and the MANACTION field set to blank.
·
If a RELEASE has been actioned on the first
sweep, and this quota has HOLDUP or HOLDUPB in the LASTACTION field and
LASTACTION matches our “PASS”, then LASTACTION is performed on this group.
In order to
ensure that any released records that are about to be “reheld
up”, are not picked up by the sample control system before they are held up,
the system uses a limbo release and hold mechanism. This releases to status 7
(fresh) or 9 (appointment), does all the holds, and then any remaining 7’s and
9’s are set back to 0’s (fresh) and 2’s (appointments).
Clicking
on the exit cross will be the same, in terms of saving or ignoring changes to
the current record, as file-exit or the exit button.
If, when the
user attempts to close the Quotas window, there are any non-blank MANACTION fields
they will be prompted “Unprocessed action(s)” Process / Clear / Leave will be
the only options. Where Process acts as clicking on the big tick, Clear sets
all the MANACTION fields to blank and Leave continues to close the window.
The filter icon
will ‘or’ the Sampledefs of all the selected groups
and use the resultant expression as a filter for a Viewdbfwin
session which opens the Sample database. Only the Sampledefs
that are on quota records where the Samplename is
blank or is the name of the Sample file will be used.
If there were
no records selected, just the highlighted record will be used.