entities? you mean classes?Hi,
I've got a domain with the following entities:
a class cannot be a variable. This probably a problem fact that and person.getDesk() nor DeskAssignement.getPerson() is the planning variables.- Person (planning entity)
- Desk (planning variable)
Now I am totally confused :)- DeskAssignment (solution)
agreed, "immovable" is the correct concept to use for that
All persons should be assigned to a desk according to some rules.
What I would like to do is to make certain Persons and their Desk immovable, ie, they are assigned a desk in the initial solution and should be fixed there. They are only there for the score calculation.
Take a look at the course scheduling example.
I looked at 14.3.1 Immovable planning entities but couldn't really see how I would apply it to my use case.
Don't mix the concept of "(im)movable entities" (which is what you want) with the concept of "limiting value ranges per entity" or the concept of "filtering specific move selectors" (which is overkill and convoluted for your needs).Why is the filter applied at the planning entity level? Since it's the planning variable that changes I thought that I should somehow filter the allowed values for the Desk.
Regards,
Mats
_______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users