When checking the status of runs in TimeXtender you need to jump around between different dialogues to get to the bottom of an issue. The UX is rather lacking at the moment and could benefit from some quality-of-life improvements: please add the following fields/columns to logging dialogues across the products:
Orchestration package:
- Orchestration package triggering a Job
- Job calling an Ingest Task or Package that sets a status
- Ingest Task or Execution Package triggering a status
- In case of a task, the Data Source the Task belongs to
- In case of an Execution Package: the instance (and Data Area) the package belongs to
This would make it much easier to narrow down where to look in TDI after checking the logging from the Orchestration side, whether using Exmon DG client or browser or coming from a notification sent by Orchestration.
Job:
- Orchestration package triggering a Job
- Job calling an Ingest Task or Package
- Ingest Task or Execution Package triggering a status
- In case of a task, the Data Source the Task belongs to
- In case of an Execution Package: the instance (and Data Area) the package belongs to
Directly seeing the Task or Package setting a status, makes it much faster to jump to the place where action is required versus needing to read through a load of text to discover where to start looking will save a lot of time. Being able to click any of the fields and have the object open in the interface would really improve this. There are also some issues with the Job log dialogue itself:
- the dialogue is blocking, making it extra annoying to diagnose issues
- the error messages are cryptic: Ingest Instance <instance name>: The task <task name> CompletedWithErrors execution. It seems like there is an Enum name being passed directly instead of a descriptive string
Execution package:
- Orchestration package triggering a Job
- Job calling an Ingest Task or Package
- Ingest Task or Execution Package
- In case of a task, the Data Source the Task belongs to
- In case of an Execution Package: the instance (and Data Area) the package belongs to
- Steps within the Ingest Task or Execution Package
Similarly to Job logging, being able to click a field and jump to the object would much improve the user's experience. As this dialogue is not blocking it is not as disruptive as the Job logging dialogue
