Case Tracker¶
Case Tracker lets someone outside the process follow a case. The person is not a user of the platform: they open the tracker, enter the case code and its PIN, and see only what the process decides to show.
What the visitor sees¶
The tracker opens with two fields, CASE and PIN. After that it shows the parts of the process that were enabled for tracking:
| Part | What it shows |
|---|---|
| Process Map | The whole diagram, with the status of each task |
| Routing history | The steps the case has gone through |
| Messages history | The emails and messages the case has produced |
| Documents | The input and output documents enabled for tracking |
Nothing else is reachable: the tracker has no search across cases and no access to other processes.
Configuring it¶
Open the process and choose Case Tracker. The window has three checkboxes:
| Option | Values |
|---|---|
| Processmap | On or off |
| Routing History | On or off |
| Messages History | On or off |
The configuration applies to every case of the process.
The code and the PIN¶
Each case gets a code and a PIN. They are created when the case starts and can be
changed from a trigger: setCaseTrackerCode() sets the code and the PIN for a case, so
a process can send them by email or print them on a receipt.
A PIN is a short secret. If it is shared too widely, the case is visible to anyone who has it; change it when the audience changes.
When to use it¶
- A customer waiting for a claim, who should see how far it has advanced.
- A supplier who must know whether the order was approved.
- Any audience that needs status, never the ability to act.
If the person must also submit something, they are not a tracker visitor: use a web entry or an action by email.
Related¶
- Events — the start event the configuration hangs from.
- Web entry — a public form that starts cases.
- Actions by email — letting someone act without signing in.