topic Timer Boundary Event - Handling of Non-Working Hour/Day in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/timer-boundary-event-handling-of-non-working-hour-day/m-p/84353#M56759 <HTML><HEAD></HEAD><BODY><SPAN>When a Timer Boundary Event is attached to an User Task, how to take into account of non-working hours e.g. there is an User Task "EvaluateLoanRequest", with a Timer Boundary Event set to 4 hours. This task will be escalated to user Task "EvaluateRequestByManager" if the user task "EvaluateLoanRequest" if not completed within 4 Hours. If the user task "EvaluateLoanRequest" is received at 4:30 pm, the task will be escalated to user task "EvaluateRequestByManager" at 8:31 p.m. since the user working hours is from 8am to 5 pm and the task is therefore not completed. This is not correct in term of operation i.e. the user task should be escalated on the following day at 11:31 am if it is still not completed by then. In addition to working hours, how can we account for non-working days like weekend or public holidays ?</SPAN></BODY></HTML> Tue, 07 Aug 2012 04:09:06 GMT bkseow 2012-08-07T04:09:06Z Timer Boundary Event - Handling of Non-Working Hour/Day https://connect.hyland.com/t5/alfresco-archive/timer-boundary-event-handling-of-non-working-hour-day/m-p/84353#M56759 When a Timer Boundary Event is attached to an User Task, how to take into account of non-working hours e.g. there is an User Task "EvaluateLoanRequest", with a Timer Boundary Event set to 4 hours. This task will be escalated to user Task "EvaluateRequestByManager" if the user task "EvaluateLoanReque Tue, 07 Aug 2012 04:09:06 GMT https://connect.hyland.com/t5/alfresco-archive/timer-boundary-event-handling-of-non-working-hour-day/m-p/84353#M56759 bkseow 2012-08-07T04:09:06Z Re: Timer Boundary Event - Handling of Non-Working Hour/Day https://connect.hyland.com/t5/alfresco-archive/timer-boundary-event-handling-of-non-working-hour-day/m-p/84354#M56760 <HTML><HEAD></HEAD><BODY><SPAN>See org.activiti.engine.impl.calendar.BusinessCalendar and org.activiti.engine.impl.calendar.BusinessCalendarManager. The manager can be plugged into the engine-configuration (property name="businessCalendarManager"). Every time a due-date is calculated, that class is consulted. You can write your implementation that follows your own timing.</SPAN><BR /><BR /><SPAN>ProcessEngineConfigurationImpl:</SPAN><BR /><CODE><BR />protected void initBusinessCalendarManager() {<BR />&nbsp;&nbsp;&nbsp; if (businessCalendarManager==null) {<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MapBusinessCalendarManager mapBusinessCalendarManager = new MapBusinessCalendarManager();<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mapBusinessCalendarManager.addBusinessCalendar(DurationBusinessCalendar.NAME, new DurationBusinessCalendar());<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mapBusinessCalendarManager.addBusinessCalendar(DueDateBusinessCalendar.NAME, new DueDateBusinessCalendar());<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mapBusinessCalendarManager.addBusinessCalendar(CycleBusinessCalendar.NAME, new CycleBusinessCalendar());<BR /><BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; businessCalendarManager = mapBusinessCalendarManager;<BR />&nbsp;&nbsp;&nbsp; }<BR />&nbsp; }<BR /></CODE></BODY></HTML> Thu, 27 Sep 2012 13:12:00 GMT https://connect.hyland.com/t5/alfresco-archive/timer-boundary-event-handling-of-non-working-hour-day/m-p/84354#M56760 frederikherema1 2012-09-27T13:12:00Z