Skip to main content
Nintex Community Menu Bar

Classify a list item as \overdue\" by comparing two dates"

  • January 16, 2019
  • 1 reply
  • 20 views

Forum|alt.badge.img

Hello all!

So, I'm fairly new to the Nintex World, only started working with it since last October. Now I'm developing a form that needs input from various departments. The way I set it was in the inicial form, I have some fields that are filled in by the iniciator. Then, on the same form, I have multiple panels with controls (mainly star dates and end dates). When the item is created, the workflow sets a Request Review for Department1 to fill in. The diference between start date and end date cannot be bigger than 120 days. If it does, the list item must be considered as "Overdue" (I plan to write this information in a list column). The Workflow goes forward if Department1 introduces the end date, as the start date is set as the date when the list item is created. Then it promps another Request Review to another department do to the same thing (introduce dates), where I have to validate the same thing, but with a difference between dates of 30 days. 

At this moment, I have in the workflow a "Wait for Item Update" next to the Request Review. I already know how to calculate the diference between the two dates (something like "If start date - 120 > today's date, then "overdue", else OK"). How can I check the difference between the dates "everyday"? I know I can't do it in runtime. And how can I store the "overdue" state if the diference is bigger than the number of days (120 or 30, depending on the department) I am really over my head on this one. Any help is much apreciated. 

PS.: Sorry for the long and confusing post, but I also struggle a bit with English.

1 reply

Forum|alt.badge.img+14
  • Scholar
  • January 21, 2019
 How can I check the difference between the dates "everyday"? 

typical approach is to design a site workflow and schedule it to run daily.

the workflow looks for items of interest (in your case ones that are 120 or 30 days ahead) and then appropriately process them (eg. flags them as overdue.

see eg. following blog - Site Workflow - Document Review Date Approaching Reminders