1 Reply Latest reply on Mar 23, 2009 5:54 PM by Ronald van Kuijk

    Working with holidays

    Anderson Souza Newbie

      Hi all,

      I am using the business calendar to calculate the time for a task occurs, actually I'm scheduling a job.This class reads jbpm.business.calendar.properties to know about the business hour and holidays. So, to add holidays I need open this file and edit it, I think it is boring and a common users can't do that..I would you like to know if there's a another way to do that?

      Another question is about the absolute duetime.
      For example: I create a job today (March 23) with the duration of 3 days. So the duedate is today + 3 (March 26). But let's suppose that I add a holiday (March 24), the duedate should be calculated again. I think JBPM doesn't know how to deal with this situation. Do you understand me? Any idea how to solve it?

      thanks in advance

        • 1. Re: Working with holidays
          Ronald van Kuijk Master

           

          I think it is boring and a common users can't do that..


          Boring? hmmmm... subjective statement. But I agree that common users can't do that. But..... it was never meant for common users to change this file. So I do not see a real problem

          I would you like to know if there's a another way to do that?


          Yes there is. You can change the jBPM core so that it reads the file/data from somewhere else. Than in addition, you can develop a webapp that helps you changing this data. You can even make it configurable per process.

          I think JBPM doesn't know how to deal with this situation.

          Correct
          Do you understand me?

          Yes
          Any idea how to solve it?

          Yes, at least three
          1: by writing an application that takes the definition, reads the duedates from the definition and recalculates all the new ones PER instance and stores that. That is assuming
          - you can be sure the duedate should be changed (it was not changed in another way) and you know at what date it was set.
          - you have the original date so you can recalculate (e.g. it was not based on a variable)
          - .... some other 'hazards'

          2: By changing the core of jBPM so it always calculates the duedate (expensive in queries!) based on the latest data

          3: By changing the jBPM core so more info about duedates is stored and can be used

          (Contributions always welcome ;-))