JCH
Java Community | Help. Code. Learn.ā€¢2mo ago
dghf

Issues with Contract Work Percentage Constraint in Employee Scheduling

Hi, I'm working on an employee scheduling system using Timefold and have encountered an issue with implementing a contract work percentage constraint. The goal is to ensure employees are scheduled according to their contract work percentage, but I'm facing a couple of challenges: 1. Employees with 0% Contract Work Percentage: - Currently, employees with a 0% contract work percentage are still being assigned shifts. I want to ensure they are not assigned any shifts at all. 2. Updating Contract Work Percentage: - I'm considering updating the employee's contract work percentage dynamically based on certain conditions. Any advice on best practices for this? Here's my current constraint implementation: 
public Constraint workPercentage(ConstraintFactory constraintFactory) {
    return constraintFactory.forEach(Employee.class)
            .join(Shift.class, equal(Employee::getName, Shift::getEmployee))
            .groupBy(
                    (employee, shift) -> employee,
                    ConstraintCollectors.sumDuration((employee, shift) -> 
                        Duration.between(shift.getStart(), shift.getEnd()))
                )
            .filter((employee, totalWorkedHours) -> {
                double fullTimeHours = 40.0;
                double desiredHours = employee.getWorkPercentage() * fullTimeHours;
                return totalWorkedHours.toHours() != desiredHours;
            })
            .penalize(HardSoftBigDecimalScore.ONE_HARD, (employee, totalWorkedHours) -> {
                return (int) totalWorkedHours.toHours() - employee.getWorkPercentage() * 40;
            })
            .asConstraint("Employee work percentage not matched");
}
public Constraint workPercentage(ConstraintFactory constraintFactory) {
    return constraintFactory.forEach(Employee.class)
            .join(Shift.class, equal(Employee::getName, Shift::getEmployee))
            .groupBy(
                    (employee, shift) -> employee,
                    ConstraintCollectors.sumDuration((employee, shift) -> 
                        Duration.between(shift.getStart(), shift.getEnd()))
                )
            .filter((employee, totalWorkedHours) -> {
                double fullTimeHours = 40.0;
                double desiredHours = employee.getWorkPercentage() * fullTimeHours;
                return totalWorkedHours.toHours() != desiredHours;
            })
            .penalize(HardSoftBigDecimalScore.ONE_HARD, (employee, totalWorkedHours) -> {
                return (int) totalWorkedHours.toHours() - employee.getWorkPercentage() * 40;
            })
            .asConstraint("Employee work percentage not matched");
}
85 Replies
JavaBot
JavaBotā€¢2mo ago
āŒ› This post has been reserved for your question.
Hey @dghf! Please use /close or the Close Post button above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically marked as dormant after 300 minutes of inactivity.
TIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here.
dghf
dghfOPā€¢2mo ago
Questions: 1. How can I modify the constraint to ensure employees with 0% contract work percentage are not assigned any shifts? 2. Is there a recommended way to update the employee's contract work percentage dynamically within the constraint? Additional Context: - I'm using Timefold 1.19.0 with Quarkus. - Other constraints, like shift preferences, are working fine. Any insights or suggestions would be greatly appreciated! Thank you!
JavaBot
JavaBotā€¢2mo ago
If you are finished with your post, please close it. If you are not, please ignore this message. Note that you will not be able to send further messages here after this post have been closed but you will be able to create new posts.
ayylmao123xdd
ayylmao123xddā€¢2mo ago
not sure if thats what you want but couldnt you filter if work percentage is 0 for a given employee in the .filter() part
dghf
dghfOPā€¢2mo ago
@ayylmao123xdd It didnt work, even when you filter, it's still assigned the employee.
dan1st
dan1stā€¢2mo ago
Can you show your modified filtering?
dghf
dghfOPā€¢2mo ago
@dan1st | Daniel 
.filter((employee, totalWorkedHours) -> {
                        double fullTimeHours = 160; // Assume 40 hours as full-time
                        double maxAllowedHours = (employee.getWorkPercentage() * fullTimeHours) / 100;    
                        return (totalWorkedHours > maxAllowedHours) || employee.getWorkPercentage() == 0;  // Penalize if worked hours exceed allowed hours
                    })
