Desktop Client: Ensuring Task Duration Accounts for Resource or Other Constraints (or why are times too large?)

If a resource is (or resources are) required to perform a task, then the duration will be limited by when those resources are in schedule if you are running in Calendar mode. The duration is simply converted to some number of seconds. In addition it does matter if you're in Calendar mode or Compressed mode, as Compressed time has 'time conversion' to change what a 'day' or greater means; though Compressed mode does not use schedules, so resources will not be constrained by schedule.

So, for example, if you are in Calendar mode (24 hours/day, 7 days/week) and if you say a duration time for a shape (activity step of the process) is 2 days, iGrafx will convert 2 days to 48 hours (or, to be precise, 172800 seconds). If there is a single resource specified on the Resources page, and it only works 8 hours per day, 5 days per week, it can only work 40 hours per calendar week. If you've set the duration to be 48 hours, and work starts on Monday at 8 AM, the task will finish at the end of the next Monday and will have taken 8 calendar days (or 7.38, to be precise, as it doesn't go to midnight of that 8th day) to complete.