Adding a new Due Date Method - Fixed Day of Fixed Month of Next Year of work item start year
S
Sampurna Basu
There are business scenarios where the work item due date is next year of the work item creation date for example, a case has a due date of 31st January but has to be triggered on enate on 1st of November previous year. Currently we have no feature to tackle this kind of situations directly via the due date methods present and have to use different workarounds.
C
Claudine Richardson
Great to hear your perspective, Sampurna Basu! I have a few more questions for you:
- Can you provide more examples of the business scenarios where this new due date method would be applicable?
- What are the current workarounds you are using to handle these situations and what challenges are you facing with them?
- How frequently do these types of cases occur and what is their impact on your overall workflow?
S
Sampurna Basu
Claudine Richardson Please find my answers below
1) Some of the other processes include fees and filings (regulations) which falls on 31st Jan, 28th Feb, 31st March, 30th June and the processes needs to be completed by that date, but they need to be created on Enate automatically through Triggers 3 Months before the due date
2)Currently we are using the Due Date Method 'From Packet Start Date' and adding the total working days in a year to the start date to get our required date. but this is a very customized due date method created assuming it will start on the fixed date , so that the due date is correctly calculated as a workaround and the challenges would be the due date will be wrong if the start date of the work item for these processes is different , if manually someone starts this process the due date will be incorrect and then users have to override those due dates manually which increases a lot of user clicks
3)These processes start annually or twice a year, and it needs to be triggered for more than 500+ customers in Enate. so, a very significant volume.