.filter((employee, totalWorkedHours) -> {
                        double fullTimeHours = 160; // Assume 40 hours as full-time
                        double maxAllowedHours = (employee.getWorkPercentage() * fullTimeHours) / 100;    
                        return (totalWorkedHours > maxAllowedHours) || employee.getWorkPercentage() == 0;  // Penalize if worked hours exceed allowed hours
                    })
dan1st
dan1stā€¢2mo ago
shouldn't that condition be inverted? normally, the filter gives you the elements that match the condition
dghf
dghfOPā€¢2mo ago
dghf
dghfOPā€¢2mo ago
I got this from doing PUT And this is the reworked code 
.filter((employee, totalWorkedHours) -> {
    double fullTimeHours = 160; // Assume 40 hours as full-time
    double maxAllowedHours = (employee.getWorkPercentage() * fullTimeHours) / 100;
    return totalWorkedHours <= maxAllowedHours && employee.getWorkPercentage() > 0; // The changed correct logic
})
.filter((employee, totalWorkedHours) -> {
    double fullTimeHours = 160; // Assume 40 hours as full-time
    double maxAllowedHours = (employee.getWorkPercentage() * fullTimeHours) / 100;
    return totalWorkedHours <= maxAllowedHours && employee.getWorkPercentage() > 0; // The changed correct logic
})
dan1st
dan1stā€¢2mo ago
looks about right Does that match your expectations?
dghf
dghfOPā€¢2mo ago
@dan1st | Daniel still Alice assigned to one, when their work percentage is 0: 
"shifts": [
        {
            "id": "2027-02-01-night1",
            "start": "2025-02-01T07:00:00",
            "end": "2025-02-01T10:00:00",
            "location": "Hospital",
            "requiredSkill": "Nursing",
            "shiftType": "MORNING",
            "employee": {
                "name": "Alice",
                "skills": [
                    "Nursing",
                    "CPR"
                ],
                "unavailableDates": [],
                "undesiredDates": [],
                "desiredDates": [],
                "shiftPreferences": [
                    "NIGHT",
                    "MORNING"
                ],
                "workPercentage": 0
            }
        },
"shifts": [
        {
            "id": "2027-02-01-night1",
            "start": "2025-02-01T07:00:00",
            "end": "2025-02-01T10:00:00",
            "location": "Hospital",
            "requiredSkill": "Nursing",
            "shiftType": "MORNING",
            "employee": {
                "name": "Alice",
                "skills": [
                    "Nursing",
                    "CPR"
                ],
                "unavailableDates": [],
                "undesiredDates": [],
                "desiredDates": [],
                "shiftPreferences": [
                    "NIGHT",
                    "MORNING"
                ],
                "workPercentage": 0
            }
        },
Both should've been assigned to Bob
dghf
dghfOPā€¢2mo ago
See here
No description
Shruti
Shrutiā€¢2mo ago
dan1st
dan1stā€¢2mo ago
Is that the result of filtering?
dghf
dghfOPā€¢2mo ago
My friend will enter the conversation, we're working together @dan1st | Daniel, he can explain better šŸ˜„
Louai
Louaiā€¢2mo ago
that the result of the solving if you look on the shifts that been assigned we see that Alice is assigned to first one while Alice workPercentage is 0
Shruti
Shrutiā€¢2mo ago
"shifts": [ 
        {
            "id": "2027-02-01-night1",
            "start": "2025-02-01T07:00:00",
            "end": "2025-02-01T10:00:00",
            "location": "Hospital",
            "requiredSkill": "Nursing",
            "shiftType": "MORNING",
            "employee": {
                "name": "Alice",
                "skills": [
                    "Nursing",
                    "CPR"
                ],
                "unavailableDates": [],
                "undesiredDates": [],
                "desiredDates": [],
                "shiftPreferences": [
                    "NIGHT",
                    "MORNING"
                ],
                "workPercentage": 0
            }
        }, 
        {
            "id": "2027-02-01-night1",
            "start": "2025-02-01T07:00:00",
            "end": "2025-02-01T10:00:00",
            "location": "Hospital",
            "requiredSkill": "Nursing",
            "shiftType": "MORNING",
            "employee": {
                "name": "Alice",
                "skills": [
                    "Nursing",
                    "CPR"
                ],
                "unavailableDates": [],
                "undesiredDates": [],
                "desiredDates": [],
                "shiftPreferences": [
                    "NIGHT",
                    "MORNING"
                ],
                "workPercentage": 0
            }
        },
This message has been formatted automatically. You can disable this using /preferences.
dan1st
dan1stā€¢2mo ago
It does say "solverStatus": "NOT_SOLVING" For this shift, the end is before the start 
        {
            "id": "2027-02-01-night2",
            "start": "2025-02-01T22:00:00",
            "end": "2025-02-01T00:00:00",
            "location": "Hospital",
            "requiredSkill": "Nursing",
            "shiftType": "NIGHT",
            "employee": {
                "name": "Bob",
                "skills": [
                    "Nursing",
                    "Medical Assistance"
                ],
                "unavailableDates": [],
                "undesiredDates": [],
                "desiredDates": [],
                "shiftPreferences": [
                    "NIGHT",
                    "MORNING"
                ],
                "workPercentage": 100
            }
        }
        {
            "id": "2027-02-01-night2",
            "start": "2025-02-01T22:00:00",
            "end": "2025-02-01T00:00:00",
            "location": "Hospital",
            "requiredSkill": "Nursing",
            "shiftType": "NIGHT",
            "employee": {
                "name": "Bob",
                "skills": [
                    "Nursing",
                    "Medical Assistance"
                ],
                "unavailableDates": [],
                "undesiredDates": [],
                "desiredDates": [],
                "shiftPreferences": [
                    "NIGHT",
                    "MORNING"
                ],
                "workPercentage": 100
            }
        }
Are you using some linear programming/linear constrained optimization library?
Louai
Louaiā€¢2mo ago
The solve status is a flag that indicates when the solving process is finishing. Since the Timefold solver performs solving while it's still in progress, the flag will show that it is still solving. Therefore, the status does not indicate anything about the shifts. "solverStatus": "SOLVING_ACTIVE" while its still solving
dghf
dghfOPā€¢2mo ago
The code is using a library called Timefold Solver, which is a constraint solver. It is used for solving planning and scheduling problems by defining constraints and optimizing solutions based on those constraints. The constraints are defined in our EmployeeSchedulingConstraintProvider class, using the Timefold Solver's API, which includes classes like ConstraintFactory, ConstraintCollectors, and HardSoftBigDecimalScore. These are used to define and manage constraints for employee scheduling, such as ensuring no overlapping shifts, respecting employee preferences, and balancing shift assignments.
dan1st
dan1stā€¢2mo ago
well in the output it was In the output, it was NOT_SOLVING with "feasible": false Can I see the exact input?
Shruti
Shrutiā€¢2mo ago
{
  "employees": [
    {
      "name": "Alice",
      "skills": ["Nursing", "CPR"],
      "unavailableDates": [],
      "undesiredDates": [],
      "desiredDates": [],
      "shiftPreferences": ["MORNING","NIGHT"],
      "workPercentage": 0
    },
    {
      "name": "Bob",
      "skills": ["Medical Assistance", "Nursing"],
      "unavailableDates": [],
      "undesiredDates": [],
      "desiredDates": [],
      "shiftPreferences": ["NIGHT","MORNING"],
      "workPercentage": 100
    }
  ],
  "shifts": [
    {
      "id": "2027-02-03-night1",
      "start": "2025-02-03T07:00",
      "end": "2025-02-03T10:00",
      "location": "Hospital",
      "requiredSkill": "Nursing"
    },
        {
      "id": "2027-02-01-night2",
      "start": "2025-02-01T22:00",
      "end": "2025-02-01T23:59",
      "location": "Hospital",
      "requiredSkill": "Nursing"
    }
  ]
} 
{
  "employees": [
    {
      "name": "Alice",
      "skills": ["Nursing", "CPR"],
      "unavailableDates": [],
      "undesiredDates": [],
      "desiredDates": [],
      "shiftPreferences": ["MORNING","NIGHT"],
      "workPercentage": 0
    },
    {
      "name": "Bob",
      "skills": ["Medical Assistance", "Nursing"],
      "unavailableDates": [],
      "undesiredDates": [],
      "desiredDates": [],
      "shiftPreferences": ["NIGHT","MORNING"],
      "workPercentage": 100
    }
  ],
  "shifts": [
    {
      "id": "2027-02-03-night1",
      "start": "2025-02-03T07:00",
      "end": "2025-02-03T10:00",
      "location": "Hospital",
      "requiredSkill": "Nursing"
    },
        {
      "id": "2027-02-01-night2",
      "start": "2025-02-01T22:00",
      "end": "2025-02-01T23:59",
      "location": "Hospital",
      "requiredSkill": "Nursing"
    }
  ]
}
This message has been formatted automatically. You can disable this using /preferences.
dghf
dghfOPā€¢2mo ago
@dan1st | Daniel
dan1st
dan1stā€¢2mo ago
Can you show the Shift and Employee classes?
ayylmao123xdd
ayylmao123xddā€¢2mo ago
ayylmao123xdd
ayylmao123xddā€¢2mo ago
i am back also for this piece right here shouldnt you add like a check where you do current worked hours + the hours you gonna work and check if its above max allowed hours because if im getting it right if you are at lets say 159 worked hours and max allowed is 160 then you will be able to work the whole shift anyway
Louai
Louaiā€¢2mo ago
dghf
dghfOPā€¢2mo ago
@dan1st | Daniel @ayylmao123xdd so doing this? 
.filter((employee, totalWorkedHours) -> {
    double fullTimeHours = 160; // Assume 40 hours as full-time
    double maxAllowedHours = (employee.getWorkPercentage() * fullTimeHours) / 100;
    double currentShiftHours = Duration.between(shift.getStart(), shift.getEnd()).toHours();
    return (totalWorkedHours + currentShiftHours) <= maxAllowedHours && employee.getWorkPercentage() > 0;
})
.filter((employee, totalWorkedHours) -> {
    double fullTimeHours = 160; // Assume 40 hours as full-time
    double maxAllowedHours = (employee.getWorkPercentage() * fullTimeHours) / 100;
    double currentShiftHours = Duration.between(shift.getStart(), shift.getEnd()).toHours();
    return (totalWorkedHours + currentShiftHours) <= maxAllowedHours && employee.getWorkPercentage() > 0;
})
ayylmao123xdd
ayylmao123xddā€¢2mo ago
i guess give it a try
Louai
Louaiā€¢2mo ago
I think the logic is correct, but the current approach first calculates the shift's hours, then checks if the employee's work percentage allows them to take the shift. Instead, it should update the employee's remaining work percentage after assigning them a shift. totalWorkedHours is the shift hours
ayylmao123xdd
ayylmao123xddā€¢2mo ago
no clue what that means im too low on sunlight today šŸ˜­ disaster right
Louai
Louaiā€¢2mo ago
.groupBy( (employee, shift) -> employee, ConstraintCollectors.sum ((employee, shift) -> (int) Duration.between(shift.getStart(), shift.getEnd()).toHours()) calculate the shift hours
ayylmao123xdd
ayylmao123xddā€¢2mo ago
hmm maybe 
.filter((employee, totalWorkedHours) -> {
    double fullTimeHours = 160; // Assume 40 hours as full-time
    double maxAllowedHours = (employee.getWorkPercentage() * fullTimeHours) / 100;
    return totalWorkedHours <= maxAllowedHours && employee.getWorkPercentage() > 0; // The changed correct logic
})
.filter((employee, totalWorkedHours) -> {
    double fullTimeHours = 160; // Assume 40 hours as full-time
    double maxAllowedHours = (employee.getWorkPercentage() * fullTimeHours) / 100;
    return totalWorkedHours <= maxAllowedHours && employee.getWorkPercentage() > 0; // The changed correct logic
})
so is this one correct or not if i look at it without thinking much i would say u need the total worked hours + current shift hours check
Louai
Louaiā€¢2mo ago
Duration.between(shift.getStart(), shift.getEnd()).toHours() represents the hours of a single shift and totalWorkedHours should be the sum of all assigned shift hours for an employee. then this should be correct i think
ayylmao123xdd
ayylmao123xddā€¢2mo ago
yea so basically what i said ig
dan1st
dan1stā€¢2mo ago
Note: 1h59min will result in you getting 1h
ayylmao123xdd
ayylmao123xddā€¢2mo ago
total worked hours + duration of single shift <= max allowed hours free unpaid overtime
Louai
Louaiā€¢2mo ago
.toMinutes() and divide 60? ye that correct but how
dan1st
dan1stā€¢2mo ago
Well when should it count the hour and when shouldn't it?
ayylmao123xdd
ayylmao123xddā€¢2mo ago
well if i was the employee 1 hour and 1 minute would count as 2 hours of work
Louai
Louaiā€¢2mo ago
the problem is i cant access the duration of single shift in filter maybe count the minutes then have a logic for the hours?
dan1st
dan1stā€¢2mo ago
what do you want to do if you have like 45min? or 30min? currently you are using integer hours for everything so you cannot do scheduling with anything except hours
ayylmao123xdd
ayylmao123xddā€¢2mo ago
i meaaaaaaaaaaaaaaaaaaaaaaaan if its a normal job ur paid by hour so ig counting the hours is the best option like even if its 1 hour 10 minutes count it as 2 h
dan1st
dan1stā€¢2mo ago
most are computing it more granually like if you have 30min on one day and 30min on another day, you have 1h in total
ayylmao123xdd
ayylmao123xddā€¢2mo ago
depends on the company ig then so in that case i would count the minutes instead of hours same for
Louai
Louaiā€¢2mo ago
Correct, I didn't fully think about that šŸ˜…. Should we use 30-minute increments, or just round to the closest hour?
ayylmao123xdd
ayylmao123xddā€¢2mo ago
totalworkedminutes instead of hours
Louai
Louaiā€¢2mo ago
its a thesis work so not really a big deal
dan1st
dan1stā€¢2mo ago
idk what you are doing - it might be best to just schedule everything based on minutes
dghf
dghfOPā€¢2mo ago
@dan1st | Daniel But even if we count in minutes instead of hours, shouldn't workpercentage being 0 mean that no shifts are assigned to that particular employee? The problem could lie somewhere in the logic here 
public Constraint workPercentage(ConstraintFactory constraintFactory) {
    return constraintFactory.forEach(Employee.class)
            .join(Shift.class, equal(Employee::getName, Shift::getEmployee))
            .groupBy(
                    (employee, shift) -> employee,
                    ConstraintCollectors.sumDuration((employee, shift) -> 
                        Duration.between(shift.getStart(), shift.getEnd()))
                )
            .filter((employee, totalWorkedHours) -> {
                double fullTimeHours = 40.0;
                double desiredHours = employee.getWorkPercentage() * fullTimeHours;
                return totalWorkedHours.toHours() != desiredHours;
            })
            .penalize(HardSoftBigDecimalScore.ONE_HARD, (employee, totalWorkedHours) -> {
                return (int) totalWorkedHours.toHours() - employee.getWorkPercentage() * 40;
            })
            .asConstraint("Employee work percentage not matched");
}
public Constraint workPercentage(ConstraintFactory constraintFactory) {
    return constraintFactory.forEach(Employee.class)
            .join(Shift.class, equal(Employee::getName, Shift::getEmployee))
            .groupBy(
                    (employee, shift) -> employee,
                    ConstraintCollectors.sumDuration((employee, shift) -> 
                        Duration.between(shift.getStart(), shift.getEnd()))
                )
            .filter((employee, totalWorkedHours) -> {
                double fullTimeHours = 40.0;
                double desiredHours = employee.getWorkPercentage() * fullTimeHours;
                return totalWorkedHours.toHours() != desiredHours;
            })
            .penalize(HardSoftBigDecimalScore.ONE_HARD, (employee, totalWorkedHours) -> {
                return (int) totalWorkedHours.toHours() - employee.getWorkPercentage() * 40;
            })
            .asConstraint("Employee work percentage not matched");
}
(from the OP)
dan1st
dan1stā€¢2mo ago
minutes vs hours shouldn't change anything there
dghf
dghfOPā€¢2mo ago
Yeah, but do you know what could be the issue instead? Should we do more logging somewhere to see what could be causing the issue along the way?
dan1st
dan1stā€¢2mo ago
Does the library allow doing custom logging? oh wait you are using != on doubles don't do that doubles aren't exact values I think return totalWorkedHours.toHours() < desiredHours should be ok or return totalWorkedHours.toHours() < desiredHours - 0.0001 or similar
dghf
dghfOPā€¢2mo ago
I think return totalWorkedHours.toHours() < desiredHours should be ok
we've tried this but it didn't work But why
return totalWorkedHours.toHours() < desiredHours - 0.0001
dan1st
dan1stā€¢2mo ago
You mean why the -0.0001?
dghf
dghfOPā€¢2mo ago
Yeah Like why do we subtract 0.0001 from desiredHours?
dan1st
dan1stā€¢2mo ago
If you are using double, you are not dealing with precise values for example if you compute 0.1+0.2, you'll get something like 0.2999999... and not 0.3
ayylmao123xdd
ayylmao123xddā€¢2mo ago
or maybe just use bigdouble
dan1st
dan1stā€¢2mo ago
and I'm subtracting a delta to ensure it's actually smaller
ayylmao123xdd
ayylmao123xddā€¢2mo ago
for calculations or whatever that class was called
dan1st
dan1stā€¢2mo ago
it's called BigDecimal but there are some other issues with it tbh fixed point mathw ith long might also work lol
ayylmao123xdd
ayylmao123xddā€¢2mo ago
or just swap to minutes šŸ˜± so u dont have 1.1 minute ezzzzzzzzzzz
dan1st
dan1stā€¢2mo ago
the only thing where decimal numbers are coming from here is the percentages lol
ayylmao123xdd
ayylmao123xddā€¢2mo ago
cant u just floor it
dan1st
dan1stā€¢2mo ago
then floor(0.2999999999) gives 0.2
ayylmao123xdd
ayylmao123xddā€¢2mo ago
oh yea i meant the round l0l
dan1st
dan1stā€¢2mo ago
same problem with 0.49999999 the solutions is comparing stuff with a delta
ayylmao123xdd
ayylmao123xddā€¢2mo ago
disaster then
dan1st
dan1stā€¢2mo ago
using a delta is no problem
ayylmao123xdd
ayylmao123xddā€¢2mo ago
delta force
ayylmao123xdd
ayylmao123xddā€¢2mo ago
Louai
Louaiā€¢2mo ago
im rewriting the whole constriant hopes it becomes better
Shruti
Shrutiā€¢2mo ago
Constraint workPercentage(ConstraintFactory constraintFactory) {
    return constraintFactory.forEach(Employee.class)
            .join(Shift.class, equal(Employee::getName, Shift::getEmployee)) // Join Employee and Shift on Employee
            .filter((employee, shift) -> {
                long fullTimeMinutes = 160 * 60; // 40 hours/week * 60 minutes/hour (2400 minutes)
                // Get the employee's total work time in minutes based on their work percentage
                long employeeWorkMinutes = (employee.getWorkPercentage() * fullTimeMinutes) / 100;
                
                // Get the shift duration in minutes
                long shiftMinutes = Duration.between(shift.getStart(), shift.getEnd()).toMinutes();
                
                // Calculate the new available work time in minutes after the shift is assigned
                long newEmployeeWorkMinutes = employeeWorkMinutes - shiftMinutes;  // Subtract shift duration
                
                // Ensure that the employee's total work minutes doesn't go below 0
                return newEmployeeWorkMinutes >= 0;
            })
            .penalize(HardSoftBigDecimalScore.ONE_HARD)
            .asConstraint("Employee work percentage exceeded");
} 
Constraint workPercentage(ConstraintFactory constraintFactory) {
    return constraintFactory.forEach(Employee.class)
            .join(Shift.class, equal(Employee::getName, Shift::getEmployee)) // Join Employee and Shift on Employee
            .filter((employee, shift) -> {
                long fullTimeMinutes = 160 * 60; // 40 hours/week * 60 minutes/hour (2400 minutes)
                // Get the employee's total work time in minutes based on their work percentage
                long employeeWorkMinutes = (employee.getWorkPercentage() * fullTimeMinutes) / 100;
                
                // Get the shift duration in minutes
                long shiftMinutes = Duration.between(shift.getStart(), shift.getEnd()).toMinutes();
                
                // Calculate the new available work time in minutes after the shift is assigned
                long newEmployeeWorkMinutes = employeeWorkMinutes - shiftMinutes;  // Subtract shift duration
                
                // Ensure that the employee's total work minutes doesn't go below 0
                return newEmployeeWorkMinutes >= 0;
            })
            .penalize(HardSoftBigDecimalScore.ONE_HARD)
            .asConstraint("Employee work percentage exceeded");
}
This message has been formatted automatically. You can disable this using /preferences.
Louai
Louaiā€¢2mo ago
what do you think? is that better way?
dghf
dghfOPā€¢2mo ago
@dan1st | Daniel
dan1st
dan1stā€¢2mo ago
looks about fine
Louai
Louaiā€¢2mo ago
i subtract the shiftminutes from the employeeworkminutes "workpercentage" then im thinking about updating the working percentage each time a shift assign to the employee
dan1st
dan1stā€¢2mo ago
You can try logging the employee, shift and the returned value in every filter() call
dghf
dghfOPā€¢2mo ago
Hmm I am not sure how that'd be done. Any suggestions?
dan1st
dan1stā€¢2mo ago
boolean result = newEmployeeWorkMinutes >= 0;
System.out.println(employee + " | " + shift + ": " + result);
return result;
boolean result = newEmployeeWorkMinutes >= 0;
System.out.println(employee + " | " + shift + ": " + result);
return result;
Shruti
Shrutiā€¢2mo ago
Constraint workPercentage(ConstraintFactory constraintFactory) {
        return constraintFactory.forEach(Shift.class)
                .filter(shift -> shift.getEmployee() != null) // Ensure shift has an employee
                .groupBy(shift -> shift.getEmployee(), // Group shifts by employee
                ConstraintCollectors.sumLong(shift -> Duration.between(shift.getStart(), shift.getEnd()).toMinutes())) // Sum total assigned minutes
                .filter((employee, totalShiftMinutes) -> {
                        long fullTimeMinutes = 160 * 60; // 9600 minutes per month (assuming full-time is 160 hours)
                        long employeeAvailableMinutes = (employee.getWorkPercentage() * fullTimeMinutes) / 100;
                        return totalShiftMinutes > employeeAvailableMinutes; // Penalize if assigned shifts exceed allowed minutes
                })
                .penalize(HardSoftBigDecimalScore.ONE_HARD)
                .asConstraint("Employee work percentage exceeded");
    } 
Constraint workPercentage(ConstraintFactory constraintFactory) {
        return constraintFactory.forEach(Shift.class)
                .filter(shift -> shift.getEmployee() != null) // Ensure shift has an employee
                .groupBy(shift -> shift.getEmployee(), // Group shifts by employee
                ConstraintCollectors.sumLong(shift -> Duration.between(shift.getStart(), shift.getEnd()).toMinutes())) // Sum total assigned minutes
                .filter((employee, totalShiftMinutes) -> {
                        long fullTimeMinutes = 160 * 60; // 9600 minutes per month (assuming full-time is 160 hours)
                        long employeeAvailableMinutes = (employee.getWorkPercentage() * fullTimeMinutes) / 100;
                        return totalShiftMinutes > employeeAvailableMinutes; // Penalize if assigned shifts exceed allowed minutes
                })
                .penalize(HardSoftBigDecimalScore.ONE_HARD)
                .asConstraint("Employee work percentage exceeded");
    }
Finally its working :3 thank you for your help
This message has been formatted automatically. You can disable this using /preferences.
Louai
Louaiā€¢2mo ago
it loop through Shift.class instead of Employee.class because we want to check actual assignments. then it check if the shift has an assigned employee (shift.getEmployee() != null). if it does then we go through the same logic
dghf
dghfOPā€¢2mo ago
@dan1st | Daniel We'll verify that employees do not exceed their assigned work percentage. For example, if an employee has a 1% work percentage, they should only be assigned shifts that fit within that limit.
JavaBot
JavaBotā€¢2mo ago
šŸ’¤ Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived. If your question was not answered yet, feel free to re-open this post or create a new one. In case your post is not getting any attention, you can try to use /help ping. Warning: abusing this will result in moderative actions taken against you.

Did you find this page helpful?