Jump to content

Recommended Posts

Posted

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 

  • Like 2
Posted

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

  • Like 1
Posted

+1 - we need the tasks/nodes to expire within 5 working days based on the Working Calendar.

  • 1 year later...
Posted

@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.

Posted

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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...