What is the Card Events report?
The Card Events report tracks all actions performed by license users on kanban, extra cards, and worklists. Actions performed by users of linked licenses (both suppliers or customers) are not included.
For each action, the table shows the initial state (Initial Status and Scanned String), the final state (Occurred event and Final String), and the action that triggered the transition from one to the other (Triggering action).
The table also shows the Result of the operation and the Message to the user.
The following actions are tracked:
- Card status changes;
- Card blocking and unblocking;
- Card quantity changes, which are reported in the Message to the user column;
- Flagging a card as urgent;
- Flagging a card as out of stock;
- Workflow execution.
This report provides visibility into the Source that performed tha status change.
The Source includes:
| Type | Description |
|---|---|
| Automatic | These are intermediate and optional status changes, performed automatically by the system. |
| Board | Status changes are performed through the browser, using widgets or directly from the board. |
| API | Status changes are performed through integration with the management system. |
| Android, iOS, … | Status changes are performed using the app. |
| Documents | Status changes (In transit/Full) are performed through the Documents module. |
| RFID | Status changes are performed using RFID technology. |
| Inventory count | Status changes are performed during the inventory count. |
By default, the table is filtered to display only card events with a successful outcome (non-empty Occurred event) and referring to the current date. As a result, events that ended with an error are not shown by default but they can be displayed by adjusting the table filters.
Comments
0 comments
Please sign in to leave a comment.