Activity History
- Megan Stanage (Unlicensed)
- Megan Stanage
Analytics
Logistics Execution > Common > Activities > Activity Maintenance > Activity History
This form can be accessed from the ribbon on Activity Maintenance, Activity Workbenches, Load Building Workbench, and Activity Scheduling.
The Activity History form displays logs of actions and status changes for paired resources.
Header
| FIELD | DESCRIPTION |
|---|---|
| Activity | The related activity. |
| Worker | The related worker. |
| Stop | The sequence number and the address. |
| Work ID | The work ID. |
| Action Succeeded | Turn on this toggle to indicate that the action completed successfully and without error. |
| Action Overridden? | Turn on this toggle to indicate that the action was overridden. |
Buttons
| FIELD | DESCRIPTION |
|---|---|
| Inbound Process Queue | Click this button to open the Inbound Process Queue, which displays a history of macros executed for the activity. |
| Show Auto Action History | Click this button to add auto action history to the displayed history. |
| Activity History List View | Click this button to open the Activity History List View form (see below). |
| View Error Log | Click this button to view captured failure messages. Note This button is only enabled for failed actions. |
Activity History List View
Logistics Execution > Common > Activities > Activity history list view
This form can be accessed via the Activity history list view button in the ribbon of the Activity History form.
The Activity History List View form displays the activity history in a list.
| FIELD | DESCRIPTION |
|---|---|
| Action Succeeded | A checkmark indicates that the action succeeded. |
Activity History Mark Successful Job
Logistics Execution > Periodic > Activity History Mark Successful
This job marks records as successfully completed.
Use the activity histories filter to select records to mark, or set the job to run in batch.
Important
It is highly recommended that existing systems run the Activity History Mark Successful job to update existing data. If the job is not run, issues may occur.
