SJEaton Posted October 13, 2017 Posted October 13, 2017 We have a lifespan setting on a human task for it to expire after 5 days however we want this to be 5 working days (i.e. not count weekends). Is there a variable we can enter to make this happen? Thanks Sam 2
SJEaton Posted October 16, 2017 Author Posted October 16, 2017 Hi, is anyone able to answer this query please? Thanks, Sam
James Ainsworth Posted October 16, 2017 Posted October 16, 2017 Hi @SJEaton I don't believe that there currently is a way of doing this. I will see if I can have someone come back with some more information and if there are any plans to add this. James
SJEaton Posted October 18, 2017 Author Posted October 18, 2017 Hi James OK, obviously due to the nature of our business we base things on working days so would be fab if this could be facilitated. Thanks, Sam 1
SJEaton Posted October 20, 2017 Author Posted October 20, 2017 Hi @James Ainsworth, any further news on this? Thanks Sam
James Ainsworth Posted October 20, 2017 Posted October 20, 2017 Hi Sam, I'll chase up to see if there are any plans to add this. I can confirm that it is not currently possible. Regards, James
Martyn Houghton Posted October 30, 2017 Posted October 30, 2017 @SJEaton, @James Ainsworth This would be something we would also be interested in as well. I presume the calculation would also take into account the Working Time Calendar linked to the request via the current Service Level, so that it can take in to account Bank/Public Holidays as well as weekends? Cheers Martyn
samwoo Posted October 31, 2017 Posted October 31, 2017 +1 - we need the tasks/nodes to expire within 5 working days based on the Working Calendar.
Darren Rose Posted November 1, 2017 Posted November 1, 2017 Yep, we've raised this request before for Tasks to be able to take into account working calendar, so I will add my +1 to this post as well
sprasad Posted May 8, 2019 Posted May 8, 2019 @James Ainsworth Can I check if there has been any progress on this please? Currently, when you use the On Hold button from Pending Activity, it automatically sets the hold date as 7 Days in future. As we count our SLA in working days, users have to use the sub-status activity a week prior to any BH then complete the Pending activity to On Hold. This causes extra work load plus some users forget to use the sub status option and use the standard activity causing Requests to come off hold on a Bank Holiday. On our in-house system, we have addressed this issue using the following as an example:INSERT INTO LE_NON_WORKING_DAYS VALUES(to_date('19/04/2019','22/04/2019','DD/MM/YYYY'));COMMIT; Many thanks.
James Ainsworth Posted May 8, 2019 Posted May 8, 2019 Hi @sprasad The change for having Activities use working time calendars is still in our backlog. This hasn't been scheduled yet with our development team. I'll update this post if there is any progress. Regards, James
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now