Events in a Dimensions integration are triggered by actions such as changes to an assignment, a staffing record, add/edit/delete codes, switch mode, trades, and so on. The system status Event tab captures event activity.
| Field | Description |
|---|---|
| Event Processor Status | Displays the current status of the event processor. A Running status indicates events will be sent to Dimensions. A Stopped status indicates events will not be sent to Dimensions. |
| Event From | Displays the range of events in Event From and Event Through values supplied. Event From targets the timestamp of the event processed. For example, an employee submits a vacation request on March 12, 2019 for April 5, 2019. The Event timestamp is March 12, 2019. Download Report Format: YYYY-MM-DD 00:00:00 |
| Event Through | Displays the range of events in Event From and Event Through values supplied. The Event Through targets the timestamp of the event processed. For example, an employee submits a vacation request on March 12, 2019 for April 5, 2019. The Event timestamp is March 12, 2019. Download Report Format: YYYY-MM-DD 00:00:00 |
| Status | Filters the events by Status. Click the Apply
button to return the Status query selected. Choices are:
|
| Apply | The Search button returns the events by the status selected. |
| Resubmit | Used to resubmit an event, such as an event that failed. |
| Audit | Used to review the state of an event, such as New, Failed, Success. Displays event timestamp with server timezone notation irrespective of the institution timezone in focus. |
| Mark as Failed In-Progress | Resubmits events stuck in an In-Progress state.See Mark as Failed section below. |
| Current Institution Only | Limits the Institution column by the focus institution. Function visible when an institution is in focus, and when Institution Focus is enabled; not visible in None focus. |
| Search | The Search grid box is used to quick find and limit events displayed on the grid using text. |
| Event ID | A unique identifier for the event. Drop-down
options:
|
| Status | Indicates the Status of the event. Same as filter Status. |
| Last Modified | The event timestamp with server timezone notation irrespective of the institution timezone in focus. Format: MM/dd/yyyy HH:mm:ss zz |
| Schedule From | Schedule From denotes the timestamp of the staffing record. For example, an employee submits a vacation request on March 12, 2019 for April 5, 2019. The schedule from timestamp is April 5, 2019. Format: YYYY-MM-DD 00:00:00 |
| Schedule Through | Schedule Through denotes the timestamp of the staffing record. For example, an employee submits a vacation request on March 12, 2019 for April 5, 2019. The schedule from timestamp is April 5, 2019. Format: YYYY-MM-DD 00:00:00 |
| Retry Attempts | The number of times the selected event attempted to push to Dimensions. |
| Task | The name of the task type. Located in Setup
> System > Task Manager. Note:
A blank cell in the Task column denotes a Schedule Import. A message in the cell denotes a Schedule Batch Import. |
| Institution | Displays the person’s home institution at the
time the event is recorded. Institution output applicable to Dimensions Batch and Low
Latency events as well. The institution name for legacy events
prior to feature release are not displayed. Available as of application
version 7.3.2. Note:
Viewing or resubmitting an event after a person has moved institutions will not change the output on the status page. The institution will not change as a result of the institution on the person’s general information being reassigned. |
| Message | The error message with general details about the run results. |
Events stuck in In-Progress for a period of time may be marked as Failed and resubmitted as of as of application 7.1.14+, 7.2.5+, and 7.3.1+. The event must exceed X minutes to be marked as failed, where X is a configurable value, denotes minutes, and must be a value greater than or equal to one in order to display Mark As Failed functionality on the Events tab.
To enable this functionality, use the following property available in the integration.properties file:
* schedule.event.ui.failed.threshold.timeInMinutes=30Using the example above, X = 30, this means the Mark As Failed function displays on the Events tab, and enables when an event has been running in a state of In-Progress for more than thirty minutes.
* schedule.event.ui.failed.threshold.timeInMinutes=0* schedule.event.ui.failed.threshold.timeInMinutes=Events stuck in In-Progress for a period of time can also be automatically marked as Failed as of application 7.3.2+. To allow the application to automatically set the event state to Failed, use the following property in the integration.properties file:
* schedule.event.processor.failed.threshold.timeInMinutesIf minutes equals 0 (zero) or Blank the application will not automatically mark an event as Failed. Default is 240 minutes.