Due Date Flavours
Last updated
Was this helpful?
English
Last updated
Was this helpful?
In addition to Name and Description, Due Date flavours are made up of the following attributes:
Setting
Description
Due Date Method
Adjust by
Add or subtract a specified number of hours/working hours/day/working days (including minutes) from the starting date determined by the Due Date method selected, e.g. the Case start date.
Advanced
If set, further options are available (see following section)
Calendar
If using working days / hours, you need to specify which calendar to use for the calculation. This can either be the supplier / customer calendar linked to the contract (there must be one if you select this option), or a standard system calendar.
Relevant only for working hours / days.
Add Wait Time To Due Date
If set, stops the SLA clock whenever the item is put into a waiting state.
Move To Next Morning If End Of Day
If set, once the due date/time has been calculated, the time will be pushed to the first working moment of the following working day (This allows you to set a calculated Due Date of '5pm Friday' to be '9am Monday', assuming working calendars are set accordingly).
Move To End Of Day
If set, once the due date/time has been calculated, the time will be pushed to the end of the calculated day.
Clicking on Show Activity button in the ellipsis will show you the activity history of the Due Date Flavour. You can see when the Due Date Flavour was created and by who, as well as if any edits have been made to the Due Date Flavour, when they were made and by who.
There are several Due Date Methods available which allow you to set the start point for calculating the desired SLA for an activity. There are more Due Date methods available.
Watch the following video to find out about the due date methods that re available when configuring Tickets:
Method
Notes / Further Variables
First Day of Current Month
Fixed Day of Current Month
Set a specific day, e.g. ‘14’
Fixed Day of Fixed Month
Set a specific day and month, e.g. ‘14’ and ‘3’. Please note that if the month and day configured using a 'Fixed day of fixed month' due date method on a Case/Action/Ticket is earlier than the work item's start date, then the system will assume that the Case/Action/Ticket is due in the following year. For example, if the fixed day of fixed month value configured in the due date of a Ticket is 14th March 2022 but the Ticket's created/start date is 16th July 2022, then the system will assume that the Ticket's due date will be 14th March 2023.
Fixed Day of Fixed Month of Work Item Start Year
Sets a specific day and month and year. The year is calculated as the year the work item was started.
It is different to the already existing 'Fixed Day of Fixed Month' due date method as it will set the due date of the work item as the same year as when the work item get started. For example, if a Ticket's due date is 14th March 2022 but the Ticket gets started on 16th July 2022, then the system will assume that the Ticket's due date is the same year as when the Ticket was started, so it will assume that the Ticket's due date is 14th March 2022.
From a Custom Date Time Field
If any field of type Date Time is linked to the work item configuration, you can select it here. At run time, when this value is set / changed, the Due Date will be calculated.
From Packet Start Date
The date the Ticket was first created.
Initial Request Date
If a further work item has been created from an original request (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 or when a new linked work item is created), this due date method captures the start date of the original request, 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.
Last Day of Current Month
Additional Due Date methods are available when setting Due Dates for Cases and Actions, as schedules and parent work item / sub-work items data can be used. Watch this video to find out more:
Method
Notes / Further Variables
First Day of Current Month
First Day of Month from Explicit Schedule Date
Requires a Schedule linked to the Case. Supply a Schedule Date, e.g. “Key Date 1”, “Key Date 2” etc. from the dates list.
Fixed Day of Current Month
Set a specific day, e.g. ‘14’
Fixed Day of Fixed Month
Set a specific day and month, e.g. ‘14’ and ‘3’. Please note that if the month and day configured using a 'Fixed day of fixed month' due date method on a Case/Action/Ticket is earlier than the work item's start date, then the system will assume that the Case/Action/Ticket is due in the following year. For example, if the fixed day of fixed month value configured in the due date of a Case is 14th March 2022 but the Ticket's created/start date is 16th July 2022, then the system will assume that the Case's due date will be 14th March 2023.
Fixed Day of Fixed Month of Work Item Start Year
Sets a specific day and month and year. The year is calculated as the year the work item was started.
It is different to the already existing 'Fixed Day of Fixed Month' due date method as it will set the due date of the work item as the same year as when the work item get started. For example, if a Case's due date is 14th March 2022 but the Case gets started on 16th July 2022, then the system will assume that the Case's due date is the same year as when the Case was started, so it will assume that the Case's due date is 14th March 2022.
From a Custom Date Time Field
If any field of type Date Time is linked to the work item configuration, you can select it here. At run time, when this value is set / changed, the Due Date will be calculated.
From an Explicit Schedule Date
Requires a Schedule linked to the Case. Supply a Schedule Date, e.g. “Key Date 1”, “Key Date 2” etc. from the dates list.
From Packet Start Date
The date the Work Item was first created. Important note: for Actions this means this would be from the beginning of the Action, not its parent Case. If you wish to drive an Action’s Due Date from the Case, use ‘From Parent Packet Start Date’.
From Parent Packet Due Date
For Actions, the date its parent Case is Due
From Parent Packet Start Date
For Actions, the date its parent Case started
From Schedule Date Linked to Step
Requires a Schedule linked to the Case. Requires a Schedule Date e.g. “Key Date 1”, “Key Date 2” etc. from the dates list to be set for the Step this Action appears in.
Initial Request Date
If a further work item has been created from an original request (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 or when a new linked work item is created), this due date method captures the start date of the original request, 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.
Last Day of Current Month
Last Day of Month from Explicit Schedule Date
Requires a Schedule linked to the Case. Supply a Schedule Date, e.g. “Key Date 1”, “Key Date 2” etc. from the dates list.
An advanced option has been enabled for Due Date rules which allows for the use of Custom Data variables when setting time adjustments. Enabling the Advanced option when setting a Due Date rule will display an additional set of options in the ‘Adjust by’ section.
This will allow you to add / subtract a certain number of Hours/Days/Working Hours/Working Days by selecting from a dropdown of numeric custom data fields.
The due date method ‘From a Custom Date Time Field’ allows configuration of rules which allows end users to supply the base date/time value for the Due Date for the rule via a custom data field at runtime, when submitting a Case or Action. The custom field must be of type ‘DateTime’.
At least one Enate custom data field specifically of the date time type.
An Enate Custom Card must be configured with the aforementioned data field.
This card must be configured on the specific Action or Case you wish to set this rule for.
The end result of this functionality is to allow direct adjustment of Work Item due dates by modifying custom data field values, i.e. setting a value on a card..
..modifies the Work Item due date:
This is only available when a unit of 'working hours' or 'working days' has been selected.
If this flag is set, whenever the due date calculation results in a value that would have been the very end point of a working day (e.g. Friday 5pm when a 9-5pm working calendar is in play), the system will instead return a value for the first working moment of the following working day e.g. Monday 9am.
This option is only available when a unit of 'working hours' or 'working days' has been selected.
Due Date method configuration includes a ‘Move to End of Day’ setting. When checked, the system will take the relevant date calculated based upon the rule’s settings, e.g. ‘add 5 working hours to start date’), and will set the due date to be the end of that working day.
For example, if the system calculates a due date of ‘11am’ on a particular day, clicking this attribute automatically shifts the value to end of that working day. The sequence of the logic here is important when understanding how date / time values are arrived at with this method. The logic sequence is as follows:
Run the "method"
Adjust by fixed (working) days/hours
Adjust by dynamic (working) days/hours
Add wait time if the option is selected (and if wait time exists).
If using working time then ensure the result is within working hours - moving to the start of the next working day if precisely at the end of a working day
Finally move to the end of the (working) day if selected.
This option is only available when a unit of 'working hours' or 'working days' has been selected.
Clicking on the 'References' tab of a flavour will show you where this Due Date rule is being used.
Various standard methods of calculating a due date can be selected from, Depending upon the method selected, additional parameters may be required, e.g. a specific schedule. See here for .
