> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2023.3-changes-overview/new-data-capture-options.md).

# New Data Capture Options

## Overdue Information

We've added the following data capture options to provide more detailed information about work items that are overdue:

* Is Overdue - this shows whether the SLA of a work item has been breached or not.
* Overdue By Days - this shows how many days or working days (depending upon the due date configuration) the work item is overdue by 
  * A value will only show if the work item is overdue
  * This value is determined by calculating the difference between the due date and the current date
  * The overdue days for running work items (i.e. Work Items in a state of Draft, To Do, In Progress or Wait) will be displayed in ranges of 'Less than 1', '1-2', '2-3' etc. up to '6-7'. 
  * Running work items which are overdue by more than seven days/working days will  show as being overdue by '7+' days/working days. 
  * For resolved or closed work items, the number of days overdue will be exact e.g. '10-11'
  * Note that the value is calculated by the engine once in a day (possibly at midnight).

{% hint style="info" %}
This data is calculated based on the due date of the work item. Therefore if the due date of a work item changes, this might lead to the information in these overdue fields changing as well.
{% endhint %}

This data is available in:

* the homepage grid to use as columns
* the [Advanced Search page](/whats-new/older-versions/changes-overview-older-versions/2023.3-changes-overview/views-page-enhancements-and-new-export-views-to-excel-feature.md) 
  * to create Advanced Search views
  * in the Advanced Search results grid to use as columns
  * in the Advanced Search results grid to group search results (note that only the 'Is Overdue' option can be used for this)

We have also added an Overdue By Hours option that will only appear in the Advanced Search results grid to use as a column. This shows how many hours or working hours (depending upon the due date configuration) the work item is overdue by. As for Overdue By Days, a value will only show if the work item is overdue. Note that the value is calculated by the engine once in a day (possibly at midnight).

## Initial Request Start Date/Time

We've added the option to capture the initial request start date and time for work items to help improve SLA calculations by allowing you to capture the entire length of time it has taken to complete a request, as opposed to just the length of time an individual work item has been being worked on.

This will be shown as a additional field on a work item's info card if the initial request start date is different to when the work item was created. 

The Initial Request Date can also be used to organize work in the homepage grids, for creating Advanced Search views and in reporting.

This data has also been added as a new due date method:

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FXSj3ag0TZvnyxfQo0tmx%2Fimage.png?alt=media&amp;token=ff8523d6-11d4-420c-878d-9e02ea1f87fd" alt=""><figcaption></figcaption></figure>

This data is useful in scenarios where a further work item needs to be created from an original request e.g. when a Sub Case is created, when a Ticket is converted into a Case, when a Case or Action gets reworked, when an Action is created via the 'Start Action' option, when a new linked work item is created or when an email comes into a closed work item which triggers a new one to be created to continue that original request.

{% hint style="info" %}
Please note that this additional information is now being captured for all situations with the exception of split Tickets, where the very original start date of activity was always being captured in the 'Created On' field. In a future release we will standardize so this date is also captured in the same 'Initial Request Date' for split Tickets also
{% endhint %}

For example, if a request comes in that generates a Ticket on the 12/1/2023 at 09:00, both the existing 'Created On' date/time and the 'Initial Request On' date/time for that Ticket will be 12/1/2023 at 09:00. And because both dates/times are the same, only the 'Created On' date/time will be shown.

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FuUEniRSnTI81pWRu2B0n%2Fimage.png?alt=media&amp;token=ce512ada-0913-4c1a-ac20-5cf05f519b35" alt=""><figcaption></figcaption></figure>

If it becomes apparent once someone has started working on the Ticket that the Ticket then needs to be converted into a Case and they then convert the Ticket into the necessary Case, the 'Initial Request On' date/time for the newly created Case will also be 12/1/2023 at 09:00 i.e. it will capture the start date/time of the original Ticket (and request). However, the 'Created on' date for the newly created Case will be later, for example 12/1/2023 at 11:00. And because both dates/times are different, both the 'Initial Request On' and the 'Created On' dates/times will be shown.

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2F2g9zqlCgoGWHeWoLsmVF%2Fimage.png?alt=media&amp;token=4edd1849-e235-4280-b4e6-883797485851" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Additionally, there will be no impact on the Initial Request On date when linking existing work items as a new work item is not being created.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2023.3-changes-overview/new-data-capture-options.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.