A despatch file that arrives days after its newest record can leave a case looking as if nothing went out in that time. The starter rule Review a late file makes a new investigation policy: when a file from one source arrives later than you allow, LotTrail runs a saved investigation again and raises a coverage review on a case for a person to check.
Use the starter rule
You need the Author role, a second factor from the last five minutes and a grant on every dataset involved. You also need a saved current-evidence investigation and an open case whose datasets you read. Starter rules are not offered in the sample workspace. The card makes an editable draft: nothing runs until the draft is proved and a Reviewer releases it.
- Open Automation policies. Under Starter rules, the cards come before Start from a saved investigation.
- Find Review a late file. It is under Late and incomplete files; you can also type a word from its title in Search starter rules and Help.
- Fill in the blanks in the card's sentence, "When a file from … arrives more than … days after its newest record, rerun … and raise a coverage review on the case …":
- Source: one of the datasets you read, such as Elland despatch.
- Days: a whole number of days from 1 to 365. The card starts at 2.
- Saved investigation: a saved current-evidence investigation, such as the forward investigation from material lot R-4471.
- Case: an open case, such as R-4471 customer query.
- Choose Use this rule. The button waits until every blank has a value.
LotTrail checks the card again against your current records and access, then makes the draft, as Create policy draft makes one. It is listed under Editable and frozen drafts, and under the gallery Draft started from Review a late file names it and its policy. Its first revision's note names the starter rule and its version. No AI is asked, and nothing is released.
What the policy does
The draft is a new policy for the decision whether a coverage review is raised, and the saved investigation run again. It reads the saved investigation's datasets, the case's datasets and the source you chose, and names the case. Its freshness limit is your number of days.
When a file from your source is accepted, LotTrail measures from the newest record the file covers to the moment it is accepted. If that is longer than your number of days, it runs the saved investigation again, saved beside the earlier runs rather than replacing them, and raises a normal-priority coverage review on the case, listed under Policy review tasks. A file that is on time, or a late file from another source, does neither. The review never holds, recalls or changes anything.
The policy reruns the investigation as well as raising the review because every LotTrail policy runs at least one saved investigation, and its proof needs an example that runs it. Both follow the one condition on the card.
Add the example that runs the investigation
The draft carries the examples LotTrail can state for the records you chose, written with your source's own identity: a file from your source that arrives on time and, where the policy reads another source, a late file from that source. None of them runs anything. Before review, add an example of a late file from your source, which runs the investigation and raises the review, with the records you expect the saved investigation to find. LotTrail never works those records out for you: they are your independent check, and the proof compares the run's actual records with them. Where SmartFACT Automation is connected, choose Open in Automation on the draft and enter the example there. Read the stated examples too, and change any whose facts do not suit your site.
Release it
Where SmartFACT Automation is connected, the draft is edited, proved and sent for review there, as every draft is. The native proof runs every example against today's evidence and needs each rule to match one example and miss another. A Reviewer independent of the draft's contributors approves the examples and the release, with a recent second factor. Until then the policy does not run. Without a connected Automation workspace the draft waits on this page.
If the card is refused
- This starter rule card, or a record it names, has changed since the page was read: a dataset was held, a grant or a case changed, or the starter itself changed. Read the page again and fill in the card once more.
- A policy reads at most 20 datasets, and the investigation, case and source you chose name more: choose a narrower investigation or case.
- A second factor from the last five minutes is needed: sign in again with your second factor and use the card again.
Change or stop it later
Nothing about a starter rule makes its policy permanent. Once released, a Reviewer can retire it at once on Automation policies, roll it back to an earlier version or bring a retired version back, and an Author can start a draft from any released version to change it. A starter rule that changes later changes no draft or policy it already made.